Loading
Because the sprint is planned against a velocity number and delivered by people who also have client calls, support escalations and a day of leave nobody counted.
A sprint is a time-boxed set of tasks pulled from the backlog, committed by the team for that period.
Planning pulls from the backlog against actual capacity for those dates — working patterns and approved leave included — so the commitment is made against hours that exist.
A two-week sprint with one person on three days' leave shows sixty-two available hours rather than eighty. The team commits to what fits and says so at the time.
It will not impose a methodology. Sprints are available for teams that want them, and a team running continuous flow can ignore them entirely.
Sprint work is the same tasks the plan and the client portal use, so a sprint that pulls from a client project moves that project's dates and margin.
Yes, which is normal for a team serving several clients.
It returns to the backlog in its position, or carries over explicitly.
Yes, and the change is recorded against the commitment.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.