DevOps Metrics
从业务角度来看，公司希望更准确地度量其开发人员的生产力，原因如下:
- Monitoring progress over time
- Creation of benchmarks
- Rewarding top performers
- Determining resource allocation
- Identification of more productive development processes
框架是想法、概念和关系的简单总结，因此基于您的上下文、环境和团队，您可以选择一组您可以解释的指标，以确定团队是否在它应该在的地方。
DORA
DevOps Research and Assessment.
Speed metrics
Deployment frequency: This measures how often a team deploys code to production.
- Low performance: once per month - once per semester. (inadequate integration, lack of automation.)
- Medium performance: once per month - once per week.
- High performance: daily for multiple times per day.
Lead time for change: This measures the time it takes from the moment a code change is made until it is successfully deployed to production.
- Low performance: one - six months. (time-consuming manual testing, lack of automation.)
- Medium performance: one week - one month.
- High performance: less than one day.
Stability metrics
change failure rate: This metric measures the proportion of deployments that result in failures.
- Poor performance: 46% - 60%. (quality and reliability issues).
- Average performance: 15%-45%.
- High performance: 0% - 15%.
mean time to restore: This metric helps assess team’s ability to handle incidents and failures.
- Low performance: one week - one month. (lack of adequate monitoring and diagnostic tools).
- Medium performance: one day - one week.
- High performance: less than one day.
SPACE
S: Satisfaction and well-being
P: Performance
A: Activity
C: Collaboration and communication
E: Efficiency and flow
DevEx
Developer Experience: DevEx captures how developers feel, how they think, and how they value their work.
Feedback loops
perceptions:
- satisfaction with automated test speed and output.
- satisfaction with time it takes to validate a local change.
- satisfaction with time it takes to deploy a change to production.
workflows:
- time it takes to generate CI results.
- code review turnaround time.
- deployment lead time.
Cognitive load
perceptions
- perceive complexity of codebase.
- ease of debugging production systems
- easy of understanding documentation.
workflows
- time it takes to get answers to technical questions.
- manual steps required to deploy a change.
- frequency of documentation improvements.
Flow state
perceptions
- perceived ability to focus and avoid interruptions.
- satisfaction with clarity of task or project goals.
- perceived disruptiveness of being on-call.
workflows
- number of blocks of time without meetings or interruptions.
- frequency of unplanned tasks or requests.
- frequency of incidents requiring team attention.