Product discovery for planning milestones and setting WIP limits or capacity indicators

Problem to solve

Research into:

How might we allow users to better groom and plan their backlogs or issue list?
How might we allow users to better prioritize backlogs or issue list?
How might we allow users to determine capacity or velocity at the backlog level (before creating a milestone or board)?
How might we allow users to set limit on WIP to promote throughput on boards?
How might we better indicate capacity on boards in progress? Do we need to?
How might we allow users to better estimate an upcoming milestone's velocity (perhaps based on team availability and analytics on prior milestones)?
Are users often shifting issues or adding new issues during milestones? If so, why? Is this a good experience?
What does the current planning process look like? How do users find this experience?

Intended users

Parker, Delaney, Presley

Testing

WIP

What does success look like, and how can we measure that?

Users are able to quickly plan (estimate and agree on capacity and velocity with their team), prioritize issues in their backlog (before starting a milestone?), optimize throughput of boards, flag any issues in capacity, and consistently complete milestones at the agreed upon velocity.