3. • Change is the new norm
• Build, measure, learn cycle
• Continuous Delivery is the new trend
• Organizations strive to reduce release cadence
• Blurred functions

4. Reducing the cost, time, and risk by delivering
incremental changes to users as early as possible

5. • Build the right thing
• Real project progress
• Reducing risk during release day
• Keeping your software fresh
• Continuous learning

6. 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

7. So the idea of Continuous Delivery is to deliver as
early as possible before your customer change their
mind.

8. “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

9. • 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”.

11. Learn Build
Customer Agile
development development
Measure

12. Build Measure & Learn
Too Late

13. Build
Measure & Learn

14. • 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

15. • 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

16. • 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

17. • 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