XP Template (2.0)
Introduction
This Extreme Programming (XP) template is currently set-up to show the status of an XP project at Iteration 5 of Release 1.
There are:
- 119 cards created
- 6 different cards types
- 13 cards properties
- 10 cards transitions
- 2 different cards trees
- a variety of charts and tables on the project overview page
Card and property set-up
This project has six different cards types:
- Defect
- Epic
- Feature
- Issue
- Story
- Task
The most widely used card type in this project is the 'Story'.
To understand the relationships between different card types see the card trees section below.
Card properties
| Property name | Property type and description |
|---|---|
| Date Added | Date |
| Estimate | Managed number list |
| Group | Managed text list |
| Iteration - Accepted | Managed number list |
| Iteration - Added | Managed number list |
| Iteration - Analysis Completed | Managed number list |
| Iteration - Dev Completed | Managed number list |
| Iteration - Scheduled | Managed number list |
| Owner | Automatically generated from the team list |
| Priority | Managed text list |
| Release | Managed number list |
| Size | Managed text list |
| Status | Managed text list |
Each card type has a number of different properties. For example, 'Story' card types have 13 card properties. Many of the card properties in this project are managed text or managed number lists such as the properties 'Iteration - Added' (managed number list) and 'Priority' (managed text list).
Project variables
This template uses a new Mingle 2.0 feature called project variables. There are two project variables used, (Current Iteration) and (Current Release). Both project variables have been used in card transitions and used to create reporting charts in this template project.
Transitions
Ten different card transitions have been created in this project. Five of these transitions move 'Story' cards between different card property values.
For example, the transition 'Add Story To Current Release' can be used by any team member to give a 'Story' an 'Iteration - Added' property value of (Current Iteration) and 'Release' property (Current Iteration). (Current Iteration) in this example is a project variable.
While all the transitions in this template are open to all team members at the moment it may be that for certain transitions you may want to limit who can use a transition. For example, 'Story Dev Complete' which moves a 'Story' from 'Status' property value of 'Dev In Progress' to value of 'Development Complete' and at the same time sets the property 'Iteration - Dev Completed' to the (Current Iteration) and property 'Owner' as (not set) could be limited to just let team members who are Developers use this transition.
Trees
There are two card trees in this template. These card trees have been set-up to show the relationships between the different card types in this project.
- Story tree - shows the relationship between the card types: 'Epic', 'Feature' and 'Story'. It has two relationship properties: 'Story Tree - Epic' and 'Story Tree - Feature'. It also has two aggregate properties: 'Total Epic Points' which is a sum of all the 'Story' cards 'Estimate' property values per 'Epic' card and 'Total Feature Points' which is a sum of all the 'Story' cards 'Estimate' property values per 'Feature' card.
- Task list - shows the relationship between 'Story' card types and 'Task' card types. It has a single relationship property: 'Task list - Story' which indicates which 'Story' card a 'Task' card is related to. There is a single aggregate property 'Total Task Estimate' which is a sum of all the 'Task' card 'Estimate' property values per 'Story' card.
Charts
This burn-up chart is created using the new Mingle 2.0 macro called data-series-chart.
The project overview page for this project has a number of different MQL charts displayed on it. The most noteworthy of which is the 'Story progress per iteration' burn up chart which shows story progress per iteration towards the total size of scope for the Release up to Iteration 8. It shows the amount of 'Story' cards per iteration that have a 'Status' property value of 'Ready for Development', 'Development Complete' and 'Accepted' and also plots the trend (regression line) for each series.
Another macro used on this page is the ratio-bar-chart which shows the amount of 'Story' cards that has the 'Status' property value of 'Accepted' per 'Feature' card. This is included as it shows the percentage for functionality completed in each 'Feature' area. Defect reporting is represented in two formats on the overview page. The first is a MQL table filled in with value queries of the total 'Estimate' of 'Defect' card types in various 'Status' values. The second is a data-series-chart which shows the number of defects added and completed per Iteration.
Favorites and tabs
A selection of favorites and tabs have been saved for this template. Each favorite or tab shows a different view on the data in this template.
