1. The team has one 100%.
Mentoring, incidents and reviews use the same capacity as projects. Look back with the team and allow for recurring support before accepting more work.
https://blog.rvnd.me/leadership/make-the-work-fit#1-count-the-work-that-does-not-look-like-a-project

2. Plan beyond code complete.
A release still needs review, integration, testing, rollout, rollback and support. Agree owners and allow time before committing to a release date.
https://blog.rvnd.me/leadership/make-the-work-fit#2-plan-through-to-running-the-thing

3. An assumption failed. Replan.
When an assumption fails or staffing changes, review scope, sequence, help and dates with the team. New owners need room for inherited responsibilities.
https://blog.rvnd.me/leadership/make-the-work-fit#3-change-the-plan-when-its-assumptions-fail

4. Raise risk while choices remain.
Raise a risk while stakeholders can still choose. Explain what changed, recommend an option, name the decision deadline and give a checkpoint for unresolved uncertainty.
https://blog.rvnd.me/leadership/make-the-work-fit#4-communicate-while-people-can-still-help

5. Remove work nobody needs.
Examine recurring reports, approvals and old features. Agree with the relevant owners on what can be simplified or stopped, and account for usage, obligations and migration work.
https://blog.rvnd.me/leadership/make-the-work-fit#5-remove-work-that-no-longer-needs-doing