Recently the company I work for has started working towards achieving some of the principles of DevOps.
https://services.google.com/fh/files/misc/state-of-devops-2019.pdf
If you're familiar with the concept or have actually managed to start measuring yourself and your work -- I'm interested in discussing how you've implemented methods to determine the core measurements of DevOps using JIRA.
Since these are technology agnostic concepts, every implementation is probably unique, but the crux of why you're doing X or Y is interesting.
For clarity, we're still working on this - but we pretty much have MTTR, Lead Time, and Cycle time nailed down, and deployment frequency mostly-nailed-down, but haven't tackled Change Failure Rate quite yet.
We have 10+ teams with unique workflows and processes and needed to come up with a relatively simple approach for measuring things that everyone could understand.
How have you decided to try it out? Anyone else out there herding cats?
(if you're not familiar with DevOps, that article is well worth checking out)
Recommended Learning For You
Level up your skills with Atlassian learning
Atlassian DevOps essentials
Learn how to build, automate, and improve DevOps processes used for the development and delivery of software and other digital products.
Tracking and improving DevOps metrics
Make informed decisions about current and future projects and deadlines to maximize your team's productivity and keep morale high.
Exploring Atlassian Cloud products for agile and DevOps
Coordinate a suite of Atlassian Cloud products for greater collaboration and trust, higher-quality solutions, faster releases, and more.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.