I am using portfolio with a kanban team. The team contains 9 members with 40 hrs per week capacity. I have 6 stories. 5 of them are assigned to 5 members of the team (one per person). Portfolio therefore predicts each story will take a month to perform based on one assignee doing a story. The capacity shows that for each week, I have 4 member of free capacity left. My 6th story is not assigned to anyone. This 6th story is assigned to a different release but this release as the same start date as the other release to which the other 5 stories are tagged.
In the portfolio setting, I have set the option that up to 12 people can work on a single story. Therefore, I would expect that this 6th story that is unassigned would use up the capacity available each week and start in parallel with the 5 others. Instead, portfolio forces it to start only once the other 5 assigned stories are done. When I look at the capacity, it is ridiculous because I see that my team is occupied at 50% during the time the team works on the 5 assigned task. HOw can I force parallelization of the tasks.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Recently, as part of a series of Portfolio for Jira case studies, we spoke with Carl DiClementi, Director of Product Management at Factom about how he uses Portfolio for Jira. In...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs