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.
Here's a simplified view of my team's issue workflow
Planned (Status type: 'To do') → Ready for sprint (Status type: 'To do') → In progress (Status type: 'In progress') → Testing (Status type: 'In progress') → Prod (Status type: 'Done')
Is anything reflected in sprint burndown chart if I:
The main reason why I am asking this is that we are only marking items as Prod (Status type: 'Done') at the very end of the sprint, all in one go.
Does this mean that the sprint burndown chart will have a large cliff at the end instead of gradual step-like progression as is ideal? If so, what can I do to make the sprint burndown chart useful for our team?
Should we add another status with the type 'done' that comes before Prod?
It appears that you posted this same question as both a discussion topic and a question, so I am posting the other link here to help the community align the ideas they give you:
Thanks @Bill Sheboy
I am new to the community, so I wasn't sure which was the best place to post this
Thanks for your response @Nic Brough -Adaptavist-
I am very new to product management (& to Jira), so I am not aware of how other software product teams go about structuring their boards.
Do they consider 'prod' as done? Or do they consider 'Ready for deployment' as done? If I could get some insight on that, it would be helpful.
This gave me some thoughts on approaches that we could go with:
What do you all think?
No, most teams would not consider "production" as "done". Done is defined by the team who need to do something about the issues, and you'll find a "done" means "does not need this team to do any more on it".
Development teams for example, don't care about where a story is after they've coded for it, "ready for test", "planning to deploy", "in production" - developers simply don't care, they can't do anything with the story any more, their work is done on it.