Improve the efficiency and experience of weighting an issue backlog
Problem to solve
Situation: When my team is collaborating on scoping a release or grooming the backlog...
Motivation: I want an easy way to run through the backlog and assign rough sizes to issues/stories...
Force: Opening each issue in a new tab, then clicking edit, entering a number, then hitting enter, then closing the tab to get back to the list, then refreshing the list view to get an updated number is really annoying and inefficient.
Force: It's frustrating that I either have to refresh the list view every time to see the updated value; but if I don't sometimes I accidentally open the issue I was just working on because the UI didn't update after adding a weight to the issue.
Expected Outcome: So that we can understand how much work is there, discuss tradeoffs as necessary, and adjust the amount of scope to match our expected output.
Intended users
Developer, Designer, Product Manager
Further details
Our Customer's Real Use Cases
User story size needs to really be a first-class concept – needs to be easy to go through backlog as a team and quickly assign rough sizes (e.g. tee-shirt sizes) to stories.
Proposal
- TBD
Permissions and Security
- TBD
Documentation
- TBD
Testing
- TBD
What does success look like, and how can we measure that?
What is the type of buyer?
- Starter
Links / references
- External existing solution - https://www.planningpoker.com/