You are on page 1of 1

Project Management methodologies compared

About Pros Cons


PRINCE2 Invented by the UK government in 1985 for large Gives an overview of all projects Expensive to learn and to implement
IT projects (and look at them!)
Gives control of projects – they can’t Too complicated (just google it and see
Broadened out to all projects in 1995: PRINCE be started or progress to next stages for yourself)
‘2’ without sign off
Doesn’t tell you HOW to do anything e.g.
Very popular since then Forces management to engage with the how to estimate tasks. Not even how to
PM process use Gantt charts. Just certifies that there
In decline now is a plan, signed off by the board.
Great if you are doing one big project
Product extension called MSP and you a full time PM Too boring for normal staff to engage with
Has a multiple choice test at the end which is a I’ve never seen it work successfully
sort of qualification

APM Association of Project Management Very practical The PMBOK can be too complicated –
needs to be boiled down and just the good
Been around for 100 years, it’s the combined Tells the PM everything they need to do bits used, (which is what my course does)
experience of 1000s of real Project Managers in the process of planning and
implementing a project Does require a list of all tasks, and
All their knowledge is in an ever increasing tome estimates of all tasks, at the start –
called the PMBOK (Body of Knowledge) Allows you to forecast finish time and though risk planning recognises that some
cost at any point during your project
Has a qualification called PMP (Project of these will change during the project.
Management Professional) which is well Recognised in USA as well – they call it
respected PMI over there.

Agile / The latest trendy thing being pushed by Acknowledges the risk involved in Not able to predict finish time or total
consultants creative processes. cost, unless these are fixed and the
Scrum deliverables are allowed to be completely
Based on remaining flexible when there is Sounds fun and exciting. flexible.
uncertainty in the project, e.g. software design
Great if you’re not sure what you want So not really a plan at all, more a weekly
Contains terms like “Sprints”, “Burndown yet. time management meeting. (Those are
charts”, and “Scrum masters”. good, but not enough!)
All the risk is with the customer

You might also like