Intelligent CIO Europe Issue 41 | Page 85

FINAL WORD
Usage statistics are also useful as you release new updates over time . A dip in usage can suggest that you implemented a change that ’ s unappealing to the end-user . A competent DevOps team will infuse measures and controls to quickly correct dips in usage caused by new features .
3 . Number of tickets
Users provide feedback by submitting tickets to your support team , and changes can be implemented between coding and tests in a DevOps pipeline . Logistics around this DevOps metric should be kept simple – you don ’ t want users submitting tickets about a poor ticketing system . Third-party tools commonly used to track tickets and their life cycles are the smartest option . This might cost more , but less time and effort should also be considered . ones . One way to keep on top of this is with a graph of tickets vs . time as it helps to focus on the trend and not just the tickets themselves .
4 . Commit count
Commits are changes sent to the main source code file using a version control system ( VCS ), such as GitHub . The more commits your team is recording , the more productive they are generally . However , a commit is only truly useful when senior developers have approved it , and therefore approved commits matter much more .
Any VCS should allow you to count the total commits completed in any given period . This can be a source of inspiration , as typically developers with more commits inspire the rest of their team to speed up .
Your DevOps team can focus on keeping the system fresh by submitting internal tickets . However , they ’ re naturally of lower priority than externally generated
Low commits can also reveal why your application versioning is slow , enabling managers to identify and support the developers with the lowest commits .
www . intelligentcio . com INTELLIGENTCIO EUROPE 85