Presentations

PRINCE2 presentation by Jorgen Jacob

Agile Planning presentation by Peter Janssens

Fishbowl discussion

Strong points of both methods

Why would you combine PRINCE2 and Agile?

• To charge more
• To get management buy-in
• Compliance with internal and external regulators
• To add risk management, closing and initiation processes
• Formal steering
• As a trojan horse, a less scary way to introduce Agile
• To have a small paper trail
• To average out the extremes of both methods
• Give a (false) sense of control
• Large and/or critical projects need to be more formal
• Business can't cope with Agile (yet)
• Customer can't cope with uncertainty
• Stepping stone to more involvement

• Hide behind processes
• Can't explain - confusing
• Fake "the other" process
• Micro-management by project manager
• Huge amount of waste
• Need to master two sets of techniques, need to know two languages, need to go to two trainings.
• Project management task duplication
• Unclear role definitions
• Stop too early
• More focus on cost instead of value (change control board)
• Mismatch in expectations
• Fear to change the process
• Local optimisations (because everything must fit in the PRINCE framework)
• Culture fights
• C&C steering committee
• Blaming the "other side"

• Define one common language
• Either cloak Agile in PRINCE2 or add PRINCE2 practices to Agile
• Hide PRINCE2
• Introduce PRINCE2 techniques when needed
• Drop both terminologies
• Don't do it
• Start by mastering both
• Study existing experience
• Scale up slowly
• Lie
• Make only 'highlight' documentation
• Educate your customer
• Use SCRUM at the work package level
• Tailor PRINCE2 to only use the minimum needed

More resources

• Comparison spreadsheet between PRINCE2 and SCRUM
• Different models of combining PRINCE2 and SCRUM