Goals
Previously, metrics were generated based on hard dates. Unfortunately the reality is that iteration planning usually is done on the first day of the iteration, stories may not be broken down immediately. This means that the charts were generated based on inaccurate data.
In addition many operations can be automatically done based on the state of the parent iteration:
- story and task dispositions may be defaulted automatically
- stories may be continued automatically on close
- actual velocity calculation may be performed
- ...
Usage
- After the Iteration meeting (Scrum meeting) is finished and all tasks have been created and estimated, the Start action link available in the iteration main view may be used to activate the iteration.
Note: the first developer to enter time to a task of an inactive iteration will be asked if the iteration should be started automatically. - Once the iteration is finished and that everybody have entered their time, somebody may click on the Close action similarly located in order to disactivate the iteration, compute the charts last data point and optionally continue all non-completed stories.
Affected Interfaces
On the main iteration view, a Start action link is available if the iteration is not started and a Close action link is available in case the iteration is started.
Notes
You must explicitely close an iteration. It no longer stops on the last day of the iteration but continues. You may be getting reminder emails for past iteration tasks because of this.
Limitations
- XPlanner does not detect that 2 iterations are active at the same time.
- The iteration is not extended if the iteration is not closed before the last day of the iteration. The consequence is that there won't be any additional data point in the charts past the original last date. The last data point will be always overwritten by the data of the day of the iteration closing.
Labels