creating a pull for devops in an agile transformation
Post on 14-Apr-2017
346 Views
Preview:
TRANSCRIPT
Visualizing the Demand For DevOpsThoughts from the field about how to identify the need for
DevOps and how to use DevOps in a large agile transformation
tim@leadingagile.com678-814-2169
www.leadingagile.comtwitter.com/timswise
facebook.com/leadingagilelinkedin.com/in/timwise
Tim Wise
Why Agile Works
Team
4
Why Agile Works
Team
5
Accountability
Why Agile Works
Team
User Story
User Story
User Story
User Story
User Story
User Story
User Story
6
Clarity Accountability
Why Agile Works
Team
Database
Report
Screen
User Story
User Story
User Story
User Story
User Story
User Story
User Story
Clarity AccountabilityMeasureable
Progress
7
Why Agile Works
Team
Database
Report
Screen
User Story
User Story
User Story
User Story
User Story
User Story
User Story
8
Why Agile Fails
Team
Database
Report
Screen
User Story
User Story
User Story
User Story
User Story
User Story
User Story
Lack of Clarity
9
Why Agile Fails
Team
Database
Report
Screen
User Story
User Story
User Story
User Story
User Story
User Story
User Story
Lack of Clarity
Lack of Accountability
10
Why Agile Fails
Team
Database
Report
Screen
User Story
User Story
User Story
User Story
User Story
User Story
User Story
Lack of Clarity
Lack of AccountabilityLack of
Measureable Progress
11
Why Agile Fails
HOW DO WE SOLVE FOR THESE?
Team
Database
Report
Screen
User Story
User Story
User Story
User Story
User Story
User Story
User Story
Clarity AccountabilityMeasureable
Progress
13
Team
Database
Report
Screen
User Story
User Story
User Story
User Story
User Story
User Story
User Story
Structure AccountabilityMeasureable
Progress
14
Team
Database
Report
Screen
User Story
User Story
User Story
User Story
User Story
User Story
User Story
GovernanceMeasureable
ProgressStructure
15
Team
Database
Report
Screen
User Story
User Story
User Story
User Story
User Story
User Story
User Story
GovernanceStructure
16
Metrics
Product Delivery
STRUCTURE
Team Team Team Team
TeamTeamTeam
Product & ServicesTeams
Team Team Team
Team Team Team Team
TeamTeamTeam
Product & ServicesTeams
ProgramTeams
Team
Team Team Team
Team Team Team Team
TeamTeamTeam
Product & ServicesTeams
ProgramTeams
PortfolioTeams
GOVERNANCE
Team
Team Team Team
Team Team Team Team
TeamTeamTeam
Product & ServicesTeams
ProgramTeams
PortfolioTeams
Product & ServicesTeams
Scrum
Team
Team Team Team
Team Team Team Team
TeamTeamTeam
ProgramTeams
PortfolioTeams
Product & ServicesTeams
ProgramTeams
PortfolioTeams
Scrum
Kanban
Team
Team Team Team
Team Team Team Team
TeamTeamTeam
Product & ServicesTeams
ProgramTeams
PortfolioTeams
Scrum
Kanban
KanbanTeam
Team Team Team
Team Team Team Team
TeamTeamTeam
METRICS
Product & ServicesTeams
ProgramTeams
PortfolioTeams
Scrum
Kanban
Kanban
• Backlog Size• Velocity• Burndown• Escaped Defects• Commit % Ratio• Acceptance % Ratio• Scope Change
• Cycle Time• Features Blocked• Rework/Defects
• Cycle Time• Cost/Value• RIO/Capitalization
P A
E
C
Start
BC1
BC2
BC4
BC5
BC3
Lean / Agile
Ad-Hoc
Agile
Learning Oriented
Convergence
Pred
icta
bilit
y Adaptability
Emergence
Predictability– Form complete agile teams, create clear backlogs, and create product roadmaps.
Small Batches– Begin quarterly release planning, implement technical practices and introduce flow-based metrics..
Remove Impediments– Focus on legacy refactoring, DevOps and Continuous Integration and Deployment.
Increase Local Autonomy– Adaptive localized governance. Funded capabilities.
BC 4
BC 1
BC 3
BC 2
BC 5
Learning Focus– Establish fully decoupled teams with outcome-based accountability, innovation focus.
P A
E
C
Start
BC1
BC2
BC4
BC5
BC3
Lean / Agile
Ad-Hoc
Agile
Learning Oriented
Convergence
Pred
icta
bilit
y Adaptability
Emergence
Pull ApproachUsing Product Development
P A
E
C
Start
BC1
BC4
BC5
BC3
Lean / Agile
Ad-Hoc
Agile
Learning Oriented
PredictableMVP Focus
Convergence
Pred
icta
bilit
y Adaptability
Emergence
BC2
What has Product Development Seen So Far?
Predictability
Increased Quality and Throughput
Now What Do We Want?
Faster Time To MarketCost Reduction
Higher Quality and Predictability
Team
Database
Report
Screen
User Story
User Story
User Story
User Story
User Story
User Story
User Story
GovernanceStructure
40
Metrics
Team Team Team
Team Team Team Team
TeamTeamTeam
Product & ServicesTeams
ProgramTeams
PortfolioTeams
BC 3 Automated Testing
DevOps
Team Team Team
Capability Capability Team Team
TeamTeamTeam
Product & ServicesTeams
ProgramTeams
PortfolioTeams
BC 4
DevOps
Systematic Decoupling
Team Team Team
Capability Capability Team Team
TeamTeamTeam
Product & ServicesTeams
ProgramTeams
PortfolioTeams
BC 4
DevOps
Release Train -> Release Pipeline
Capability Teams
ProgramTeams
Portfolios
Service Teams
Data, UX/UI, other Teams
Dev Ops
Program Team
Push Approach – Way 2
P A
E
C
Start
BC1
BC4
BC5
BC3
Lean / Agile
Ad-Hoc
Agile
Learning Oriented
FullyDecoupleTeams
Convergence
Pred
icta
bilit
y Adaptability
Emergence
BC2
What has Product Development Seen So Far?
Nothing
Team
Database
Report
Screen
User Story
User Story
User Story
User Story
User Story
User Story
User Story
GovernanceStructure
The End State Is the Backlog
49
Metrics
Team
Team Team Team
Capability Capability Team Team
TeamTeamTeam
Product & ServicesTeams
ProgramTeams
PortfolioTeams
BC 1
DevOps
Predictability and Automation
Team
Team Team Team
Team Team Team Team
TeamTeamTeam
Product & ServicesTeams
ProgramTeams
PortfolioTeams
BC 1 Predictability and Automation
DevOps
Team
Capability Capability
Team
Product & ServicesTeams
ProgramTeams
PortfolioTeams
BC 2 Isolation and Reduction of Batch
Team
Team Team
Team Team
TeamTeam
DevOps
Team
Capability Capability
Team
Product & ServicesTeams
ProgramTeams
PortfolioTeams
BC 4 Breaking Change -> Release Pipeline
Team
Team Team
Team Team
TeamTeam
DevOps
Team
Capability Capability
Team
Product & ServicesTeams
ProgramTeams
PortfolioTeams
BC 1 Organize the Next Hot Mess
Team
Team
DevOps
Team Team
CapabilityTeam
TeamTeam
DevOps
Which Is Better?
Thanks!@timswise
tim@leadingagile.comhttps://www.linkedin.com/in/timwise
top related