I am struggling to figure out how to use Portfolio to do release planning in what I would consider the natural intuitive fashion. In my simple example you can see two issues that I can not figure out how to address. The item listed as priority #10 is scheduled to start before issues 1-9. Secondly, the epic is not completed sequentially. Instead it is split up across several months!
Here is some context to the epics that are contained within this release.
I am relying on Portfolio to use the story point velocity, scoping and priority to suggest the target release. I would have expected that the work would be scheduled in one sprint if each developer is tasked with a single story. Alternatively it would take two sprints by the same developer. However this is not happening. I have experimented with all of the settings and different permutations in Portfolio but I always end up with the same results. This problem is not unique to this one epic/story. It happens with other epics as well that only have a single story. I can only imagine that I am doing something wrong since I can't imagine that this type of scheduling is useful for anyone.
Thank you in advance.
If you look at your scope table issue order (when all sorting is turned off), is the story order as you'd like it to be? 'Priority' of issues is derived from the story level, so give this a check and make sure they are in the order of priority you want.
I would also recommend making manual release assignments for your issues, given you have them set up. Especially if you have an expectation that certain issues should be done as part of a particular release. You don't have to do this, but it will 'force' issues that are assigned to a release to be done in the fixed timeframe you've set on the release.
In combination with story 'ranking' (or priority), you should get the result you're looking for.
Please don't hesitate if you have any other questions at all and please let me know if this works for you.
I have been told that in order to properly use Portfolio to manage your schedule and backlog, you have to prioritize by Story alone - not Epic. This is difficult, if not impossible for my business as we do not have a good way to organize Stories in a consistent way throughout our project. I was operating under the notion that Stories grouped under an Epic would inherit the relative Epic priority, but evidently that is not the case. It would be great to know if you organize by story alone that you can actually use Portfolio. I have yet to prove this myself.
So, yesterday I created a project and a few stories to test this, as I also read somewhere.
Result: same problem. Inumerous tests, configurations.. always the same.
One of the most simple tests I've made that shows the problem:
- one new portfolio for a new test project
- team with just one person, capacity = 40 hours a week (1 week scrum)
- some stories with 21 hours each
- one story per week
- remaining capacity of 19 hours a week! Incredible..
- if you have the last story of your backlog with less than 19 hours, it will put it in front of all the others..
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