-
Bug
-
Resolution: Fixed
-
Low
-
10.119.3
-
2
-
Severity 3 - Minor
-
No
Issue Summary
Kanban teams don't have sprints so the velocity should not be calculated as for agile teams.
Kanban teams have throughput, but throughput is calculated differently, and treated differently in the Forecast than it is in the Program Board (mainly because Jira Align is treating throughput as velocity, even though they are different fields).
Steps to Reproduce
N/A
Expected Results
To be determined by the Product Manager.
Actual Results
In the forecast, the throughput is calculated like this: anchor sprints x number of stories accepted in the past 5 weeks.
In the program room, throughput is calculated like this: number of weeks in a PI x number of stories accepted in the past 5 weeks.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- mentioned in
-
Page Failed to load
- resolves
-
ALIGNSP-18644 You do not have permission to view this issue
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JIRAALIGN-4997] The Kanban Team velocity calculation in Forecast is confusing
| Fix Version/s | New: 10.126.0 [ 106111 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Long Term Backlog [ 12073 ] | New: Closed [ 6 ] |
| Labels | Original: Bulldog | New: BW1 Bulldog |
| Support reference count | Original: 1 | New: 2 |
| Remote Link | New: This issue links to "Page (Confluence)" [ 763408 ] |
| Remote Link | New: This issue links to "ALIGNSP-18644 (Atlassian Support System)" [ 763188 ] |
| Status | Original: Short Term Backlog [ 12074 ] | New: Long Term Backlog [ 12073 ] |
| Labels | New: Bulldog |
| Status | Original: Needs Triage [ 10030 ] | New: Short Term Backlog [ 12074 ] |
| Support reference count | New: 1 |