Many large organizations use a Prince 2 based project process. Generally this is based around securing advance funding for projects with a defined business case. Project boards can park any project by removing the authorization and budget for the next phase. Formal controls (highlight reports, checkpoints) ensure things aren’t going off track.
Scrum turns this on its head to an extent, in that the time and resources are already committed before a defined set of benefits are realized.
The adoption of scrum can be a headache in many organizations, but the change in mindset can be handled.
The following blog post provides a mapping between Prince 2 Process stages and their equivalents in Scrum (the creator is also a Certified Scrum Master and Prince 2 Practitioner)
http://www.julianonsoftware.com/?p=1300
Mapping Spreadsheet:
http://www.julianonsoftware.com/public-docs/prince2-scrum-checklist.xls
Three things jump out at me from this when thinking about the application of agile in many organizations:
The number of business critical prince process items appearing in “Sprint 0” (the first steps for many new scrum teams)
The mapping between the Scrum Master and Project Manager roles (many organizations have a difference in opinion)
The project controls for which there is rarely a formal equivalent in"BAU" i.e risk logs, product based planning
Any thoughts?
5 comments:
Hi Neil, Julian here, thanks for your views on my mapping doc.
As time goes on, I get a better feel for how PRINCE2 and Scrum relate. My project right now could easily be described as PRINCE2-based Scrum -- my biggest complaint with Scrum specifically is that it just doesn't give the Team a lot of guidance as to how to get on. Particularly if they're inexperienced with the level of trust given in Scrum, even very good senior people, they'll fumble around in the dark a lot and make expensive mistakes. As PM, I see it as my responsibility to not ONLY keep them focused on the right planning horizon, but 'top and tail' the Scrum process -- basics such as config management, making sure some form of quality planning is in place, the way the team interacts with the rest of the environment, business process change etc etc etc. No one else but the PM is thinking of this stuff, so PRINCE2 helps fill in these gaps. Mike Cohn, a very practical Scrum Practitioner and trainer has been considering writing a book on practical Scrum, and it's sorely needed to avoid future Scrum Master lemmings jumping off the 'the Team does all the stuff' cliff.
Being a PRINCE2 Practitioner and Approved Trainer, although I am not SCRUM certified, I'd very much like to point out that tailoring PRINCE2 to the individual project and organisational environment is far more important than going off the bureaucratic cliff and implementing PRINCE2 full scale.
PRINCE2 have 2 levels of stages; Management and Specialist and at specialist level we have the actual production methodology in place; in the case of Software Development projects, this is where SCRUM, XP or what not comes in.
Pairing a SCRUM master and PM role is in my view impractical, unless we are talking really small projects - the focus and requirements of the two roles are very different indeed.
As a PRINCE2 PM I have had SCRUM teams with SCRUM Masters and a Product Owner, with Work Packages authorizing the actual Sprints and their contents. Again, in PRINCE2, Quality Review Technique is optional, so a Sprint Review will fit in just as well, the point being that we do excercise quality control in accordance with our Project Quality Plan.
Also, PRINCE2 has very tight change control, through which the Product Owner can interface with the PRINCE2 PM on changes to the actual Sprint contents; PRINCE2 might attempt to be proactive, but it is not static and will allow for changes in a controlled manner.
It's really about being practical and not overly theorietical, in my view. Thank you for this post!
best regards,
Nikolaj Raahauge
Hi,
I am about to use Scrum in one of my Prince2-based projects, and I was looking for some experiences from other folks. Your post looked quite promising, unfortunately I couldn't open the files you linked from your article.
Any chance you could give me access?
Thanks and greetings from Hamburg,
Susanne
Hi gents,
I was looking forward to insights of e.g. Julian's regarding matching SCRUM and PRINCE II. As sutchi alrady stated (old, like a year ago)the links are behind a logon page.
Julian, are you willing to share your thoughts on this?
Thanks in advance!
JW
This is such an informative article and very clearly written. Every single thought and idea is direct to the point. Perfectly laid out. Thank you for taking your time sharing
how scrum relate to prince 2
Post a Comment