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
Hoping I can get some help resolving an issue I am having with capacity in portfolio. We have specialists working on projects that can be up to 6 months long. When I create an issue, epic, and feature, I have been inputting all the correct information - estimated time, start date, end date etc. On all levels. I also assign the issue to a sprint.
The problem is that in portfolio, the estimated time does not roll over and spread across future sprints. Which means all of our specialists appear over capacity. Please see image attached, our staff members are working 128 days in 10 day sprints.
Our staff members can be working on up to 3 projects at once, and we have 50 staff members in our faculty. So the resolution to this problem cannot be that we have to create an issue every 10 days for each project.
Is there anyway way for the hours to spread over multiple sprints? Or to resolve this problem?
Hi Dominique! How are you doing?
In your case, it seems to me that work in Kanban scheduling would be better than Scrum. The schedule will be based in days, not in sprints.
Hope this helps!
Hi Cristiano, thank you for getting back to me.
Would this view in Kanban with days still appear in the same way as the sprint portfolio? This portfolio would be great for us if it worked as we need it to, because we need to see many staff members at once, how much capacity they have per fortnight, and when they are next available. In the management team, we like that it appears in a linear format.
Would the solution you are suggesting allow for this kind of view?
Most views in both modes are basically the same. I would suggest you to change your team to work in Kanban mode and, in case you don't get the view you want, just rollback the change. You don´t need to commit to JIRA in order to check whether the reports fit your needs.