Methodologies

If you have spent any time in project management circles, you will have heard passionate arguments for and against Agile, Waterfall, PRINCE2, Scrum, and half a dozen others. These debates can obscure a more useful insight: no methodology is inherently superior, and every methodology is a set of choices about how to organise time, decisions, and accountability under uncertainty. The question worth asking is not "which methodology is correct?" but "what is the nature of this project's uncertainty, and which approach is best suited to navigating it?"

Why it matters

Methodology mismatch is one of the more wasteful problems in project management. Applying a detailed upfront planning discipline to a project that is exploratory by nature produces plans that are irrelevant by the time they are printed. Applying an iterative, evolving approach to a project that has fixed regulatory requirements and a non-negotiable deadline produces a project that misses the deadline. Both errors are preventable, but only if the project manager has enough methodological literacy to recognise what kind of problem they are actually facing.

For Irish SMEs and charities, there is an additional pressure: most teams have neither the time nor the budget to master multiple methodologies in depth. What they need is a working understanding of the main approaches, their respective strengths and constraints, and the judgment to choose appropriately, or to borrow sensibly from each.

Core concepts

The oldest and most familiar structured approach to project management is the predictive (or Waterfall) model, which organises project work into sequential phases, requirements, design, build, test, deploy, with each phase fully completed before the next begins. The Waterfall approach works well when requirements are stable and well-understood from the start, when the deliverable is fixed, and when the cost of late change is very high (as in construction, infrastructure, or regulated manufacturing). Its weakness is inflexibility: a requirement that changes after the build phase has begun is expensive to accommodate, and a test phase that reveals fundamental design flaws cannot go back cheaply.

The Agile movement emerged as a direct response to these constraints in software development. In February 2001, seventeen software practitioners gathered in Snowbird, Utah and produced the Manifesto for Agile Software Development, which placed four values at the centre of their philosophy: individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; and responding to change over following a plan (Beck et al., 2001). The manifesto's twelve supporting principles reinforced the priority of working deliverables, close customer collaboration, and short iterative cycles over long planning phases. The key insight was structural: if requirements will change, and in most real-world projects, they will, then building in the capacity to respond to change is not a compromise on rigour, it is rigour.

Scrum is the most widely used Agile framework. Developed by Ken Schwaber and Jeff Sutherland, and maintained as a freely available reference document at scrumguides.org, Scrum organises work into sprints, time-boxed cycles, typically two to four weeks long, at the end of which a working, potentially shippable increment must be delivered (Schwaber and Sutherland, 2020). Scrum uses three roles (the Product Owner, who holds the product vision; the Scrum Master, who facilitates and removes obstacles; and the Developers, who do the work), three artefacts (the Product Backlog, the Sprint Backlog, and the Increment), and five events (the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective). Its power lies in the regular, forced feedback loop: every sprint ends with a demonstration of real work and a retrospective conversation about how to improve the process.

PRINCE2 (PRojects IN Controlled Environments), maintained by AXELOS, is a structured, process-based methodology that is widely used in UK and Irish public sector and government-funded projects (AXELOS, 2017). Where Agile prioritises flexibility and iteration, PRINCE2 prioritises controlled change, clear accountability, and documented justification for every project decision. It provides seven principles, seven themes, and seven processes that together create a comprehensive governance framework for project delivery. PRINCE2 Agile, a hybrid version, attempts to combine PRINCE2's governance rigour with Agile's iterative delivery approach.

PMI's PMBOK Guide, most recently published in its seventh edition in 2021, has evolved from a prescriptive process framework toward a principles-based guide that explicitly accommodates multiple delivery approaches, predictive, iterative, incremental, and hybrid (PMI, 2021). The shift reflects the industry consensus that most real projects are neither purely Waterfall nor purely Agile: they involve some elements that are well-defined and benefit from planning, and some elements that are exploratory and benefit from iteration.

The Irish context

