DevOps – Visibility & Insights: 1

DevOps is about continuous improvement in Business Outcome. What is your formula to define, measure and achieve this Business Outcome using DevOps? Are you really continuously improving Business Outcome from 0.8 to …. Say 0.9999?

Typical question from a Techno-Business Leader - My Teams do follow Agile practice &.... implemented DevOps as a paradigm. Good Automation, BUT need better visibility to continuously improve Software Value... 

Sometimes a similar question is asked in a different way, i.e. - how to improve our checklist for continuous improvement in business outcome using DevOps? 

Simple, Faster and Pointed Insight -

Our focus has been to identify various methods of continuous improvement in Business Outcome through pertinent Insight.

• Harvest right VISIBILITY for everyone in the team without interfering their working culture and practices.

Let the Team decide their actionable from this feedback. One of the examples can be :

• Provide pertinent information & visibility into Continuous Integration (CI)!!!

You get this visibility and insights through the DevOps tool usage across Dev & Ops by the team(s). Consider following harvested information & depiction

Considering number of builds “Today”, “Last 7 Days” & “Last 14 Days” mentioned above – Is there a need for better Continuous Integration (CI)? Can the improvement in CI practice will enable better understanding of XYZ (say Rework or experimentation ...)?

Way Forward

Similar questions can be posed when the Team is performing set of activities (while using associated tool) as part of another phase of CI/CD pipeline. In brief, Objective is to provide the much-needed feedback on the Teams' ‘Flow of Work’ & thereby providing a potent force-multiplier for improvement across Teams and organization at large. This must be done without hampering team performance, i.e. achieved with minimal distractions and interruptions.