Difference between revisions of "An Overview of PRINCE2 Agile"

From PRINCE2 Agile wiki
Jump to: navigation, search
(Other pages)
(External Links)
(4 intermediate revisions by the same user not shown)
Line 154: Line 154:
* [http://prince2agile.wiki/PRINCE2_Agile_Glossary PRINCE2 Agile Glossary]
* [http://prince2agile.wiki/PRINCE2_Agile_in_Practice PRINCE2 Agile in Practice]
* [http://prince2agile.wiki/PRINCE2_Agile_2017#List_of_all_PRINCE2_Agile_2017_products PRINCE2 Agile 2017 - Changes]
== External Links ==
== External Links ==
Line 162: Line 163:
* [http://mplaza.pm/free-prince2-agile-course/ PRINCE2 Agile Awareness, One Step a Day], a free introductory email-based course
* [http://agilepm.wiki AgilePM wiki]
* [http://agilepm.wiki AgilePM wiki]
* [http://prince2.wiki/What_is_PRINCE2 What is PRINCE2]

Latest revision as of 09:33, 6 June 2019

PRINCE2 Agile is a new concept from AXELOS (the owner of PRINCE2), which is a tailored form of PRINCE2, suitable for Agile environments such as Scrum. PRINCE2 Agile does not contain an Agile delivery method, and supports the existing ones instead.






PRINCE2 Agile is described in an official manual with the same name, which is available in hardcopy and PDF at the TSO webshop, and other online book stores such as Amazon.

PRINCE2 Agile Practitioner candidates can only use this book during their open-book exam.

The manual is not prepared by a group of experts, but by a single author. A number of contributor and reviewers have had some involvement in the process as well.

Process Model

PRINCE2 Agile Process Model state02.png



  • The diagram is schematic and many details are not shown.

Stages are still set based on the management needs of the project, rather than turning into iterations. Each Stage contains one or more "release", and each "release" contains one or more "iterations". Iterations are usually called "timeboxes" in PRINCE2 Agile.

Plans are created as usual, with the default responsibilities. Then Work Packages would be the basis for creating the release plans and iteration plans (Team Plans), while their high-level aspects have been defined in the Project Plan and Stage Plans from the beginning.

Delivery team members are empowered to decide on minor changes, as long as they do not affect the Category:Management Products directly. Otherwise, the usual change control process would be run, with escalations based on tolerances. Therefore, a limited level of adaptation exists in the delivery layer, and higher-level adaptation would happen in the higher layers, and specially in the Managing a Stage Boundary Process.

The suggested approach in PRINCE2 Agile is to have fixed time and cost for the project, similar to DSDM Atern. Consequently, the contract would be fixed-price. When the customer asks for a new feature, they have to swap it for one (or more) of the initial features mentioned in the contract, with the same size.

PRINCE2 Agile defines Agile as a set of behaviors and practices rather than the use of an adaptive lifecycle, and consequently, the manual is focused on providing generic guidelines on common behaviors in Agile environments rather than providing a complete integration between the PRINCE2 process model and Agile lifecycle.

Tailoring done on PRINCE2






Management Products



Roles and Responsibilities


While PRINCE2 Agile frequently mentions the Scrum roles such as Product Owner and Scrum Master, as if they are a fixed part of the team, still does not considers them as default roles, and uses the more generic roles mentioned below. More on this in the Organization Theme's page.

The original PRINCE2 responsibilities tables have not adjusted to include the new roles, or reflect any tailoring. The new roles are not even mentioned much through the manual and it's not clear how they are supposed to be used, and how they are connected to the rest of the methodology.

Extra Concepts




Other pages

External Links