Record availability constraints
Owner role · Team lead
Evidence: Leave, support duty and required meetings are acknowledged by each owner.
Sprint decisions / Team leads
Decision deskReview sprint capacity without invented certainty
Compare planned work with actual owner availability and separate capacity limits from unresolved effort estimates.
Use an owner-level availability review rather than extrapolating a precise productivity score.
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: Reduce the commitment or change the delivery date before assigning work that depends on unavailable time.
Illustrative case: a three-person team plans a full sprint, but one member has two days of leave and another is on support rotation.
Identify review bottlenecks
Owner role · Review owner
Evidence: The plan shows which tasks require the same reviewer and when review time is available.
Choose the tradeoff
Owner role · Product lead
Evidence: The agreed scope reduction or date change is recorded with affected tasks.
Filled illustrative decision
Invented planning text. Adapt it to your evidence and confirmed owners.
The invented plan originally assumes three fully available people. After recording two leave days and the support rotation, the lead removes the optional report styling task. The remaining commitment includes the required review window; assigning the removed work to the same people would not create more capacity.
Questions about this workflow
Can we use last sprint as a baseline?
It can inform the discussion, but compare interruptions, staffing and task uncertainty before treating it as equivalent.
Should we plan to full availability?
Leave room for the interruptions your team actually experiences. Agree that allowance from observed work, not an arbitrary universal percentage.
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
- Ask owners for realistic availability without collecting unnecessary personal details.
- Include review and dependency waiting in the planning discussion.
- Record the scope/date tradeoff and recheck it when availability changes.
From a useful outline to team work
Explore TeamBoostAI for your team
Review real owner availability before allocating TeamBoostAI task work; this worksheet does not calculate productivity. 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.