The adoption of Agile methodologies in Irish organisations has grown substantially over the past decade, driven primarily by the country's large technology sector, home to the European headquarters of Apple, Google, Meta, and Microsoft, among others, where iterative product development is the norm (IDA Ireland, 2024). The practices and tools developed in these environments have migrated into the wider SME ecosystem, supported by communities like Agile Ireland, which hosts events and meetups across the country.

For Irish charities and public-funded projects, PRINCE2 and PMBOK-aligned approaches have historically been more common, particularly for projects funded by state agencies or EU structural funds, which typically require formal project documentation, milestone reporting, and change control processes. The governance requirements of the Charities Governance Code, documented decision-making, change controls, risk registers, are in many respects more compatible with PRINCE2's structured approach than with Scrum's iterative rhythm.

The most practically useful insight for small Irish organisations is that the methodology does not need to be wholesale adopted. A small charity implementing a new CRM system might use a light-touch Agile approach for the internal configuration and testing work, while maintaining a PRINCE2-style project board and milestone reporting structure to satisfy its funder's oversight requirements. This hybrid approach is increasingly recognised by PMI, Agile Alliance, and AXELOS as the practical reality for most projects.

Common pitfalls

Three failures recur. The first is methodology cargo culting, adopting the ceremonies and vocabulary of a methodology (daily standups, sprints, story points) without understanding or applying the underlying principles. Agile jargon without Agile values produces meetings about meetings and estimates about estimates. The second is methodology dogmatism, insisting that your chosen approach is always right and every other approach is wrong. Real projects require judgment, not loyalty. The third is adopting complexity before need. A three-person team delivering a six-month project does not need a full PRINCE2 governance structure; it needs a clear plan, a shared understanding of roles, and a weekly check-in. Methodology should reduce the cognitive overhead of coordination, not increase it.

Watch / Listen / Read

Watch, Build a tower, build a team by Tom Wujec (TED2010, 7 min). The marshmallow challenge, in which teams must build the tallest freestanding structure using spaghetti, tape, string, and a marshmallow, reveals why iterative prototyping, building, testing, and rebuilding, consistently outperforms detailed upfront planning. Essential context for understanding why Agile works. Available at https://www.ted.com/talks/tom_wujec_build_a_tower.

Listen, Scrum Inc Radio, the official podcast from Scrum co-creator Jeff Sutherland's organisation, covers practical Scrum and Agile implementation. Available at https://www.scruminc.com/scrum-inc-radio-podcast/. Useful alongside the free Scrum Guide at scrumguides.org.

Read, Beck, K. et al. (2001) Manifesto for Agile Software Development. Available at https://agilemanifesto.org/. The original 68-word document that launched the movement, read it alongside the twelve principles. Then read Schwaber, K. and Sutherland, J. (2020) The Scrum Guide. Available free at https://scrumguides.org/.

Quick quiz

1. Name the four core values of the Agile Manifesto.
2. In Scrum, what is the name for the time-boxed iteration during which a working increment must be delivered?
3. What does PRINCE2 stand for?
4. What key shift did PMI make in the seventh edition of the PMBOK Guide regarding delivery approaches?
5. Roughly where and when was the Agile Manifesto signed?

Answers: (1) Individuals and interactions; working software; customer collaboration; responding to change, each valued over its counterpart. (2) A Sprint. (3) PRojects IN Controlled Environments. (4) It moved from a prescriptive process framework to a principles-based guide explicitly accommodating predictive, iterative, incremental, and hybrid approaches. (5) Snowbird, Utah, USA, in February 2001.

References

AXELOS (2017) PRINCE2 6th Edition: Managing Successful Projects with PRINCE2. London: TSO.

Beck, K. et al. (2001) Manifesto for Agile Software Development. Available at: https://agilemanifesto.org/ (Accessed: 27 April 2026).

IDA Ireland (2024) Technology sector in Ireland. Available at: https://www.idaireland.com/why-ireland/sectors/technology (Accessed: 27 April 2026).

Project Management Institute (2021) A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th edn). Newtown Square, PA: PMI.

Schwaber, K. and Sutherland, J. (2020) The Scrum Guide: The Definitive Guide to Scrum. Available at: https://scrumguides.org/ (Accessed: 27 April 2026).