This question is in reference to Atlassian Documentation: How do Story Points get burnt down and reflected on the Burndown Chart
We have 'Resolved' and 'Done'. A Story is completed only after it is marked as DONE. This means that the progress will NOT be gradual as everyone seems to think so. A developer resolves it, QA verifies it and then finally PO marks as Done. This means that a story will typically get 'Done' only after 4-5 days. So how does the step ladder come into play?
The story-point burndown does not show a daily burndown or progress of tasks. How can we see that?
We are having the same issue and are looking for a similar answer.
Currently we have two boards, a development board and a releases board. The Development Board (Scrum) has all statuses that are QA and Release prep as marked as Done. That is where the Releases Board starts.
There are major disadvantages as if an issue fails QA (specifically when they fail integration testing), it gets rejected and then doesn't show back up on the dev board. We'd like to all then use the same board to progress tickets.
However, we'd like the Burndown chart to reflect development and not release (as the OP lists). Is there any way to map the burndown chart against custom statuses and not the right-most column on the Sprint board?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs