Page Operations
Browse SpaceThe 0.6.3 has introduced 2 operations on Iteration: Start and Close and a Story Disposition.
This is the first step to provide better answers for the following questions:
- How much did I carried over from the previous iteration? Is there a pattern here?...
- How much did I add to this current iteration?
- How much did I remove from this iteration? [to be implemented]
- How much was discovered that wasn't planned at the iteration planning?
Story Disposition
| Disposition | Description |
|---|---|
| Planned | Story has been added to the iteration before the iteration started |
| Carried Over | Story has continued from the previous iteration before the iteration started |
| Added | Story was added after the iteration was started |
The goal is to better track scope creep and better visualize the amount of slippage.
Start/Close Iteration
These operations are meant to define precisely the start and the end of an iteration. This comes from the real world experience that
- iteration do not start at midnight on the first day but more like after iteration planning meeting on that first day.
- on distributed teams the task breakdown might be delayed by one day causing havoc to the current data sampling mechanism.
This has also the objective to provide sensible defaults to Disposition of Tasks and Stories. Our experience is that developers and even customer won't necessarily enter Disposition and Types correctly. As much of the tracking value of xplanner relies on the accuracy of these, having the system automatically generates an appropriate defaults will greatly improve the feedback it gives.
| Iteration State | Story Disposition | Task Default Disp. |
|---|---|---|
| Not Started | Not Carried Over | Planned |
| Not Started | Carried over | Carried Over |
| Started | Not Added | Discovered |
| Started | Added | Added |
TODO
This means obviously that a task can be "Carried Over".
On Continue story, we should change the disposition of all copied tasks to Carried Over.