Scrum template (2.3)
Introduction
This template is designed to show how Mingle can be used to maintain (and report on) on Scrum projects. The template has been set up with an initial set of cards to illustrate the workings of the dashboards and transitions at Release 1 Sprint 2.
There are
- 115 cards created
- 7 different cards types
- 18 cards properties
- 10 cards transitions
- 2 different cards trees
- a burn down chart on the project overview page
Card and property set-up
This project has seven different cards types:
- Release
- Sprint
- Story
- Task
- Defect
- Feature
- Epic Story
'Story' and 'Task' are the most used card types in this project.
To understand the relationships between different card types see the card trees section below.
Card properties
| Property name | Property type and description |
|---|---|
| Accepted On | Date |
| Added On | Date |
| Analysis Completed On | Date |
| Days Open | Formula |
| Defect Status | Managed text list |
| Development Completed On | Date |
| Development Started On | Date |
| Estimate - Planning | Managed number list |
| Fixed On | Date |
| Owner | Individual assigned to a work item Automatically generated from the team list |
| Priority | Managed text list |
| Reported On | Date |
| Status | Managed text list |
| Task Estimate | Managed number list |
| Task Status | Managed text list |
| Testing Completed On | Date |
| Testing Started On | Date |
Of the 17 card properties in this template many of them use date as a value. For example, 'Accepted on, 'Added on', and 'Analysis Completed On' all are date properties.
This template shows the use of a formula property. 'Days Open' is 'Fixed On' - 'Reported On' where 'Fixed On' and "Reported On' are date properties.
Transitions
Transitions in this template are used in much the same way as transitions in the XP template as they allow transitions from one 'Status' value to another 'Status' value.
Trees
- Feature tree - shows the relationship between 'Epic Story', 'Feature' and 'Story'. A Feature tree such as this one can be very useful for describing how larger pieces of functionality are split into smaller units of work such as stories and help visualize the complexity of a project.
- Planning tree - shows the relationship between 'Release', 'Sprint', 'Story', 'Task' and 'Defect' card types. A standard practice in Scrum is to break down and estimate larger 'Story' cards as multiple 'Task' cards. This tree shows how an aggregate formula property can be used to calculate this as 'Estimate - Task' is the sum of each 'Task' card type's 'Estimate' property per 'Story'.
Charts and tables
This template has a comprehensive 'Burn down chart' which tracks planned scope to completed scope in the current Release. Date properties are used to track these data. The XP template draws the burn up chart using card relationship properties.
In 2.1 Scrum template, the chart 'Dependency Chart' is newly added. This chart used card relationship property, 'Depend On', to track dependencies between cards.
Favorites and tabs
Project and sprint backlog are fundamentals of Scrum scope tracking and this template indicates how favorites and tabs can be used to visualize a Project and Sprint backlog.
Project Backlog tab - this shows 'Story' cards that are yet to be planned to a Release
Sprint Backlog tab - this shows 'Story' cards that have been planned for 'Sprint 2' and their current 'Status'.
