PMM

1. There is no doubt that PRINCE2 is currently the most widely-recognized project management
methodology in the UK. The PRINCE2 qualifications are a standard feature of project management
job specifications, and PRINCE2 training is vital to any project role within a PRINCE2-aligned
organization.
However, the popularity of 'Agile' methods is spreading, and many managers are keen to implement
a more flexible and adaptive approach within their own business environment. Project managers
need to be informed about both methodologies to ensure both regular employment and project
success.
In this article we will explore the main differences between PRINCE2 and Scrum.
Key differences between PRINCE2 and Scrum
Probably the most fundamental difference between PRINCE2 and Scrum is that PRINCE2 is a
project management method whereas Scrum is a development method used by teams.
Scrum is a method which enables teams of software engineers to work together collaboratively with
the customer. This is done by defining and prioritize requirements, developing, testing and providing
feedback in a continuous and repetitive cycle of iterations. Scrum gives guidance to the team
members on how this can be done effectively. The kind of questions which Scrum helps a team
answer are “what needs to be delivered next week?” and “is the working software what the customer
needs?”
PRINCE2, on the other hand, is a method by which an organization can manage a project (whether
software or not) and provides guidance to the key stakeholders on how to ensure the project is
managed effectively. The kind of questions which PRINCE2 helps these stakeholders answer are
“why should we do it (the project)?” and “are the benefits worth the costs and risks of doing the
project?”
Predictive and adaptive approaches
Another key difference between PRINCE2 and Agile methods is that PRINCE2 is a predictive (plan-based)
approach, while Agile calls for short-term, incremental achievements independent of an over -
arching plan (the adaptive approach). This means that, while PRINCE2 projects might be more likely
to remain focused on the original business goals, Agile projects are more responsive to changes in
the project environment and customer requirements.
Scrum is one of the most widely-recognized Agile software development frameworks. Operating on
the principle that the development process is (predictably) unpredictable, Scrum works by
encouraging complete transparency, close collaboration and frequent delivery of usable sub -
products that will eventually contribute to the final product delivered.

2. Self-organization of teams
Central to Scrum is the self-organisation and independence of the team members. Plan-oriented
methodologies such as PRINCE2 require a project manager and team managers to plan, allocate
and monitor the distribution of tasks. Assignments might be determined by membership of a
particular team after undertaking critical path analysis, rather than by direct consideration of the
individual’s particular skills or strengths.
Within a Scrum-aligned project, on the other hand, all tasks are up for grabs. A Task Board and
Burndown Chart display are the tasks that need to be completed and the tasks remaining during any
given “Sprint” (cycle of product development). This means that any developer may chose to work on
any available task, according to their skill-set and time available.
There are clear advantages to the Scrum framework, which allows greater freedom to team
members, thereby encouraging greater personal investment in the project. The more structured
approach of PRINCE2, however, does go further in ensuring that the project goals are tackled in an
efficient and organised manner.
The requirements churn of Scrum represents another key difference between the two philosophies.
This term is frequently used to describe the Scrum principle that customer requirements can and will
change over the course of the project, forcing Scrum developers to adopt a flexible and responsive
approach to their collaboration with the client.
PRINCE2 manages changing requirements through change control
PRINCE2, in contrast, requires that Acceptance Criteria (the required features of the final product)
remain fixed, with any proposed changes to be filtered through a change control board and an
agreed change control process. This has important advantages in terms of ensuring that customers
know what to expect and developers do not have to deal with inconsistent or unconsidered customer
demands, but it also deprives the project, the customer and the development team of the opportunity
to respond directly to changes in the environment and expected function of the product.
Neither PRINCE2 nor Scrum provides comprehensive, step-by-step instructions to ensuring project
success. Both have been described as flexible, adaptable frameworks that provide role descriptions,
sets of practices and management documents/artefacts. While PRINCE2 focuses on the role of the
project manager in planning, organizing and adjusting the transformation of project inputs into
product outputs, Scrum is designed to allow a freer reign to all individuals involved on the project,
enabling a more responsive and creative, as well as a more vulnerable, environment.
Conclusion
So, is there a half-way house between PRINCE2 and Scrum - one which is able to leverage the
benefits of both approaches? I think there is and it's in the form of 'Agile' project management. Agile
project management enables a project manager to gain both the benefits of a more predictive
approach (PRINCE2) with the benefits of a more adaptive approach (Scrum).
.