
Stop using separate environments for development, testing, and production (DTAP)
About this episode
In this episode we make a bold argument: stop using separate environments for development, testing, acceptance, and production - commonly called DTAP. Why? Because DTAP-pipelines create queues and accumulate all sorts of waste. Not only does this cost you a lot in terms of money and effort, they also make it harder to respond quickly to changing needs and emerging issues.
In this episode, we explore what the problem with DTAP-pipelines is. We also offer a number of alternative strategies that allow you to deploy faster AND with higher quality and reliability.
You can also read the accompanying blog post here (all sources are in there as well):
http://bit.ly/35vPVAz
Donate to support our work
https://bit.ly/supportheliberators
Follow us on Medium:
https://medium.com/the-liberators
We're building Columinity to help teams improve continuously based on scientific insights:
https://columinity.com
Check out our webshop for tons of powerful exercises and workshops to run with your team(s):
https://shop.theliberators.com
The music for episodes 91 and onward was written and produced for us by Basanite. The music for episodes 1-90 was acquired through Yummy Sounds. Post-production by Jasper Huiskamp.
Get every episode summarized
Each time The Liberators Podcast publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from The Liberators Podcast

In-Depth: What Is The Optimal Size For A Scrum Team?
The Liberators Podcast

5 Effective Ways To Increase Management Support For Agile
The Liberators Podcast

In-Depth: Is SAFe® Really That Bad?
The Liberators Podcast

In-Depth: How To Make Pair Programming More Effective
The Liberators Podcast