PRINCE2 & Agile

Let us build your new home on the web

Waterfall or Agile - let us manage your project

We are qualified and experienced project managers (PRINCE2 Foundation and Practitioner level qualifications). We can work within either waterfall or agile project management environments - each has its benefits and works well when applied correctly.


PRINCE2 has a long and venerable history as a project management methodology, and is still the tool of choice for many major projects and programmes. PRINCE2 provides a highly structured approach to project management and is very useful in structured environments and where requirements can be precisely defined.

Using Agile methodologies

Agile techniques are being used increasingly commonly in software development projects in particular. The Agile way is appealling for a whole range of reasons:

  • It is light-touch.
  • It is flexible to cope with changing project requirements.
  • The focus is on delivery of working product in preference to structure and reporting.
  • It provides excellent tools for highlighting and addressing drift.
  • There is a very strong focus on client participation and decision-making
  • Did we mention that the focus is on delivery?

Agile works well in environments where requirements cannot be settled at the beginning of the project (by the way, this means most projects that we have worked on over the years!), as it permits rapid prototyping and throwing away of features and releases that don't work. Implicit in the Agile approach are the ideas of test-centred development and light-touch documentation and reporting. Testing as a core part of the development process aids in minimising bugs (since they tend to get dealt with soon after appearing) and avoids the common phenomenon of the squeeze on available time for testing that often happens in a waterfall environment towards the end of the project.

Use both! Use the parts that add value, leave the rest alone

Ask anyone who has done serious project management, and they will tell you that slavish adherence to any single methodology is a bad idea. Project management tools are great servants but poor masters, and it's important to know where to take useful features from a methodology and where to leave them in the drawer.