This is a proposal, still in draft phases of the steps a team must take in order to reach full autonomy. Also which processes, metrics and improvements one should focus in order to ascend to the next phase.
- Clear and achievable sprint goals
- Bugs separated from sprint work
- Strong implementation of framework
- Actionable points with due date
- Cycle time
- Lead time
- Repair time
- Reducing Roll overs
- Backlog exists for at least 3 sprints
- Small increments to deliver
- No roll overs
- Oncall service for Bugs support
- WIP limitations
- Meetings with meeting notes and action points
- Build and integration frequency
- Release Frequency
- Release stabilization period
- Defect Trend
- Technical Debt
- Production Incident Trend
- Stability of delivery
- Reducing bugs reported
- Adapt framework to the needs
- Stable story/feature size
- Continuous Deployment
- Legacy refactoring is constant
- Feature Usage Index
- Installed version index
- Active code branches
- Time to merge
- Context switching
- Continuous automated delivery
- Reduction of tech debt
- Release can happen at any moment
- Changes can arrive at any moment
- Product Cost Ratio
- Customer satisfaction
- Customer usage index
- Autonomy and accountability
- Projects are initiated by the team
- Design sprints / Design thinking
- Team has funding and decides on how to use it
- WHY is clear, WHAT can change and HOW is always up for debate
- Revenue per Employee
- Employee Satisfaction
- On the North Star metric
- Finding new WHATs to match our WHY