Explore how UX measures and manages capacity for a given milestone
Problem:
Today, designers don't have a defined way of measuring their capacity for a milestone and communicating that out to their stage groups. The problem can be broken down into three statements:
- How might we measure/score the weight of an issue in a meaningful way?
- How might we measure our capacity for a milestone in a meaningful way?
- How might we communicate our capacity to our stage group in a way that promotes prioritization and valuable work?
Intent:
Conclude this issue with a direction for a pilot.
🕐 What's been tried in the past:
Google sheets
- Andy: I've been keeping a google sheet and manually assigning weights to planned issues based on assumed effort and uncertainty. Link to sheet See the tab labeled UX Weighting for how I've initially defined weight scoring.
Pros:
- Editable and does not impact the workflow of the issue we are discussing.
- Allows for flexibility when scoring
- Aggregates scores automatically for capacity planning
- Allows for retros and adjustment of scores after the work as been completed
- Helps with establishing capacity thresholds for designers
Cons:
- Not in GitLab so visibility is limited.
- Actions and todos have to be remembered and put back into GitLab
- Manual process which relies on copying and pasting issue links from the issue boards.
- Somewhat time intensive
- Lack of defined process on when to score and communicate out inhibits adoption
- The current template is busy and might be trying to do too many things at once.
Ideas to consider:
- T-shirt sizing as a general measure of capacity
- Aggregate scoring based on expected effort + uncertainty
Next steps:
-
Create a time-boxed pilot issue for measuring capacity in a milestone
Edited by Andy Volpe