You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have 8 teams in total and they are all showing up on the program allocation report. Unfortunately for each of the last 5 sprints for everyone of my 8 teams, the points planned shows the same as my points accepted.
Is this how its supposed to work? Is this how it works for all of the users? If so what's the point? I would expect that it show the points planned and points accepted similar to how it shows in Jira velocity chart. Currently the points accepted corresponds to that in Jira. But the points planned is the same as the points accepted. And No... All the 8 teams did not complete all the stories that they took in exactly over the period of 6 sprints!!!
@Jay Michael the simple answer is because your Avg Team Velocity is 0. The Avg Team Velocity is calculated on the last 5 CLOSED Sprints. If the Sprints are not closed, then you will not get a team velocity.
The more complex answer is how this report is using data from Jira and the sprint information that comes over through the integration. Let's say the team planned 25 story points of work for the sprint, but only accepted 20 story points. The report should be 25 planned and 20 accepted. In Jira when you close the sprint and move the incomplete stories to another sprint (versus pushing it to the backlog first), the planned points that Jira sends for the current sprint to JA is 20. So now the report shows 20 planned and 20 accepted.
There are some other views such as backlog sprint view and the team coaching report that may show planned story points at the beginning of the iteration. We are having conversations internally on how to best use this type of report and the data that drives it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.