Description:
Join ThoughtWorks, renowned as one of the pioneers and leaders in the evolution and practice of Agile Software Development, as we present our Continuous Delivery workshop.
Who should attend?
Those who want to close the gap between Development (Applications/Software Engineering teams), Technology Operations (Release Managers), and Quality Assurance (Testing and QA Managers).
Learning Outcomes:
Refreshments, coffee and light fare will be served during breaks.
Agenda:
8:30am - 9:00am: Registration
9:00am - 10:30am
- Some short case studies of typical delivery environments: ones in which releasing software takes a long time and is painful, and ones which continuously deliver new software. Root cause analysis of slow, risky releases.
- How Things Ought To Be, using examples from several projects
- The value proposition of continuous delivery
- Questions & Answers
10:30am - 10:45am: Break
10:45am - 12:00pm
- A brief refresher on continuous integration, with particular reference to how to integrate it with the rest of the delivery process
- Why branching in version control is inimical to continuous delivery. Using incremental development, a superior alternative to version control branching which allows for application evolution. Example from Go
- Interactive exercise: take various architectures and team structures and discuss how to apply branch-by-abstraction to enable continuous delivery
12:00pm - 1:00pm: Lunch Break
12:00pm - 2:20pm
- Building deployment pipelines for component-based architectures, including dependency management
- Going live: How this differs from deployment. A/B testing and business metrics
- Data management and migration
2:20pm - 2:40pm: Break
2:40pm - 4:00pm
- Environment and Infrastructure management, including provisioning, management, and monitoring - part 2
- Managing continuous delivery Continuous improvement. How to implement a deployment pipeline through modeling the delivery process. How to evolve the pipeline, and your organization's delivery process