What:
As a developer and product owner, I would like to track the work being done in a sprint to understand the likelihood of the work being completed by the end of the Sprint.
To be able to do so, the burn-up chart must show the sub-statuses, not only the top-statuses.
A product backlog consists of larger items, like Epics and Stories.
Stories are broken down to tasks that the developers works on in a Sprint.
Why:
Work item are often broken down into many child items and that is where the actual work is being done.
Tracking the main items in the burn-up chart is not so interesting as they will not be completed until the very end of the time period.
The interesting part is to track the "child" tasks.
Background info:
Hierarchy:
Kanban Board 1: Product Backlog: Epics broken into Stories. (for PO and Stakeholders)
Kanban Board 2: Sprint: Stories broken into tasks. (for developer team and PO)
The Epic, Stories and Tasks are linked by using the powerful synced copy feature.
Wish: Create a burn-down chart showing only what is taken into the Sprint, and showing progress of the sub-statuses.
This data is already present in most other calculations, charts and boards in Teamhood, but the most valuable presentation for a Scrum Team is the burn-up chart
The Custom Chart widget has the option to choose the particular statuses of interests, but unfortunately it does not have a burn-up or burn-down option. Just bar and donut.
Please authenticate to join the conversation.
Open
Feature Requests
6 months ago

Annette Hopland
Get notified by email when there are changes.
Open
Feature Requests
6 months ago

Annette Hopland
Get notified by email when there are changes.