- Top 11 Bottlenecks That Undermine Success of the DevOps
- How Do I Find and Fix DevOps Bottlenecks in Enterprise Software Delivery?
- How to break through your DevOps bottlenecks
- Get the right metrics – are you measuring right thing?
- Do you understand how value flows across the process?
- Can you easily obtain real-time metrics across the process?
- Are you able to produce accurate traceability and other performance reports?
The four categories for measuring outcomes:
- Time - lead time to deliver business value
- Productivity - business value in terms of stories
- Cost - cost per story point
- Quality - mean time to resolution (MTTR)
Theory of constraints
- Eliyahu Goldratt’s book The Goal in 1984
- Theory of Constraints
- Getting real with the theory of constraints
Taking a scientific approach to identify the primary factor limiting performance, then working on it until it’s no longer a problem. These three tips will get you off to a good start:
- Identify your bottleneck
- Develop and implement a targeted solution
- Identify – what part of the process limits the rate at which goals are achieved?
- Exploit – make quick improvements to throughput using existing resources.
- Subordinate – ensure all actions are geared towards eliminating the bottleneck, everything else is deprioritised
- Elevate – if the above steps don’t help, deploy additional resource. Attack the constraint aggressively until it’s resolved.
- Repeat – once the constraint is removed, move on to the next problem causing a bottleneck elsewhere.
- Optimise for continuous improvement
Value stream mapping
- What’s wrong with your value stream mapping
- How to increase enterprise collaboration and speed in your DevOps pipeline
- DevOps and value stream mapping: Why you need metrics
- How to defrag your DevOps value stream
- Why value stream management success hinges on flow, governance
- How to monitor business goals with value stream management
- How to Use Value Stream Mapping in DevOps
- DevOps process: Visibility of work in the value stream
- Value Stream Mapping for Software Delivery
- The 8 Wastes of Lean
- What is value stream mapping?
3 key components:
- VA (or PT) - Value added time (or Process time) is the amount of time that a team actually spends working on the project.
- LT - Lead time represents the total time it takes a person or team to complete a task—it is the combination of value added and non-value added.
- %C/A - % Complete/accurate - his is the percentage of information-based work that is complete and accurate the first time and requires no re-work by downstream processes.
Build your own data-driven stream by following these four steps:
- Map out your as-is DevOps stream
- Identify waste
- Build your to-be DevOps stream
- Communicate change to your organization
Common pitfalls with work visibility:
- Overestimating the state of organizational knowledge
- Failing to map the entire value stream
- Focusing on the wrong areas for improvement
- Not granting authority to make changes