You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.