minware Report Walkthrough
If this is your first time using minware or you want a more detailed tour before jumping in, this guide is for you. Here we will briefly talk about how to use each report.
(This walkthrough does not cover how to ingest data. Please see Source Integrations for guidance on initial data connection.)
To start with, it helps to think about software engineering productivity as a four-layer stack:
- Where people spend time
- The tasks accomplished in that time
- The projects completed by those tasks
- The business value that those projects unlock
These layers are largely independent of one another, but they all have to operate effectively to have a productive software organization.
minware’s reports are structured around each layer, with the goal of measuring best practices and helping you identify opportunities for improvement wherever they lie.
The walkthrough is divided up by report. We recommend reading about these top five reports it in the following order, but feel free to hop around if you want to learn more about a particular area:
- Time Allocation - Provides a high-level view of how people spend their time (layer 1) and whether that time was used productively.
- Sprint Trends - Shows how tasks flow through sprints based on their estimates (layer 2) and illustrates trends in delivery vs. commitments.
- Scorecard - Provides a comprehensive list of how well people follow best practices across all four layers of the productivity stack with specific, actionable insights about the most important areas to improve.
- Sprint Insights - Shows a detailed breakdown of all the activity that occurred during a particular sprint, both from a time and ticket/point perspective. This report is designed for teams to use during sprint retrospectives.
- Predictive Roadmap - Helps you plan out future projects and observe historical progress on a per-project basis (layer 3), with dynamic projections based on configurable team velocity.