XP Template (2.3)
Introduction
This Extreme Programming (XP) template is currently set-up to show the status of an XP project at Iteration 5.
There are:
- 127 cards created
- 7 different cards types
- 12 cards properties
- 9 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
- Iteration
- Story
- Task
The most widely used card type in this project is the 'Story'.
Card properties
| Property name | Property type and description |
|---|---|
| Date Added | Date |
| Estimate | Managed number list |
| Group | Managed text list |
| Iteration - Accepted | Card |
| Iteration - Added | Card |
| Iteration - Analysis Completed | Card |
| Iteration - Dev Completed | Card |
| Iteration - Scheduled | Card |
| Owner | Automatically generated from the team list |
| Priority | Managed text list |
| Size | Managed text list |
| Status | Managed text list |
Each card type has a number of different properties. For example, 'Story' card types have 12 card properties. Many of the card properties in this project are managed text or managed number lists such as 'Priority' (managed text list).
Project variables
This template include a project variables called - (Current Iteration). This project variable is a card type project variable. The card type project variable can take any existing card in a project as a value. This project variable has been used in card transitions and used to create reporting charts such as the burn-up chart in this template project.
Transitions
Nine 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 'Schedule Story for Current Iteration' can be used by any team member to give a 'Story' an 'Iteration - Scheduled' property value of (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 and tables
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 estimated size of scope up to Iteration 7. It shows the size of 'Story' cards per iteration that have were 'Analysis Complete', 'Development Complete' and 'Signed Off' and also plots the trend (regression line) for each series. It was created using a data-series chart and card relationship properties such as 'Iteration - Added' and 'Iteration - Accepted'. These properties create relationships between the cards without the need for a tree and can be easily used to create burn-up charts.
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.
For example, the 'BA Story Wall' has been set-up to show the 'Story' card types scheduled for the 'Current Iteration' that have 'Status' property values of 'New', 'Open' or 'Ready for Development'. This type of view allows BAs to quickly see which cards still need to be analyzed and moved to 'Ready for Development'. Conversely, the 'Dev Wall' tab shows 'Story' and 'Task' cards that are 'Ready for Development' and beyond as these are the cards Developers on this XP project are most interested in.
The 'High Priorities' favorite shows all cards that have 'High' as its priorities regardless of its card type and is created by using the 'MQL filter'.