building an organisation for continuous delivery
TRANSCRIPT
• Change is the new norm
• Build, measure, learn cycle
• Continuous Delivery is the new trend
• Organizations strive to reduce release cadence
• Blurred functions
Reducing the cost, time, and risk by delivering
incremental changes to users as early as possible
• Build the right thing
• Real project progress
• Reducing risk during release day
• Keeping your software fresh
• Continuous learning
You can't just ask customers what they want and
then try to give that to them.
By the time you get it built, they'll want something
new.
-- Steve Jobs
So the idea of Continuous Delivery is to deliver as
early as possible before your customer change their
mind.
“How long would it take your organization to deploy
a change that involved just one single line of code?
Do you do this on a repeatable, reliable basis?”
-- Mary and Tom Poppendieck
• The market value of a feature
ultimately goes to zero.
• Software depreciates over time.
• We need to keep our software
fresh.
• 1-4 weeks of “freshness”.
Build
Measure
Learn
Agile
development
Customer
development
Build Measure & Learn
Too Late
Build
Measure & Learn
• Analysts, marketing, coder, tester and operations
work as one team – remove the silos
• Focus on product’s success not department’s
success – no politics!
• Shorten the release cadence
• Start with continuous deployment
• Define metrics that matters and monitor
• Keep on releasing to production
• Move away from managing to coaching
• Continuously learn, continuously improve
• What ever happens keep on releasing
• It puts people under pressure and it forces
people to think about quality
• You will never get it right, you only make it better
than today
• Managing people limits creativity, it prevents
collaboration and it slows people down
• Managing large teams or many teams is even
harder
• Helps teams to release in short cadence