How to use SCRUM properly with PRINCE2 project management?

Case study

Description of the need for the project

The sales and marketing department found it increasingly difficult and difficult to manage its business activities using Microsoft Excel. The team expanded and people were on the move, with frequent visits to clients, meetings, product demonstrations, etc. In accordance with the PRINCE2 methodology, the sales and marketing department created a Business Case with requirements for internet applications that would enable efficient management of its market and sales functions. The business case was approved and the project was started.

How did we map PRINCE2 and SCRUM together in task-by-task mode?

Task 1:

Defining roles and responsibilities (PRINCE2)

Senior User (PRINCE2) specifies the Product Owner (SCRUM).

The Senior User is responsible for specifying the needs of those who will use the project products. Senior User is set up as the owner of the product. Senior User defines customer expectations in terms of quality and defines the acceptance criteria of the project product. Acceptance criteria are part of the project product description (PRINCE2)

Task 2:

Product-based planning (PRINCE2) generates a Product Backlog (SCRUM)

The product breakdown structure (PRINCE2) is mapped to the Product Backlog (SCRUM).

The philosophy behind the development of plans in PRINCE2 requires that the products be defined first, and only then the necessary activities, dependencies and resources for the delivery of those products. This is known as “Product based planning” and is used for Project Plan, Stage Plan and, optionally, Team Plan.

Modules are mapped to Epics, sub-modules are mapped to Functions, and requests are mapped to User Stories. (SCRUM)

Task 3:

Tailoring of the PRINCE2 methodology in accordance with the project environment

PRINCE2 faze (Stages) se preslikavaju na SCRUM iteracije (Iterations).

Prilagođavanje se odnosi na odgovarajuću upotrebu PRINCE2 na bilo kom projektu, što osigurava da postoji tačno definisana količina planiranja, kontrole, upravljanja i upotrebe procesa i tema PRINCE2. Izazov ovde je preslikavanje trajanja faza PRINCE2 u cikluse iteracije SCRUM-a. Iteracije SCRUM-a su obično traju dve do četiri nedelje. Ako se svako trajanje faze upravljanja PRINCE2 može prilagoditi ovom trajanju (što je uglavnom slučaj ukoliko se dobro prilagodi PRINCE2 – Tailoring Principle), lako možete koristiti SCRUM. Faze upravljanja PRINCE2 i iteracije SCRUM-a nesmeju se preklapati. Rezultati faze su backlog-ovi u iteraciji.

Task 4:

Creating and authorizing work orders (PRINCE2 Work Packages) – (Backlog Items – SCRUM)Radni nalozi se preslikavaju u backlog item-e.

PRINCE2 alocira rad na projektnim proizvodima koristeći radne naloge (Work Packages). Radni nalozi su izvedeni iz planiranja zasnovanog na proizvodima. Svaki radni nalog preslikava se u backlog. Senior User definiše i kontroliše prioritet backlog item-a. SCRUM tim uzima te backlog item-e, radi poker procenu, i rangira backlog item-e po vrednosti. Zatim se kreira backlog iteracije za samu iteraciju, tj. PRINCE2 fazu, na osnovu odabranih backlog item-a.

Task 5:

Ensuring efficient delivery by synchronizing MPD + CS + MSB processes

(Managing Product Delivery + Controlling a Stage + Managing Stage Boundary – PRINCE 2)

The evaluation of each phase (PRINCE2 end stage assessment) is mapped to the SCRUM sprint review.

At the end of the current phase, in PRINCE2, we plan the next phase in the Managing a stage Boundary process. It maps perfectly with SCRUM. At the end of the sprint, a review of the sprint is held to show the potential product increment to the user (Product Increment). At this time, Business Case PRINCE2 is updated by adding profit to the achieved delivery of Product Increment. The plan of the next phase is created and sent for approval. The plan of the next phase corresponds to the next iteration. The team performs the assessment in the final phase, ie. Sprint Retrospective.

Conclusion and lesson:

By efficiently customizing PRINCE2 and using SCRUM, we were able to successfully deliver our user product. The user is satisfied with the new products, easy to correct and improved performance.

Contact the author Mario Bojadžić