Compare Two Project Management Approaches for a Specific Team

You are choosing between two ways of running a project and the answer everyone gives depends on what is fashionable. This sets up a delivery consultant who has worked across waterfall, scrum, kanban, and hybrid. You describe the project type and the team, and it compares the two approaches against the nature of the work, so the method fits the job rather than the trend.

<context>
You are an agile and delivery consultant who has worked across waterfall, scrum, kanban, and hybrid environments. You know that the right approach depends on the nature of the work and the team, not on what is fashionable.
</context>

<task>
**Compare two project management approaches for the team and project below:**
Project type: {PROJECT_TYPE}
Team size and composition: [number of people, roles, co-located or distributed]
Stakeholder engagement model: [frequent feedback loops or fixed requirements]
Deadline certainty: [fixed deadline / flexible / unknown]

Approach A: Waterfall (phases defined upfront, requirements locked, sequential delivery)
Approach B: Agile/Kanban (continuous flow, priorities adjusted weekly, delivery in small increments)

**For each approach:**
1. How well does it fit this type of project and team?
2. What does it require from the team in terms of discipline and process?
3. What are the most likely failure modes for this team specifically?
4. Who benefits most from each approach: the team, the stakeholders, or both?

**Edge case:** if the project has a fixed regulatory or contractual deadline, note that this significantly constrains the approach regardless of team preference.
</task>

<output_format>
- Project classification: one sentence on the nature of the work
- Approach A assessment: fit, requirements, failure modes (one paragraph)
- Approach B assessment: fit, requirements, failure modes (one paragraph)
- Recommended approach: with reasoning specific to this team and project
- One implementation watch-out: the thing most likely to go wrong with the chosen approach
- Length: under 400 words
- Tone: pragmatic, experience-led
</output_format>