Made for Engineering Managers
Run a Mid-Sprint Change Gate
Also useful for: people in Engineering Managers
45 min
Advanced
Engineering Managers
Engineering Manager
Improve Operations
Career outcome:
Avoid Professional Risk
Route an urgent sprint request through a disciplined gate that tests value, delivery impact, tradeoffs, authority, and follow-through.
Create a free account to save your progress and use this Playbook.
Use this when
A stakeholder wants work added, replaced, accelerated, or redirected after the sprint has started, and the team hasn't formally changed its commitment yet.
You'll need
- Sprint goal
- Proposed change
- Requested timing
- Reason and expected value
- Current sprint commitments
- Capacity and estimate evidence
- Dependencies and technical impact
- Risk concerns
- Stakeholders and authority
- Alternatives and constraints
You'll get
- The proposed change stated in testable terms
- Confirmed facts separated from assumptions and open questions
- Urgency and delivery impact reviewed
- At least two viable response paths compared
- Any accepted work matched to explicit displacement or verified capacity
- A gate outcome approved by the right decision owner
By the end of this playbook
You will have:
- The proposed change stated in testable terms
- Confirmed facts separated from assumptions and open questions
- Urgency and delivery impact reviewed
- At least two viable response paths compared
- Any accepted work matched to explicit displacement or verified capacity
- A gate outcome approved by the right decision owner
Sample
This is sample data, not your prompt. Pro unlocks this higher-stakes Playbook. On Free Playbooks you can still copy the assembled prompt into any AI.
Sample input
Sprint goal: Enable enterprise admins to complete SSO setup before Monday's pilot. Proposed change: Add audit-log export and release it with SSO. Requested timing: Before sprint end. Expected value: Sales says the pilot customer asked for it, but no confirmed blocker exists. Current commitments: SSO review is underway, domain verification is half complete, and end-to-end testing hasn't started. Capacity evidence: Two to four days estimated for the endpoint only. UI, security, and validation are excluded. Dependencies: Reporting service, permissions, storage, admin UI, security review, and support documentation. Risks: Permission leakage, export timeouts, reduced SSO testing, and more on-call exposure. Authority: Sales requested it, Product owns priority, Engineering owns delivery, and the product VP resolves pilot tradeoffs. Alternatives: Support can produce a manual export for the pilot.
Sample assembled prompt
Gate Summary Recommendation: DEFER the full... Offer one controlled manual export for... Facts and Gaps Confirmed: The request... SSO validation remains incomplete. Unconfirmed: The pilot is blocked without... The estimate covers the complete change. Security review can finish within the... Urgency Test Classification: Customer preference with... Consequence of waiting: The pilot may... Impact Review Adding the full feature... The two-to-four-day estimate excludes critical work. Options Compared 1. Accept the full feature now: highest... 2. Defer the feature: protects the... 3. Provide a manual export: addresses... Recommendation DEFER, with a manual workaround... Reverse this decision only if the... Displacement Decision No sprint work moves... If accepted, Product must name which... Ownership and Approval Decision owner: Product... Delivery impact owner: Engineering manager. Manual export owner: Support lead. Validation owner: Security engineer. Checkpoint: Pilot readiness review tomorrow at... Communication Draft We reviewed the request... The full feature is deferred because... Support will provide a controlled manual... Product will confirm that need at... Follow-Up Checks Sprint board unchanged. Manual export access reviewed. Product confirmation pending. Full feature queued for estimation and...