Hot answers tagged

17

Great question! Most of us know investing in DevOps practices is a highly worthwhile pursuit for myriad reasons; we don't often justify DevOps on the impact to the bottom line alone, though. Note: this is something of an opinionated question, and my answer is likewise, opinionated. Tensibai wisely suggested we find the right metrics, and he used time-to-...


12

The key metric for a DevOps pipeline is Cycle Time (also called Lead Time). This is the time it takes for a change (or a change request, tracking all the way to the inception of the idea). The best illustration of this concept I know of is from the book "The Goal", which talks about it in a manufacturing context. Deployment Frequency is useful as well. ...


8

Captain obvious : by reducing time to market and defects on releases. To extend on this one liner, the usual pitfall is being an organization change without any reference. Engaging a culture or organization change implies some expense to train and introduce people to this new method, this have a cost in training but also imply a loss in productivity as ...


1

Late to the game here but thought I'd chime in. You can't manage what you don't measure, so for starters, here are the key metrics devops teams should be tracking for incident response: Uptime % : total % of time available = [total time - downtime] / [total time] MTTR : mean time to resolution = [downtime] / [# incidents] MTTA : mean time to acknowledge = [...


Only top voted, non community-wiki answers of a minimum length are eligible