Do you have a Report Card!
Raminder Rathore
IT Practitioner | AI-driven DevOps | Researcher | Blogger | CDF Ambassador | Community Lead
What clicks your mind the moment you hear "Report Card"? Most of us would relate this to our School Report Cards. The intention behind a report card was very clear. It acted as a mirror to our performance, helping us setup a bench mark and target for better results next time.
Inline to this thought, organizations too have report cards now!! We Dashboards that reflect our scores. These scores or say metrics help us view our current progress, compare values against the benchmark and target for improvement in the next iteration. There are various metrics that are defined at Executive and Program levels and focus on measuring productivity, quality, cost and efforts. These metrics are important to measure our success while adopting DevOps Ways of Working.
To share few metrics that are a good start to monitor improvements-
1) Effort saved with test automation
2) % of rollbacks from production
3) Technical Debt - Quality of Code produced
4) Number of releases / duration
5) % test coverage, and so on...
The definitions and benchmarks for these metrics are defined by the organization itself. And these are periodically reviewed as part of the Continuous Improvement Journey.
Associate Principal Engineer, DevOps - Technology
6 年Just to add here, incorporation of trend analysis would even do a value addition from a BU head POV, along with the existing dashboard, which is again offered by open-source DevOps tool.