Abstract: How frequently does a good agile team deploy to production? Not every team is capable of deploying "on every commit". What does it take for a team to even start deploying at the end of each sprint, or each week, or each day?
Most companies don't realize that deploying more frequently often requires both significant technical change as well as cultural change. In this talk, I'll guide you through what it takes to deploy more frequently, both from the technical side of setting up pipelines as well as the organizational side of removing red tape. I'll draw on the unique challenges that teams must overcome at each step of the way, from deploying once a month all the way down to full continuous delivery. If your team has been struggling to go faster, come see how you can change to get there. And if you already are at full continuous delivery, come see how to go even faster than that!
Learning Outcomes: - Attendees should leave the talk with a full understanding of the different challenges for deploying at these intervals:
- - Once per sprint
- - Every few days
- - Daily
- - On Every Commit
- Attendees should be familiarized with common technical solutions to these problems, including:
- - Automation through delivery pipelines in Jenkins (or some other CI tool)
- - Feature toggles and their role in code
- - The role of automated acceptance testing and smoke testing (especially when you go fast)
- - Using configuration management tools to create consistency across environments
- - Strategies for versioning and dealing with "in transition" states
- Attendees should be able to answer to these common cultural questions:
- - Does more frequent doesn't equate to more risk?
- - How do you ensure quality without a dedicated QA team of manual testers?
- - Who should be responsible for authorizing deployments to production?
- - Do all deployments deliver functionality?
- - Are bug counts the only way to measure quality?
Attachments:
