15 teams, 1 monolith and 4 months to achieve Continuous Delivery

This is the story of 15 teams and one monolithic application going from bi-annual releases to fortnightly releases in 4 months time achieving a state of Continuous Delivery.

The reason for that move: the cost and time for testing quality into the software product, and stabilising and releasing the product during each bi-annual release were skyrocketing.

Continuous Delivery involves a long list of technology and organisational changes that you have to apply to the unique circumstances of your organisation. Where do you start?

This is where The Improvement Kata, Value Stream Mapping and Theory of Constraints are helpful tools to choose which changes to apply first. However, because of the short time frame, the plan ended differently and turned into fear mitigation. Which worked wonderfully well.

After this session, you’ll understand how The Improvement Kata, Value Stream Mapping, Theory of Constraints can kick-start a Continuous Delivery program and mitigate fear.

Folks who should attend are anyone involved near and far in designing, creating, testing, deploying and releasing a software product.

 
1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Case Study

The presentation is about my experience of helping a federal Belgian agency achieving Continuous Delivery with 15 teams on one monolithic application.

00:00 Introduction: the context of the organisation

00:05 The plan: what I had in mind when starting this journey - The Improvement Kata, Value Stream Mapping and Theory of Constraints

00:15 What actually happened: how the plan turned out differently than expected

00:25 Tada: achieving Continuous Delivery and what were the outcomes for the organisation

00:30 The learnings: what I learned from this journey

00:35 Questions

This presentation will be given for the very first time at Expand Conf in Amsterdam beginning of September 2019. Hopefully, I'll get the necessary feedback to improve the session.

Learning Outcome

  • Be able to kick-start a Continuous Delivery program.
  • Be able to use the Improvement Kata to introduce change at scale.
  • Be able to run a Value Stream Mapping workshop to understand the current situation.
  • Be able to use the Theory of Constraints to identify which activity should be improved first.
  • Be able to mitigate fear.

Target Audience

Anyone involved near and far in designing, creating, testing, deploying and releasing a software product, i.e. software engineers, test engineers, architects, product managers but also CTOs, agile coaches, technology leaders, ...

Prerequisites for Attendees

Have a basic understanding of what Continuous Delivery is.

schedule Submitted 5 days ago

Public Feedback

comment Suggest improvements to the Speaker