Content
View differences
Updated by Rosanna Sibora 6 days ago
How can users access the sprint reports?
* via all sprints index page
* via ... menu within backlog and sprints page
* from the sprint board
Information visible on the 1st iteration (static page)
* sprint goal
* overview over wp # within the sprint
* number of work packages initially planned for the sprint
* number of work packages completed
* number of work packages unfinished
* number of work packages added additionally to the sprint during the sprint
* \[open question\] sprint progress chart (unfinished / completed)
* story points overview (initially planned, change after the sprint start, completed, unfinished)
* \[open question\] sprint progress chart (unfinished / completed)
* graph "Work package status"
* showing the status of work packages within the sprint
* we use the existing bar chart wp widget
* \[open question\]: I think a pie / doughnut chart might work better in order to show how the entire sprint scope splits into statuses. Should Do we go for bar have a pie chart or another one? widget we could possibly reuse?
* the graph could quickly give an overview over the progress within the sprint
* velocity chart (story points based) / more details within <mention class="mention" data-id="71903" data-type="work_package" data-text="#AGILE-66" data-display-id="AGILE-66">#AGILE-66</mention>
* 7 last completed sprints
* committed / completed
* average calculated based on the completed and visible sprints only (not only the line, but also the number)
* work package table: Completed work packages
* Columns: ID, subject, type, status, assignee
* work package table: Unfinished work packages
* work package table: Scope change after sprint start
* via all sprints index page
* via ... menu within backlog and sprints page
* from the sprint board
Information visible on the 1st iteration (static page)
* sprint goal
* overview over wp # within the sprint
* number of work packages initially planned for the sprint
* number of work packages completed
* number of work packages unfinished
* number of work packages added additionally to the sprint during the sprint
* \[open question\] sprint progress chart (unfinished / completed)
* story points overview (initially planned, change after the sprint start, completed, unfinished)
* \[open question\] sprint progress chart (unfinished / completed)
* graph "Work package status"
* showing the status of work packages within the sprint
* we use the existing bar chart wp widget
* \[open question\]: I think a pie / doughnut chart might work better in order to show how the entire sprint scope splits into statuses. Should
* the graph could quickly give an overview over the progress within the sprint
* velocity chart (story points based) / more details within <mention class="mention" data-id="71903" data-type="work_package" data-text="#AGILE-66" data-display-id="AGILE-66">#AGILE-66</mention>
* 7 last completed sprints
* committed / completed
* average calculated based on the completed and visible sprints only (not only the line, but also the number)
* work package table: Completed work packages
* Columns: ID, subject, type, status, assignee
* work package table: Unfinished work packages
* work package table: Scope change after sprint start