Capacity planning in roadmaps
- When you look at the roadmap, you should be able to do these two things:
- Quickly see what is planned in the future.
- Quickly see if what is planned in the future is feasible from an effort perspective. That is, do we have enough capacity to the work planned in the future?
- This second problem is the capacity planning problem.
- Capacity planning across milestones is addressed in https://gitlab.com/gitlab-org/gitlab-ee/issues/6765.
- This is about capacity planning in a roadmap context, which is typically across longer stretches of time, further in the future, and at a higher level.
- Look at your current roadmap with the given filter.
- Look at the epics going on into the future with open issues. (For the algorithm below, the epics we care about need to have end dates.)
- Sum the open issues' weights for each epic, and spread them evenly over time, for that epic's remaining estimated time.
- Take that even spread and add across all epics for given time periods (in the mockup below, it is for months).
- Indicate the sums in a visualization. In the mockup below, we just add the line chart to the dates area.
- One design is that when you click the line chart, there is a modal, and you see more detail with graphs.
- The idea is that this visualization lets you know how much work is planned over time.
- We should have a way to indicate the planned capacity. In order to do this, we might have to "saved roadmaps", similar to having multiple boards with saved configs.