This presentation was used to start a conversation with the Atlanta DevOps community around patterns for introducing DevOps in large organizations. During the session, I presented findings from coaches around the US.
Creating a pull for DevOps in an Agile Transformation
1. Visualizing the Demand For DevOps
Thoughts from the field about how to identify the need for
DevOps and how to use DevOps in a large agile transformation
30. 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.
41. Team Team Team
Team Team Team Team
TeamTeamTeam
Product &
Services
Teams
Program
Teams
Portfolio
Teams
BC
3 Automated Testing
DevOps
42. Team Team Team
Capability Capability Team Team
TeamTeamTeam
Product &
Services
Teams
Program
Teams
Portfolio
Teams
BC
4
DevOps
Systematic Decoupling
43. Team Team Team
Capability Capability Team Team
TeamTeamTeam
Product &
Services
Teams
Program
Teams
Portfolio
Teams
BC
4
DevOps
Release Train -> Release Pipeline
50. Team
Team Team Team
Capability Capability Team Team
TeamTeamTeam
Product &
Services
Teams
Program
Teams
Portfolio
Teams
BC
1
DevOps
Predictability and Automation
51. Team
Team Team Team
Team Team Team Team
TeamTeamTeam
Product &
Services
Teams
Program
Teams
Portfolio
Teams
BC
1 Predictability and Automation
DevOps
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.