I have multiple areas of work that I want to do each sprint. The Themes model works well here; I have assigned a Theme to all my stories and I can check how much of each Theme I'm working on each sprint with the Themes report. But the backlog/Scope view in Portfolio gets pretty unmanageable for rank prioritization; there's no way to only consider one Theme at a time and sort those items. Is there a better way to make a plan that merges all Themes together, but lets me sort items in a single Theme better? I think a Theme filter in the Scope view would do this well, but I also wonder if there's a better workflow in general.
I must be blind; that's great, thanks!
Any suggestions as how to manage the prioritization of items in different Themes to help make sure Theme targets are met? That is, if I want to spend 70% on Theme A and 30% on Theme B, with a backlog of 100+ items, how should I interleave the items to make sure the scheduling algorithm picks items to maintain that ratio?
Putting aside dependencies and other external date factors such as releases, Portfolio's algo takes into account rank as the main factor for scheduling. I think your direction is good, there is a lot of trial and error in the scope section but after a few times the theme report should show your desired outcome.
I hope that helps,
The Portfolio for Jira team wants to hear from you. Share your top tips for building a great Portfolio for Jira plan for a chance to win some Atlassian swag. Do you structure your teams i...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot