Project Flow
🟣 Ad-hoc Work​
Ad-hoc Work refers to unplanned or spontaneous tasks that arise outside of the regular planned work or project scope. It often involves urgent or unexpected requests, troubleshooting, or addressing immediate issues or customer needs. Ad-hoc Work can disrupt planned work schedules and priorities.
How is it calculated?
- This is only calculated for sprints. When a ticket is added to a sprint after the sprint was started, it is considered an ad-hoc ticket. We exclude "sub-tasks" from ad-hoc work calculations.
If a sprint starts on May 1st, but a ticket (say GROW-123) was added to it on May 3rd, then GROW-123 will be considered an ad-hoc ticket.
🟣 Sprint Spillover​
Sprint Spillover refers to the unfinished or incomplete work from a sprint that is carried over to the next sprint. It occurs when the planned work for a sprint exceeds the team's capacity or unexpected obstacles hinder completion. Sprint Spillover impacts the team's ability to deliver all planned work within the designated sprint time. It may require reevaluation of priorities, resource allocation, or identifying and addressing underlying issues.
How is it calculated?
- This is only calculated for sprints. When a ticket was present in the sprint but was moved to the next sprint before it could be completed, it's considered a spilled over ticket.
If a ticket (say GROW-123) was present in Sprint S1 which would end on May 10th, but it was moved to Sprint S2 before it could be completed, then the ticket GROW-123 would be considered a spilled ticket.