Upload
others
View
11
Download
0
Embed Size (px)
Citation preview
1© S c a le d A g i le , In c .
Scalable DevOps and Continuous Delivery for the Agile Release TrainThe 9 deadly mistakes organizations make and a simple 5 step plan to overcome them
2© S c a le d A g i le , In c .© S c a le d A g i le , In c . 2
Inbar OrenMethodologist and SAFe fellow
Scaled Agile, Inc
3© S c a le d A g i le , In c .
Inbar Oren
4A developer, team lead, project manger, product manager
4Helping enterprises with Agile for over a decade
4Part of the SAFe framework team
43rd degree black belt in Iaido and Jodo
4Family at scale
4© S c a le d A g i le , In c . 4© S c a le d A g i le , In c .
Mistake #1 – Underestimating the impact
5© S c a le d A g i le , In c .
Adapt or dieSince 2000, 52 percent of the names on the Fortune 500 list are gone, either as a result of mergers, acquisitions or bankruptcies.
—Teresa Novellino, New York Business Journal
6© S c a le d A g i le , In c . 6© S c a le d A g i le , In c .
Mistake #2 – Forgetting the Goal
7© S c a le d A g i le , In c .
What are we trying to accomplish
8© S c a le d A g i le , In c . 8© S c a le d A g i le , In c .
Mistake #3 – We Know What Our Customers Want
9© S c a le d A g i le , In c .
We want faster horses
https://w w w .google.com /url?sa=i& rct= j& q=& esrc=s& source=im ages& cd=& cad=rja& uact=8& ved=0ahU K E w iW 4-
roz9nW A hU i34M K H fzP A Q cQ jR w IB w & url=https% 3A % 2F% 2Fpxhere.com % 2Fen% 2Fphoto% 2F1127502& psig=A O vV aw 3sS tfv7G 2P lO xkpA B thfvv& ust=1507297722839383
10© S c a le d A g i le , In c .
Or do we….
11© S c a le d A g i le , In c .
Hypothesis Driven Development
Hypothesize (Plan)
Build (Do)
Measure (Check)
Learn (Adjust)
12© S c a le d A g i le , In c . 12© S c a le d A g i le , In c .
Mistake #4 – Let’s Wait With Integrations
13© S c a le d A g i le , In c .
My Marshmallow Challenge
14© S c a le d A g i le , In c . 14© S c a le d A g i le , In c .
Mistake #5 – Deploying IS Releasing
15© S c a le d A g i le , In c .
Deploy = Release
https://commons.wikimedia.org/wiki/File:Senghenydd_pit_disaster_10.jpg
16© S c a le d A g i le , In c . 16© S c a le d A g i le , In c .
Mistake #6 – Ignoring Culture
17© S c a le d A g i le , In c .
The DevOps gap
https://dv.m.wikipedia.org/wiki/ ������ :Tug_of_war_2.jpg
18© S c a le d A g i le , In c .
With great power
https://pixabay.com/en/spider-man-superhero-character-1749191/
19© S c a le d A g i le , In c .
Who is DevOps?
Dev Ops
Development
Operations
Business
SecurityArchitecture
Compliance
…
20© S c a le d A g i le , In c . 20© S c a le d A g i le , In c .
Mistake #7 – Unwillingness to invest in infrastructure
21© S c a le d A g i le , In c .
Architected for speed
22© S c a le d A g i le , In c . 22© S c a le d A g i le , In c .
Mistake #8 – It’s DevOps OR Agile
23© S c a le d A g i le , In c .
Do you remember the whoosh?
24© S c a le d A g i le , In c .
What happens when we forget one side?
25© S c a le d A g i le , In c . 25© S c a le d A g i le , In c .
Mistake #9 – Not measuring enough
26© S c a le d A g i le , In c .
Measure the results
https://pixabay.com/en/belly-body-calories-diet-exercise-2354/
27© S c a le d A g i le , In c . 27© S c a le d A g i le , In c .
Step 1 – Visualize the current state
28© S c a le d A g i le , In c .
Value Stream mapping – identify the steps – customer example
Build PlanningUnit TestCode
CoverageIntegration
Test
Review +Deploy to Dev
FunctionalTest
DeployTo Test
Smoke Test
Deploy to UAT
AcceptanceTest
CreateTicket
DeployTo Stage
29© S c a le d A g i le , In c .
Build
Value Stream mapping – identify the people
PlanningUnit TestCode
CoverageIntegration
Test
Review +Deploy to Dev
FunctionalTest
DeployTo Test
Smoke Test
Deploy to UAT
AcceptanceTest
CreateTicket
DeployTo Stage
Dev [Auto]
Dev [Auto]
Dev [Auto] Dev
[Auto]
Dev [Button]
Dev/Test DevDev/Test
DevOpsBusiness
DevOps Magic
30© S c a le d A g i le , In c .
Value Stream measurements
Lead time (LT) – Time from when work was ready after the previous station to completion
Process time (PT) – Actual value-added work
Percent complete and accurate (%C&A) – Percent of work that the next station could process as-is
Build PlanningUnit TestCode
CoverageIntegration
Test
Dev [Auto]
Dev [Auto]
Dev [Auto]
Dev [Auto]
31© S c a le d A g i le , In c .
Value Stream mapping – measure the steps
Build PlanningUnit TestCode
CoverageIntegration
Test
Review +Deploy to Dev
FunctionalTest
DeployTo Test
Smoke Test
Deploy to UAT
AcceptanceTest
CreateTicket
DeployTo Stage
PT: 3mLT: 8 m%C%A: 80%
PT: 5mLT: 5m%C%A: 75%
PT: 1mLT: 1m%C%A: 80%
PT: 30mLT: 80m%C%A: 80%
PT: 60mLT: 90m%C%A: 60%
PT: 120mLT: 360m%C%A: 90%
PT: 5mLT: 365 m%C%A: 95%
PT: 10mLT: 90 m%C%A: 95%
PT: 10mLT: 370m%C%A: 90%
PT: 30mLT: 20,160m%C%A: 99%
PT: 60mLT: 2880m%C%A: 95%
PT: 10mLT: 4320m%C%A: 99%
32© S c a le d A g i le , In c .
Value Stream map – calculate the total metrics
Activity ratio = PT/LTRolled %C&A = %C&A1 * %C&A2 * %C&A3 * 100
Total PT = 455 minutes
Total LT = 41,900 minutes
Activity ratio = 10.8%
Rolled %C&A = 13%
Build PlanningUnit TestCode
CoverageIntegration
Test
Review +Deploy to Dev
FunctionalTest
DeployTo Test
Smoke Test
Deploy to UAT
AcceptanceTest
CreateTicket
DeployTo Stage
PT: 3mLT: 8 m%C%A: 80%
PT: 5mLT: 5m%C%A: 75%
PT: 1mLT: 1m%C%A: 80%
PT: 30mLT: 80m%C%A: 80%
PT: 60mLT: 90m%C%A: 60%
PT: 120mLT: 360m%C%A: 90%
PT: 5mLT: 365 m%C%A: 95%
PT: 10mLT: 90 m%C%A: 95%
PT: 10mLT: 370m%C%A: 90%
PT: 30mLT: 20,160m%C%A: 99%
PT: 60mLT: 2880m%C%A: 95%
PT: 10mLT: 4320m%C%A: 99%
33© S c a le d A g i le , In c . 33© S c a le d A g i le , In c .
Step 2 – Identify the impediments to flow
34© S c a le d A g i le , In c .
Build PlanningUnit TestCode
CoverageIntegration
Test
Review +Deploy to Dev
FunctionalTest
DeployTo Test
Smoke Test
Deploy to UAT
AcceptanceTest
CreateTicket
DeployTo Stage
PT: 3mLT: 8 m%C%A: 80%
PT: 5mLT: 5m%C%A: 75%
PT: 1mLT: 1m%C%A: 80%
PT: 30mLT: 80m%C%A: 80%
PT: 60mLT: 90m%C%A: 60%
PT: 120mLT: 360m%C%A: 90%
PT: 5mLT: 365 m%C%A: 95%
PT: 10mLT: 90 m%C%A: 95%
PT: 10mLT: 370m%C%A: 90%
PT: 30mLT: 20,160m%C%A: 99%
PT: 60mLT: 2880m%C%A: 95%
PT: 10mLT: 4320m%C%A: 99%
Value Stream map – Where are the problems
Total PT = 455 minutes
Total LT = 41,900 minutes
Activity ratio = 10.8%
Rolled %C&A = 13%
35© S c a le d A g i le , In c . 35© S c a le d A g i le , In c .
Step 3 – Create a future state
36© S c a le d A g i le , In c .
Value Stream mapping – The future state
Build PlanningUnit TestCode
CoverageIntegration
Test
Review +Deploy to Dev
FunctionalTest
DeployTo Test
Smoke Test
Deploy to UAT
AcceptanceTest
CreateTicket
DeployTo Stage
PT: 3mLT: 8 m%C%A: 80%
PT: 5mLT: 5m%C%A: 75%
PT: 1mLT: 1m%C%A: 80%
PT: 30mLT: 80m%C%A: 80%
PT: 60mLT: 90m%C%A: 60%
PT: 120mLT: 360m%C%A: 90%
PT: 5mLT: 365 m%C%A: 95%
PT: 10mLT: 90 m%C%A: 95%
PT: 10mLT: 370m%C%A: 90%
PT: 30mLT: 20,160m%C%A: 99%
PT: 60mLT: 2880m%C%A: 95%
PT: 10mLT: 4320m%C%A: 99%
TDD
PT: 5mLT: 5m%C%A: 99%
PT: 20mLT: 30m%C%A: 99%
FeatureToggles
BDD
37© S c a le d A g i le , In c .
Example from the DevOps class
38© S c a le d A g i le , In c . 38© S c a le d A g i le , In c .
Step 4 – Prioritize the opportunities
39© S c a le d A g i le , In c .
What’s the right thing to work on?
40© S c a le d A g i le , In c . 40© S c a le d A g i le , In c .
Step 5 – Start implementing
41© S c a le d A g i le , In c .
Insert into the backlog and into PI Planning
42© S c a le d A g i le , In c .
Takeaways
4Understand the 9 deadly mistakes
4Focus on Release on Demand
4Visualize the current flow of value, and identify potential bottlenecks
4Imagine the future state
4Prioritize the work, and start implementing
4Keep assessing and improving
43© S c a le d A g i le , In c .© S c a le d A g i le , In c . 43
Thank you!