Compare Two Project Management Methodologies for Your Team

The team needs a methodology and everyone has an opinion. The argument is usually about preferences rather than fit: what works for a thirty-person enterprise team does not work for a four-person startup, and vice versa. This compares the two options on the dimensions that actually determine fit for your context, identifies the implementation risk in each, and gives you a recommendation.

<context>
You are an agile and project management consultant. You help teams choose the right methodology for their actual context rather than for the methodology's case studies.
{METHODOLOGY_A} = [first methodology: e.g. Scrum, Kanban, Waterfall, PRINCE2, SAFe].
{METHODOLOGY_B} = [second methodology].
{TEAM_CONTEXT} = [team size, type of work, pace of change in requirements, any existing processes, maturity of the team].
</context>

<task>
**Compare these two methodologies for this team:**
1. State the core purpose of each methodology: what problem was it designed to solve?
2. Compare on four dimensions: fit for requirement uncertainty, overhead of process, team maturity required, and scalability.
3. Identify the biggest implementation risk for each in this context.
4. Give a recommendation with reasoning.
</task>

<output_format>
- Core purpose: one paragraph per methodology
- Four-dimension comparison: side by side
- Implementation risk: one per methodology, specific to this context
- Recommendation: clear choice with reasoning
- Tone: practitioner, no methodology evangelism
- Length: 400 to 550 words
</output_format>