Create a post-crunch team recovery sprint plan

Design a two-week reset sprint to help teams recuperate after an intense deadline push. Use this to tackle low-stress tech debt, clear mental fatigue, and restore sustainable momentum.

You getSprint Objectives, capacity and Meeting Rules and two-Week Timeline

Prompt

Prompt
Act as an agile team coach and engineering manager. Design a balanced two-week post-crunch recovery sprint schedule for a team that has just finished an intense, high-stress delivery milestone.

- Lower cognitive load by capping commitments at 50 percent of standard velocity.
- Focus strictly on low-stress technical debt, documentation clean-up, and tooling improvements.
- Reduce meeting overhead by at least half to allow uninterrupted focus time.
- Include structured, blame-free reflection points to process the crunch period.

Output format:
- Sprint Objectives (3 bullet points)
- Capacity and Meeting Rules (bullet list)
- Two-Week Timeline (Day-by-day outline covering Weeks 1 and 2)
- Team Retro Discussion Prompts (numbered list)

Example output

Sprint Objectives
  • Restore physical and cognitive energy without halting everyday operational baselines.
  • Address low-friction technical papercuts, obsolete documentation, and developer environment friction.
  • Evaluate the root causes of the preceding crunch to prevent future emergency crunches.
Capacity and Meeting Rules
  • Sprint capacity is locked at 45% of typical story points; no new feature work accepted.
  • Cancel all non-essential recurring meetings, including multi-team syncs and secondary grooming sessions.
  • Daily standups are shortened to 5 minutes or replaced by asynchronous written check-ins.
Two-Week Timeline

Week 1: Decompression & Easy Wins

  • Day 1: Late start, brief sprint kickoff, cancel afternoon meetings, light personal planning.
  • Day 2-3: Low-stress individual backlog clearing (fixing small bugs, updating broken internal docs).
  • Day 4: Tooling maintenance or dependency updates with zero release pressure.
  • Day 5: Focus Friday, zero meetings, personal learning or exploration time.

Week 2: Clean-up & Future Calibration

  • Day 6-7: Team pairing on minor refactoring tasks and improving test coverage.
  • Day 8: Milestone post-mortem and open reflection session (90 minutes maximum).
  • Day 9: Standard backlog pruning and gentle preparation for standard sprint return.
  • Day 10: Sprint review showcasing quality improvements; social unwind hour.
Team Retro Discussion Prompts
  1. What systemic issues or planning oversights pushed us into crunch mode near the end?
  2. Which processes felt completely unnecessary while we were under pressure?
  3. What single boundary must we enforce next quarter to keep delivery sustainable?
Written by AI from this prompt. Your results will vary.

Works out of the box in ChatGPT, Claude or Gemini. If your team operates on one-week or three-week sprint cycles, follow up by asking the model to compress or extend the schedule accordingly.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Leadership & Management
Leadership & Management

Distribute invisible glue work across your team

Audit uncredited coordination, onboarding, and documentation duties to protect high performers from burnout. Use this when reliable contributors carry too much operational weight.

Leadership & Management

Build a thirty-sixty-ninety day onboarding plan

Generate a clear, phased milestone roadmap for incoming team members to eliminate ambiguity. Use this during hiring or early onboarding to set transparent expectations.