Design a fit-for-purpose delivery methodology for your team

Overview

Use this prompt when your team needs to move beyond rigid Scrum or Waterfall and design a customized delivery approach that fits your specific project context. This prompt is built for teams who need a fast, practical way to move from intention to execution.

In a delivery context, this prompt helps you align stakeholders, surface the right constraints, and structure the output so it is immediately actionable.

Prompt template

You are an experienced agile coach helping me design a fit-for-purpose delivery methodology for {{team_name}} at {{company_name}}.

## Team Context
- Team size: {{team_size}} people
- Product type: {{product_type}}
- Release cadence: {{release_frequency}}
- Current methodology: {{current_methodology}}
- Biggest pain points: {{pain_points}}
- Stakeholder expectations: {{stakeholder_needs}}
- Compliance/regulatory requirements: {{compliance_requirements}}

## Design a Custom Methodology

### 1. Diagnosis
- What is working well in the current approach? (Keep these elements)
- What is causing the most friction? (Root cause, not symptoms)
- Is the team over-processed or under-processed?

### 2. Methodology Blueprint
| Element | Recommendation | Why |
|---|---|---|
| Sprint/iteration length | | |
| Planning ceremony | | |
| Standup format & frequency | | |
| Review/demo format | | |
| Retrospective cadence | | |
| Backlog management | | |
| Estimation approach | | |
| Documentation level | | |

### 3. Ceremony Evaluation
For each proposed ceremony, evaluate:
- **Purpose:** What decision or alignment does this enable?
- **Cost:** Time spent x number of people
- **Alternatives:** Could async communication replace this?
- **Verdict:** Keep / Modify / Drop

### 4. Roles & Responsibilities
- Who owns the backlog? Who runs ceremonies? Who handles stakeholder communication?
- Identify any missing roles or responsibilities to assign

### 5. Metrics
- 3-5 team health and delivery metrics to track
- How often to review them and what actions to take when they move

### 6. Adoption Plan
- Week 1-2: Introduce changes incrementally (start with highest-pain-point fix)
- Week 3-4: Full methodology in practice
- Week 6: First retrospective on the new methodology itself
- Explicitly state what to stop doing immediately

How to use this prompt

• State the objective and the product context in one sentence.
• Add any constraints such as timeline, target users, or business metrics.
• Ask for a structured output (framework, checklist, or decision summary).

Prompt details