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)
Does your team need an operational reset? Ever feel like your team has too many meetings? Or don't know why you're even having a meeting? Ever get the dreaded Zoom fatigue? Are the r...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events