Hi, Hauke - Portfolio scheduling is focused on agile principles of highest-priority items first, thus it indeed schedules the highest prio item with the max. possible capacity, to finish it as fast as possible, and then the next one. We found it makes sense to promote this as a best practice - if there is nothing blocking the work on the highest-priority task, why should the work be interrupted by working on the second most important at the same time? However, the focus has rather been to do higher-level planning towards release dates, where in both cases (parallel or sequential), it is guaranteed that at least the total capacity until a cut-off date is realistic. The details for how the team works might anyways turn out slightly different in practice. I don't think there is a good workaround to this right now, the only things that result in parallel work being scheduled are "max resource limits", e.g. only X people can work on a story at a time, if there is more people, stories will be scheduled in parallel (you could set this to 1 in the scheduling settings and you'd see that different people will take on different tasks at each time, running in parallel), or other factors like stages or dependencies causing that the highest-prio task needs to wait a bit.
Hi Martin, thank you for the fast response. I guess i have to think more about the combination of high.level-planning and the weekly / daily planning for every single team member. i was trying to start the high-Level planning in Portfolio and exporting JIRA issues for the stages and so on. The dimension of a stage would have been work about maybe 1-3 weeks and 1-5 team members. These Members work at different Epics which are all have stories and stage-based tickets and have to run definately in parallel. This is where my problem. There is a lot of parallel work in workshops and of course also single-sequential work. But you still answered my question, so i have to find another way to combine the "real work"-JIRA issues with the higher-level planning. Maybe create virtual Members which are small teams of people who work together instead big teams with real members.. i have to think about it.. :smile:
I also see this as an issue with Portfolio. I do not want to have to manage each person as it's own team. If I look at a team with 5 people, I simply want to show 2 epics being worked at the same time. No need to call out dependencies at that level of detail in a planning tool. Is there no better way to setup concurrent Epics??
Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events