The new portfolio planning experiens

Question

I think I will eventually like the new experience but the first thing that need to be fixed is support for larger plans; more issues and more projects.
The next thing a saw was missing is the capacity view of the team.

Have it overlay the planning view so you easily can see when you have planed enough work for the team.

Carl Dorbeus · Answer

1. Currently we are creating one plan per team, and it works fairly good, then we create a iframe report for the scope view and one iframe report for the capacity view, and then we combine all the reports from all teams on a confluence page.
From this page we get the whole department picture. Its basically an interactive Programs view with a added capacity view which loads very slow.

This is cumbersome when doing planing and moving work between teams.

The number of issues we can handle with better disciplined filter, but the number of projects we can see how we handle.

samrobertsofficial · Answer

@Carl Dorbeus

1. It seems like you trying to achieve a single plan that captures all the issues for your entire jira instance, is that correct? It sounds like having multiple smaller plans wouldn't suit your needs? Is this mainly to do reporting, or would many users be modifying and interacting with that plan at once?

The new experience does offer improved performance for larger plans, but we still have work to do to support larger plans. The best advice I can offer in the meantime is to think about what issues you could exclude from your plan to decrease the issue limit, as well as if you could create multiple smaller plans.

2. Got it. Thanks for clarifying.

Please let me know if you have any other feedback about the new experience.

Carl Dorbeus · Answer

1. We currently have about 200 jira projects, where our team are cross functional so it is very easy to create filters that pull in more than 100 projects, when you create a plan for single team, and it is impossible to create a plan for our entire department with more than 10 teams.
The number of issus is also a problem for the department plans since most team has a large number of old completed issues in there backlog filter. currently around 8000 issues in all team backlogs (includes both future, current and completed issues).

2. Capacity per team and sprint for the length of the plan for scrum teams. and suitable granularity for kanban teams (daily average based on a forward looking sliding window e.g 1 sprint duration).