...
- Not ready for development backlog is taken into work
- Poor requirements provisioning process Frequently changing scope and priorities
- Uncontrolled scope volatility
- Too many stakeholders on business side
...
Info |
---|
|
- If an item is changed several times in different iterations it will be counted as a changed item for each iteration.
- Sub-items are not included in the calculation because they usually do not represent delivery value at a business level.
- If an item was returned to ready for development status several times, only the changes that were made after the last ready for development status assignment will be reflected on the metric.
|
Data source
Data for the metric can be collected from a task tracking system (Jira, TFS, Rally, etc.).
...