# Cut scope to hit a fixed release date

Scope-cut options ranked by value lost versus time saved, plus how to present the trade-off to stakeholders.

- Topic: Projects & Operations
- Framework: RTF
- Level: Standard
- Tags: Rewrite & Edit, Fill-in Template
- Source: https://www.thinkwithprompt.com/prompts/cut-scope-to-hit-a-fixed-release-date

## Prompt

```text
Help me cut scope so we can still hit a fixed release date.

**Release goal and date:** [WHAT MUST BE TRUE AT LAUNCH, AND WHY THE DATE IS FIXED]
**Current scope:** [ITEMS WITH ESTIMATES AND STATUS]
**Remaining capacity:** [TEAM, WORKING DAYS LEFT, KNOWN ABSENCES]
**Gap:** [HOW FAR OVER WE ARE, IF KNOWN]
**Commitments already made:** [TO CUSTOMERS, SALES, MARKETING]

Steps:
1. Separate must-have from nice-to-have by asking: without this, does the release still achieve its goal for the core user?
2. For each candidate cut, consider options short of removal: simplify, make manual, limit to one segment or platform, ship behind a flag, follow up in a fast second release.
3. Estimate time saved versus value lost for each option.
4. Identify risks we must not cut: quality, security, accessibility, data integrity, legal requirements.

Return:
- A table: Item | Option | Time saved | Value lost | Who is affected | Recommendation.
- The recommended scope package that fits capacity with a small buffer.
- What moves to the follow-up release, with a target window.
- A message to stakeholders explaining the trade-off, what they still get, and what changes for anyone we made commitments to.

Do not suggest cutting testing or quality checks to save time.
```

## What to fill in

- WHAT MUST BE TRUE AT LAUNCH, AND WHY THE DATE IS FIXED
- ITEMS WITH ESTIMATES AND STATUS
- TEAM, WORKING DAYS LEFT, KNOWN ABSENCES
- HOW FAR OVER WE ARE, IF KNOWN
- TO CUSTOMERS, SALES, MARKETING

Free to copy and use. From ThinkWithPrompt (https://www.thinkwithprompt.com/), a library of 2,663 curated AI prompts.