Weight and progress information in roadmap epic bars
Problem to solve
When using the roadmap, there is currently no way to know if an epic is on track to be completed by the assigned end date.
When I'm viewing the roadmap...
I want to quickly understand the completion progress of each item on the roadmap...
Force: It's frustrating that I can't understand the overall progress of a given epic item on the roadmap. There are timelines but those are set before something is usually started and aren't adequately maintained while an given epic is in progress.
Force: Issues aren't groomed regularly, especially when it comes to issue weights, so I'm hesitant to trust any progress completion data I will see on the roadmap when this is completed because it doesn't necessarily take into account historical velocity of the team implementing it.
So that I can report progress outwards, provide additional support as necessary to lagging items, and get better visibility into where we said we were going and how we are progressing towards those goals.
Product managers, project managers, directors, executives
How teams could define progress:
- Time estimate vs. time spend per issue
- Issue Tasks completed/outstanding + Issue count open vs. closed
- Weight completed vs. weight outstanding
Data To Collect
- What percentage of customers are currently using weight?
- What percentage of customers view milestones by issue count vs. weight
- Usability study / multivariate tests.
- Expose weight completed vs. weight outstanding in some form or fashion on a roadmap epic.
Follow on iterations
- Issue Tasks completed/outstanding + Issue count open vs. closed, provide way for user to select which progress calculation to use.
- Issue Tasks completed/outstanding + Issue count open vs. closed, add option to interface for selecting which progress calculation to use.
- The entire roadmap needs to support real time functionality sooner rather than later. Engineering, can you please take this into consideration when thinking through the implementation?
- This is a good opportunity to pay down some technical debt and refactor the Roadmap to use GraphQL (#12887)
- Use components from Pajamas. If they don't exist, contribute them if at all possible. Let's try to only create custom front-end components as an absolute last resort.
Permissions and Security
- As the MVC exposes no configuration options, users with access to view the Roadmap will be able to view progress completion.
- Update Roadmap Documentation
- It will be important to remember that the aggregate progress completion data will be derived from all sub-epics and issues within sub-epics.
What does success look like, and how can we measure that?
- Increase in roadmap usage (avg. views per user over a given period, number of unique users with at least one view over a given period)
- A user can view the completion progress per epic on the roadmap.
What is the type of buyer?
Links / references