Jira Portfolio capacity warning

Lawrence Leonard_520bng

I read where if a team exceed its capacity (velocity) for a sprint the issue is only partially scheduled.  Does this mean that Portfolio only schedules to the teams capacity and the rest is unscheduled?  I can see where this makes sense for future sprints, but the active sprint means the team has committed to completing this work.  Can you clarify how this works and the rationale for it.   It may just be that this is the most conservative view, but I want to make sure I understand what my plan is representing.

Larry at Isos

That text you are referring to is related to how the scheduling algorithm works.

The scheduling algorithm does this, it's useful to predict how long the epics and stories associated with a team will take to complete  beyond the team's sprint to sprint commitments. As you indicated: it's useful for future sprints.

Your team configuration (in your plan) should indicate which scrum board the team is using. This allows the plan to see the explicit sprint commitments the teams make.

Any commitments the teams make in their scrum board will not be disrupted by the scheduling algorithm. There will be a warning in the capacity view to call attention to the fact that the team is committing more than their planned velocity. But it's not an error, it's a warning.

You'll also notice (when you connect each Team to their Scrum board) that the names they (the team) uses for each of their sprints in their board appear on the plan. The predicted future sprints follow a generic naming convention of Sprint <number>. This makes it easy to tell where the algorithm has started populating stories into predicted future sprints that the team doesn't even have on their board (yet).