PRINCE2 is a formal, structured approach to project management. Agile methods are a family of developer-oriented software engineering approaches. They are very different animals. How can they possibly work together?
Well, wait a minute. There's a clue in there: they are different animals; they're about different things. Different, but exceedingly complementary. PRINCE2 is about project management. It provides a framework for project managers to track the construction and delivery of products against a plan. Agile methods are about constructing software in a more responsive, more customer-focused way, with an emphasis on built-in quality.
In actual fact, they're a perfect fit! Let me try and convince you.
First off, PRINCE2 is as formal and structured as you need it to be. One criticism I've both read and heard first-hand is "all this formal process stuff just weighs us down and gets in the way". My response is always the same: "well, you're doing it wrong!" One the key principles of PRINCE2 is tailoring: take the framework and scale it down (or up!) to match the kind of project you're running. In fact, the 2009 revision to PRINCE2 reiterated its underlying simplicity by recognising explicitly seven principles:
- There is continued business justification for a project (or you should stop!).
- There are defined roles & responsibilities (everyone knows what they should - and should not - be doing).
- Manage projects by stages (bite-sized chunks are easier to track…