The two worlds of PRINCE2 project management and agile have just become a lot more interesting:
AXELOS is developing new guidance to bring the best of PRINCE2 and agile together for the benefit of practitioners everywhere irrespective of which side of the fence they come from.
With the working title "PRINCE2 agile", this new initiative is equally significant and exciting for organizations and individuals who may be using PRINCE2 and looking at agile or may already be agile and are looking at PRINCE2 for more control. The former will have definitive guidance and clarification on how to control projects where agile methods and techniques, whilst the latter will understand how to incorporate PRINCE2 to achieve the same result. Either way individual practitioners from both camps will have a way of extending their expertize and knowledge. Certainly, the tendency for some of the PRINCE2 and agile advocates to denigrate each other's approaches should now be consigned to history.
The launch date for this is Q1 2015; the author for the new guidance has been selected and I hope you share our faith in that choice: Keith Richards of agileKRC, and his agile capabilities, pre-date even the founding of the Agile Manifesto! He is both an agile thought leader (voted "Most Valuable Agile Player UK" at the Agile Awards in 2011) and has a solid understanding of the relationship between PRINCE2 and agile. Along with talking directly to other agile gurus globally during the research process, he will be working alongside nominated mentor Larry Cooper of BSSNexus Global Inc. in North America to get his regional perspective. Larry has been involved in incremental and iterative delivery approaches since the early 1990's, has applied agile practices to procurement and business process design, and was a reviewer for Rod Collin's latest book "Wiki Management: A Revolutionary New Model for a Rapidly Changing and Collaborative World" which brings agile thinking to executive ranks.
The genesis of this new direction is not accidental. AXELOS has set this project in motion after listening to the community and investing in something the community has asked for specifically. In fact, the notion of "including agile" and understanding how it could fit with PRINCE2 was at the top of everybody's wish list. The result is another major new product development within the AXELOS portfolio.
The growth in people and organizations using agile approaches and techniques has raised its profile; and while welcoming it, the community has mooted the point of giving agile more rigour. Though we're not accusing agile of living up to the "Fr-agile" moniker used by some, having a relationship with PRINCE2's project governance and control qualities will go some way to reassuring its critics. Above all, we see PRINCE2 and agile as complementary rather than adversarial in the bigger picture of collaborative working.
Ultimately, PRINCE2 agile will benefit any project where PRINCE2 is applied and the team want to introduce agile, or where an agile approach needs to exhibit greater control. The marriage of the two approaches will help organizations to understand whether their investment in a project is worthwhile.
But what about the practicalities of, metaphorically, bringing "Mars and Venus" together?
Using PRINCE2 instils an organization's management control over its investments while agile offers an approach that is iterative and operated in short bursts.
However, once a project manager agrees the scope of work - or "work package" - with a team manager, PRINCE2 doesn't dictate how the team manager has to deliver the work. If the industry norm is an agile approach, there's nothing in PRINCE2 that disallows it.
Despite my assertions, sceptical people in the agile community might remain suspicious of PRINCE2. But they should see it as their ally in getting projects funded in the first place! The organization needs a business case for your development plans and, for that, you need look no further than PRINCE2.
Rather than being a marriage of opposites, I consider PRINCE2 and agile highly complementary. For example, in new product development a business case is required; once that and the investment are established, the development process can occur in an agile way. One approach supplements the other while managing the risks of the wider project.
And this has an application to broader project and programme management. If projects adopting agile exist within a programme, AXELOS' Managing Successful Programmes (MSP®) should naturally accommodate the agile approach via PRINCE2. Likewise, Management of Portfolios (MoP®) will be able to incorporate PRINCE2 agile to ensure investments concur with the strategic intent of the organization.
Regarding the intermingling of PRINCE2 and agile, we have previously produced complementary publications to show how PRINCE2 fits with a particular agile approach, for example the Dynamic Systems Development Method (DSDM), recently hailed by the Society of Information Technology Management (SOCTIM) as a product and service development approach that combines the best of agile and PRINCE2.
However, in proposing PRINCE2 agile we want to show how it works with all agile approaches and become the definitive best practice guidance for blending the two. I think you would expect nothing less from the owners of PRINCE2!
This initiative is aimed at taking the debate wider than any other alternative instruction currently available on the market; to cover more of the agile approaches, bring in the latest thinking from agile communities and create something that's more comprehensive and inclusive.
That's quite a project - but I think you'll agree, the interest and demand is there.