CloudMunch platform provides the metrics not only at project level but also at instance level. Such wide-eyed scope of metrics would prove of immense help to the DevOps team, as it now enables the team to get an idea where one project stands in comparison with another at a global level. Instance level Insights support is provided to various tools such as JIRA and Jenkins.
CloudMunch provides metrics in the form of view cards and key metrics for a range of tools. In the case of JIRA, Cloudmunch provides view cards on Time, Velocity, Scope, Risk and Defect details at project level. So, if CloudMunch is configured for a specific project of JIRA, those above mentioned metrics will be rendered by it. Along with those views, CloudMunch provides the key metrics such as Defect Density, Project Completion Percent, Velocity Volatility.
However, in cases, where, we might require certain metrics for all the configured projects in JIRA. As a user who is interested in the cost, I may like to know the project where the amount of time spent on dev is more, comparing to any other project. As a user who is interested in the quality, I may like to know the project where the amount of time is most spent on tackling the defects. I may also want to know where each project configured in JIRA stands with respect to other project or overall average metrics at instance level. For example, if an average number of stories assigned to a developer is 10 at instance level, I may be interested in knowing where each project stand with respect to this average value.
I hope that you would have got an idea about how useful these instance level metrics will be, in order to understand the nature of individual projects by comparing it with instance level metrics and so better compare one project with another. Cloudmunch Insights provides the view cards at instance level that provide details on Defects Over Stories, Open Defects Percent, Average Stories Per User, Estimation Deviation, Time Spent On Defects, Time Estimation By Story points along with key metrics such as Stories closed in previous week, Defects closed in previous week, total number of closed stories across all projects, total number of closed defects across all projects, Top project by completion, Project with least open defects, Project by team size, Average stories being handled by user, Average defects per story, Total estimated time, Total time spent on stories, Total time spent on stories during last week, Total story points completed last week, Estimate deviation, Percent of Time spent on Defect handling, Average time estimated by story points, Total time spent on defects, etc.
While the list of key metrics and view card details might seem interesting and exhaustive, the list would grow continuously and soon, CloudMunch will provide much more such metrics at instance level. Sign up for CloudMunch to get more on!