Content
View differences
Updated by Julia Racsko 4 days ago
As an agile coach I would like to understand my teams' current velocity so that we can use the average velocity for the sprint planning in future.
**Acceptance criteria**
* Should automatically show as a part of a sprint report (both completed and active sprints)
* Should show past 7 sprints as a bar chart with the numbers displayed (like the charts in the Dashboard)
* The last sprint (the one to the right) is the one the report page is created for. That means the widget always shows the 6 sprints before the looked at sprint and the sprint looked at. If the sprint is not completed, the values might still change. Once the sprint is completed, the values should no longer change.
* \[open\] The "last sprint" label is not ideal given the semantics.
* \[assumption\] If there are less than 7 sprints, we simply show less. Meaning in the extreme, only a single sprint is shown. Julia: this sounds good to me!
* Should compare committed number of story points and completed
* The axises depict
* x: sprints
* \[open\] How to display long sprint names? Ideally chart.js solves this itself.
* y: story points
* The datasets are:
* Committed: Sum of story points stored on work packages associated to the sprint when the sprint is started (button pressed)
* \[open\] The point in time when the button is pressed would be ideal. But we don't have that information now. We will have to rely on the sprint start date until the sprint is journalized.
* Completed: Sum of story points stored on work packages associated to the sprint when the sprint is completed (button pressed). If the sprint is not yet completed, use the current value.
* \[open\] same as above, we currently have to rely on the sprint finish date instead until the sprint is journalized.
* Should show a line representing the average velocity of the last 7 sprints with the number next to/on top of/over/? the line (let's discuss between design and dev what the design options are with chartjs and OP!)
* in addition to the bar chart we should show the following numbers within the chart
* velocity of the last (looked at) sprint.
* average velocity of 7 past sprints
* \[open\] For all graphs: How are the graphs scrolled. Or is the whole page scrolled?
* \[open\] What is displayed on hover? The dataset name and the value or nothing at all?
* \[open\] The specification states for the feature to be on the EE PRO level. The mockup shows it displayed when there is no EE license. What is the desired EE level?
* \[open\] If multiple active sprints are enabled, which sprints do we compare to. Proposal: Remove the velocity chart for now.
**Out of scope**
* Should be possible for a user to define the velocity chart as a widget on the project dashboard
* Users should be able to define how many sprints they would like to see on the chart
* What happens with multiple active sprints?
* Can we attach semantic colors? It would be weird to have committed as green and completed as red.
**Acceptance criteria**
* Should automatically show as a part of a sprint report (both completed and active sprints)
* Should show past 7 sprints as a bar chart with the numbers displayed (like the charts in the Dashboard)
* The last sprint (the one to the right) is the one the report page is created for. That means the widget always shows the 6 sprints before the looked at sprint and the sprint looked at. If the sprint is not completed, the values might still change. Once the sprint is completed, the values should no longer change.
* \[open\] The "last sprint" label is not ideal given the semantics.
* \[assumption\] If there are less than 7 sprints, we simply show less. Meaning in the extreme, only a single sprint is shown. Julia: this sounds good to me!
* Should compare committed number of story points and completed
* The axises depict
* x: sprints
* \[open\] How to display long sprint names? Ideally chart.js solves this itself.
* y: story points
* The datasets are:
* Committed: Sum of story points stored on work packages associated to the sprint when the sprint is started (button pressed)
* \[open\] The point in time when the button is pressed would be ideal. But we don't have that information now. We will have to rely on the sprint start date until the sprint is journalized.
* Completed: Sum of story points stored on work packages associated to the sprint when the sprint is completed (button pressed). If the sprint is not yet completed, use the current value.
* \[open\] same as above, we currently have to rely on the sprint finish date instead until the sprint is journalized.
* Should show a line representing the average velocity of the last 7 sprints with the number next to/on top of/over/? the line (let's discuss between design and dev what the design options are with chartjs and OP!)
* in addition to the bar chart we should show the following numbers within the chart
* velocity of the last (looked at) sprint.
* average velocity of 7 past sprints
* \[open\] For all graphs: How are the graphs scrolled. Or is the whole page scrolled?
* \[open\] What is displayed on hover? The dataset name and the value or nothing at all?
* \[open\] The specification states for the feature to be on the EE PRO level. The mockup shows it displayed when there is no EE license. What is the desired EE level?
* \[open\] If multiple active sprints are enabled, which sprints do we compare to. Proposal: Remove the velocity chart for now.
**Out of scope**
* Should be possible for a user to define the velocity chart as a widget on the project dashboard
* Users should be able to define how many sprints they would like to see on the chart
* What happens with multiple active sprints?
* Can we attach semantic colors? It would be weird to have committed as green and completed as red.