Burndown chart

The following graph provides a rough status on the progress of the Confluence team.

Rules for how to update the release dashboard

Steps that need to be done at the end of an iteration

• Tasks that were finished get ticked off with a and remain where they are.
• Tasks that have been started but not finished get moved to the next iteration. No estimates are changed, and in the comment field a text is added "carried over from previous x weeks".
• Tasks that were planned but not even started get moved to next iteration without comment.
• Velocity of previous iteration may be calculated and added, but only based on finished tasks, no matter how close unfinished tasks were to completion
• New unplanned work is added to the new iteration and marked in blue. cards that simply took longer than expected don't get any colour-coding.
• The "remaining estimated work" number from previous iteration remains unchanged.
• "Remaining estimated work" for the new iteration (including the backlog) is calculated based on the original estimates, and includes unplanned added work. So even a 2d-task that is considered 90% done will show up as 2d in the new iteration. The new iteration may exceed the previous velocity since we assume that there just remain 10%. But for the "remaining estimated work" the two days will be used.
• If the sum of all remaining work is larger than the original budget, some tasks at the end have to be declared as "won't fix" and greyed out. Their estimates are no longer counted for the remaining work.