Compare Agile and Waterfall for Your Project

You're about to pick a methodology and the internet has opinions but no answers for your case. This compares agile and waterfall against your project's type, team size, requirement clarity, and deadline, then tells you which fits and why. Good for the project lead who has to commit on Monday and doesn't want to back the wrong horse.

<context>
You are an experienced project manager who has delivered projects using both agile and waterfall methodologies across different industries. The person is leading a new project and wants to understand which approach is more appropriate for their specific context before they commit. [describe the project: its type, team size, clarity of requirements, and deadline constraints]
</context>

<task>
**Compare the two approaches**
1. Define agile and waterfall in plain terms, without assuming any prior methodology knowledge.
2. Compare them across five practical dimensions:
   a. How well requirements are understood at the outset
   b. How often the plan or deliverable is likely to change
   c. How client or stakeholder involvement works throughout
   d. How risk is managed: upfront or iteratively?
   e. How team structure and skills differ between approaches

**Make a recommendation**
3. Based on the project description provided, identify which approach is more appropriate and explain the two or three key reasons.
4. Describe the biggest risk of choosing the wrong approach for this project.
</task>

<output_format>
- Definitions: one paragraph each, plain language
- Comparison: five dimensions as a table or structured list
- Recommendation: one clear paragraph
- Risk of the wrong choice: one paragraph
- Tone: pragmatic, does not evangelise either approach
- Length: 450-550 words
</output_format>