Project management methodology

Project management methodology is a structured framework of principles, processes, and practices that guides how projects are planned, executed, monitored, and completed, with major methodologies including Waterfall, Agile, and PRINCE2 (PMI 2021, p.18)^[1]. The software development team argues about process. One faction wants detailed requirements upfront and phased execution. Another demands iterative development with constant customer feedback. A third insists on formal governance structures. Each advocates for a different methodology—and each has contexts where they're right.

Methodologies matter because they shape how work gets done. The Waterfall model, introduced by Winston Royce in 1970, emphasizes sequential phases with clear handoffs. Agile methods, emerging in the early 2000s, prioritize flexibility and customer collaboration. PRINCE2, developed by the UK government in 1996, provides structured governance suitable for large-scale projects. Increasingly, organizations blend approaches—using PRINCE2's governance with Agile delivery practices, for instance.

Major methodologies

Common approaches include:

Waterfall

Sequential phases. Projects proceed through distinct stages: requirements, design, development, testing, deployment^[2].

Characteristics. Comprehensive upfront planning; limited scope for change once phases complete.

Best suited for. Projects with well-defined requirements, stable scope, and low uncertainty. Enterprise-level projects with strict deadlines.

Limitations. Inflexible to change; delays testing until late stages; limited customer involvement.

Agile

Iterative approach. Work proceeds in short cycles (sprints) with continuous feedback and adaptation^[3].

Characteristics. Embraces change; frequent delivery of working software; close customer collaboration.

Frameworks. Scrum (sprints, daily standups, retrospectives); Kanban (visual workflow, continuous flow).

Best suited for. Projects with evolving requirements, need for quick delivery, or significant uncertainty.

PRINCE2

Structured governance. Seven principles, seven themes, and seven processes provide comprehensive project control^[4].

Characteristics. Clear roles and responsibilities; business case justification; stage-gate decisions.

Best suited for. Large-scale projects requiring accountability and formal governance; public sector projects.

Comparison

Key differences:

Approach

Waterfall. Linear, phase-driven, plan-focused.

Agile. Iterative, adaptive, value-focused^[5].

PRINCE2. Controlled, stage-based, governance-focused.

Customer involvement

Waterfall. Requirements gathered upfront; limited ongoing involvement.

Agile. Continuous involvement throughout; frequent feedback^[6].

PRINCE2. Defined stakeholder roles; regular decision points.

Flexibility

Waterfall. Resistant to change once phases begin.

Agile. Embraces change as competitive advantage.

PRINCE2. Can accommodate change through formal change control.

Choosing a methodology

Selection depends on context:

Project characteristics. Uncertainty levels, scope stability, delivery urgency^[7].

Organizational culture. Some organizations favor structure; others value flexibility.

Industry norms. Regulatory requirements may mandate certain approaches.

Team capabilities. Available skills and experience with different methods.

Hybrid approaches

Blending methodologies:

PRINCE2 Agile. Combines PRINCE2's structure with Agile's flexibility—governance at the project level, Agile at the delivery level^[8].

Scaled Agile. Frameworks like SAFe apply Agile principles at enterprise scale.

Pragmatic blending. Many organizations customize, taking elements that work from multiple methodologies.

Project management methodology — recommended articles

Project management — Agile methodology — Waterfall model — PRINCE2

References

• PMI (2021), A Guide to the Project Management Body of Knowledge, 7th Edition.
• Axelos (2017), Managing Successful Projects with PRINCE2, 6th Edition.
• Schwaber K., Sutherland J. (2020), The Scrum Guide.
• Kerzner H. (2017), Project Management: A Systems Approach, 12th Edition.

Footnotes

1. ↑ PMI (2021), PMBOK Guide, p.18
2. ↑ Kerzner H. (2017), Project Management, pp.67-82
3. ↑ Schwaber K., Sutherland J. (2020), Scrum Guide, pp.3-8
4. ↑ Axelos (2017), Managing Successful Projects, pp.23-45
5. ↑ PMI (2021), PMBOK Guide, pp.89-104
6. ↑ Schwaber K., Sutherland J. (2020), Scrum Guide, pp.9-14
7. ↑ Kerzner H. (2017), Project Management, pp.234-248
8. ↑ Axelos (2017), Managing Successful Projects, pp.312-328

Author: Sławomir Wawak