You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Recently the company I work for has started working towards achieving some of the principles of DevOps.
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)