May 2, 2018
Measuring DevOps Initiatives
At Attunix, we develop products and applications to help modernize our clients’ businesses. Depending on the client’s goals, existing infrastructure and overall strategy we may recommend a DevOps project. DevOps or development and operations is a relatively new concept. As a business discipline, it combines software development and IT operations. In order to stay competitive, IT operations must constantly evolve. When developers and operators work in silos, it can delay implementation, cause re-work or derail alignment internally.
How do you measure the success of a DevOps project? A recent TechRepublic article highlights an interview with DevOps author and professional, Nicole Forsgren about measuring and optimizing DevOps initiatives.
Set a Manageable Number of Initiatives
One of the mistakes Forsgren highlights is setting too many initiatives before launching a project. Setting just a few big-picture initiatives for the project helps your team focus and succeed. This also helps provide clarity on how the success of the project will be measured.
Software Delivery Performance
A key measurement of success for any DevOps project is software delivery performance. You want to deliver software with both speed and stability. Speed allows you to beat your competitors to market while stability prevents disturbing internal operations or customer experiences.
How does your DevOps project directly affect your organization’s performance as a whole? These goals may include profitability, market share or operational performance.
The initiatives for DevOps projects may not directly aim to improve employee satisfaction, but the results often create better, more efficient working environments that allow people to be more effective in their jobs and make room for increased work-life balance. Automation through DevOps can mitigate some of the manual legwork.
Forsgren emphasizes to measure anything effectively, stay focused on outcomes versus outputs. Secondly, focus on measurements globally versus locally. Measuring globally encourages teams and individuals to strive for the success of the entire project throughout the company versus on only on their proprietary tasks and pipelines.