ScrumDo has a dynamic reporting engine that will only continue to become increasingly more powerful as we continue our mission of building better teams and organizations.
As I write this, ScrumDo has 7 standard reports with several options for customizing them to your needs:
- Cumulative Flow Diagram
- Lead Time Histogram
- Burn Ups, Burn Downs, Stacked
- Aging Report
- Blocker Clustering
- Open Blockers
- Blocker Frequency
TIP: CUSTOMIZE REPORTS: When you're customizing a report, remember to hit the refresh button in the top right-hand corner of the report after setting your selections.
TIP: FAVORITES: You can favorite any of thees reports and add them to your personal or workspace(team) dashboards. You can simply FAVORITE a report by
You have options to run with absolute or relative datesS
Favorite reports may be access from the board or can be added to the dashboards.
Let's take a look at each report in more detail.
Cumulative Flow Diagram
The Cumulative Flow Diagram (CFD) is a visual reporting mechanism used extensively in Kanban (a Lean-Agile framework). When you create your visual workspace boards in ScrumDo, you're essentially defining the queuing system through which your work flows.
CFDs allow teams (or organizations) visualize their workflow over time. This temporal view of activity improves our ability to see potential problems before they arise.
ScrumDo's CFD Report has several filters and steps enabling you to customize your report (see the example below). For more advanced users, we recently added the CFD Range Tool (great for calculating slope, velocity, and other metrics dictated by Little’s Law).
Lead Time Histogram
The Lead Time Histogram is another visual reporting mechanism used extensively in Kanban. A histogram is a vertical bar chart that reflects the distribution of a particular set of data.
A Lead Time Histogram shows the distribution of work card lead times for all cards completed within the date range you select. So if your team completed 10 work cards in the span of a week, each card would have been "in progress" within your system for different times. One work card may have moved through your team in less than a day, another may have taken 7 days. The histogram displays the distribution of these times and allows us to easily discern where the bulk of a team's lead times for completed work lies.
Having an improved understanding of a team’s distribution pattern directly translates to better planning and forecasting capabilities.
NOTE: When generating this report, it's very important to select your appropriate start and end steps to get the specific data (and understandings) for which you're looking.
Burn Up and Burn Down Charts
Those familiar with the Scrum framework will recognize the burn-down chart as an effective visual display of the progress through an iteration, answering the question "how much work is left to do in this iteration?"
The burn-up chart is slightly more difficult to read but gives a good visual in seeing the change in work within an iteration. It helps answers the question "how has the total amount of work changed over the course of the iteration?"
The Aging Reports tell you how long cards (stories) stay in a certain state. We have 3 types of Aging Reports: Time in State Histogram, Aging Breakdown, and Relative Time charts.
Time in State Histogram lets you look at a single step or tag and see the distribution of how long cards spent in that step.
Aging Breakdown gives you a look at a multiple steps or tags compare how long cards spent in those steps.
Relative Time Chart depicts the relative amount of time cards spent in steps or tag.
We have 3 types of blocker reports: Blockers List, Blocker Clustering, and Blocker Frequency. It is important to understand what causes delays in delivering your work, and blockers are a key way of identifying these things.
Using these reports on a regular basis to examine the most current blockers will help teams to figure out the root causes and devise a strategy to eliminate or minimize their future recurrence.
The Blockers List Report lists the blockers yet to be resolved. The report shows the reason, the date the card was blocked, who blocked it, the card number, and other relevant information. Teams want to resolve blockers sooner rather than later. Having somebody (such as a Scrum Master) regularly run this report and ensuring the team addresses them is key to helping resolve delays in the delivery of your work.
The report on Blocker Frequency is going to show us specific blockers, distinguished by whether they are internal and external, and how often they occur. On the X-axis it lists the specific blockers and the Y-axis number of days.
In addition to these core reports, we have Dashboard Stats, Report Profiles, and Favorited Reports.
Stats are displayed in the Workspace Dashboard for any of your workspaces, and provide a quick overview of workspace status.
Report profiles allow users to change certain parameters relevant to how metrics are generated.
We have recently added a powerful boost to our User Interface, so if you need help navigating the UI, reach out to us through the orange pop-up in the lower right-hand corner.