Clarify the actual deadline
Owner role · Duty coordinator
Evidence: The requester confirms the audience, deadline and smallest acceptable output.
Sprint decisions / Duty coordinators
Decision deskTriage urgent work against the sprint commitment
Assess an incoming request, identify what it displaces and record a visible decision instead of silently expanding the sprint.
Separate urgency from priority and make the opportunity cost explicit.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Decision desk
Decide before adding more work
Decision to make: Confirm the minimum urgent outcome; replace a named task or defer the request with an explanation.
Illustrative case: a stakeholder asks for a presentation export during an already committed sprint. The deadline is tomorrow, but the audience and minimum output are unclear.
Identify displaced work
Owner role · Sprint lead
Evidence: The decision names the committed task that would move and its consequence.
Record the accepted tradeoff
Owner role · Decision owner
Evidence: The urgent request is accepted, reduced or deferred with a communicated reason.
Filled illustrative decision
Invented planning text. Adapt it to your evidence and confirmed owners.
The invented stakeholder needs a three-slide summary tomorrow, not a new presentation-export feature. The lead proposes a manual summary, identifies the label review it would displace, and requests approval of that tradeoff. No sprint task changes until the commitment owner accepts the replacement.
Questions about this workflow
Who should decide the tradeoff?
The person responsible for the affected delivery commitment, with input from the requester and owners of displaced work.
Should the urgent task be hidden from the sprint plan?
No. Record both the incoming work and the changed commitment so the final review explains what happened.
Does this create tasks in the product?
No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.
Put the outline to work
- Gather the consequence of waiting rather than accepting an urgent label at face value.
- Ask the commitment owner which work should move if the request is accepted.
- Notify affected owners and revisit the changed plan at the next check-in.
From a useful outline to team work
Explore TeamBoostAI for your team
Document which existing commitment would move when considering urgent new work in TeamBoostAI. Confirm the workflows available in your account before adopting this outline.
Request TeamBoostAI access
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.