This is the first post about the sessions I attended in the LAST Conference. The session was about SCRUM and Prince2, describing the similarities and the discrepancies.
Scrum is the by far the most popular AGILE Framework used for software Projects. It calls for time-boxed, iterative and incremental development process aimed at faster delivery to customer. It involves frequent inspections and adoption to maximize quality.
Prince2 is a process driven Project Management standard. Projects in Controlled Environments, as the name suggests, it emphasises on controlling the environment rather than micro-managing it . It works in Phases/Stages/Iterations. The seven core principles of Prince2 can be seen here.
Similarities between SCRUM and Prince2:
- SCRUM involves Sprints/Iterations i.e. work done in Phases. Similarly, there are stages in Prince2 environment.
- Retrospectives hold great important in SCRUM and so are the ‘Lessons Learnt” in Prince2.
- SCRUM and Prince2 both recognise decreasing complexity, improving quality and enhancing communication as primary goals.
- SCRUM is a lightweight framework which allows customisation. Prince2, as well, is an adaptable methodology.
- Both SCRUM and Prince2 have similar and comparable roles : (SCRUM Role/Prince2 Role) : Product Owner/Executive, Scrum Master/Project Manager and Team(s)/Delivery Team(s).
SCRUM and Prince2 differences:
- One SCRUM Team concentrates on delivery of one project while Prince2 looks after work across multiple teams.
- Project Resourcing and Procurement are not defined but assumed in SCRUM, while these are included explicitly in planning in Prince2.
- Regarding Risk Management, SCRUM stresses more on Risk Mitigation as opposed to Prince2, for which Risk Management strategy is an important part of Project.
- Sprints in SCRUM are generally 1-4 weeks. The stage duration is not specified in Prince2 specifications.
- Time-boxing is more stringent in SCRUM for all events. Prince2 allows timing changes, managed by Exception.
- Everything is inspected in SCRUM, while only programs are inspected in Prince2.
- The SCRUM Master collaborates actively with the team. Project Manager in Prince2 does not actively communicate with the team.
- Product Owner owns requirements whereas requirement ownership is not defined in Prince2.
- Scope changes in SCRUM are managed by Business. Delivery or Project Team takes ownership of scope changes in Prince2.
- SCRUM teams are self-managing and organising. On the contrary, Prince2 has a Delivery Manager identified.
Looking at all above, it is pretty much clear that SCRUM can be used within Prince2 for delivery of products. SCRUM and Prince2 complement each other in multiple ways and can be used effectively to develop high quality software while minimising time-to-market in a managed, structured Project Environment.