The PRINCE2 Agile® Practical Implementation Guide – Step-by-step advice for every project type

Jamie Lynn Cooke

• Publisher: ITGP
• Year: 2021
• eBook ISBN: 9781787783355
• Topic: Business
• Subtopic: Project Management
• Index: Business

The PRINCE2 Agile ® Practical Implementation Guide – Step-by-step advice for every project type, Second edition explains how the structured, management-driven PRINCE2 project governance framework can work cohesively with team-driven, quality-focused, responsive Agile methods.

This guide provides an overview of PRINCE2 ® and Agile before detailing the combined PRINCE2 Agile governance and project management framework. It also provides expert guidance on how to implement the PRINCE2 Agile framework in your organization, whether you have existing PRINCE2, Agile or waterfall structures in place, or you are implementing PRINCE2 Agile with no pre-existing frameworks.

The key to successfully implementing PRINCE2 Agile is understanding how it brings together PRINCE2 and Agile best practices into a cohesive framework, and how to adapt that framework to meet your organization's specific needs. This guide is structured to provide you with the core information that you need to understand how PRINCE2 Agile works, and implementation guidelines aligned to the needs of your organization and your projects.

Ideal for PRINCE2 Agile students, project managers, IT managers, senior managers, PRINCE2 users and Agile users, this guide will help you to successfully deliver high business value outcomes within the PRINCE2 Agile framework.

PRINCE2 Agile® is a registered trade mark of the PeopleCert group. Used under licence from PeopleCert. All rights reserved.

CHAPTER 1: OVERVIEW OF PRINCE2

PRINCE2 (PRojects IN Controlled Environments) is a project management and governance framework that is used in more than 150 countries.⁶ It provides senior management with ongoing assurance that their funded projects are generating the expected level of business value.

The PRINCE2 framework has the flexibility to be applied to projects of any type, size, duration, complexity, and scope, and is applicable to both Information Technology (IT) and non-IT projects.

PRINCE2 is based on the understanding that well-managed projects need:

•To start with a justified business case and an organized plan for delivering the identified business value.

•To progress in a way that enables the Project Delivery Team to generate the required outputs with ongoing assurance to senior management that:

∘Work is progressing.

∘Changes, issues, and risks are being managed.

∘Agreed timelines, budgets, and quality metrics are being achieved.

∘The business case for the project work continues to be justified.

•To complete the project with confirmation of the achieved business value, documented records of the project work (and closure), and feedback to the organization on lessons learned to benefit future projects.

The PRINCE2 framework achieves this with an integrated approach of:⁷

Seven principles that guide all of the project work:

1.Continued business justification: Is there a justifiable reason for starting the project that will remain consistent throughout its duration?

2.Learning from experience: PRINCE2 project teams should continually seek and draw on lessons learned from previous work.

3.Defined roles and responsibilities: The PRINCE2 project team should have a clear organizational structure and involve the right people in the right tasks.

4.Management by stages: PRINCE2 projects should be planned, monitored, and controlled on a stage-by-stage basis.

5.Manage by exception: PRINCE2 projects should have defined tolerances for each project objective to establish limits of delegated authority.

6.A focus on products: PRINCE2 projects focus on the product definition, delivery, and quality requirements.

7.Tailoring to suit the project environment: PRINCE2 is tailored to suit the project’s environment, size, complexity, importance, capability, and risk.⁸

Seven themes of project management disciplines that need to be enforced throughout the project lifecycle:

1.Business case: What value would delivering the project bring to the organization?

2.Organization: How will the project team’s individual roles and responsibilities be defined in order for them to effectively manage the project?

3.Quality: What quality requirements and measures are there and how will the project deliver them?

4.Plans: What steps are required to develop the plans and PRINCE2 techniques that should be used?

5.Risk: How will project management address the uncertainties in its plans and the project environment?

6.Change: How will project management assess and act on unforeseen issues or requests for change?

7.Progress: How will the ongoing viability and performance of the plans determine how (and whether) the project should proceed?⁹

Seven processes that comprise the full project lifecycle with detailed checklists of recommendations for each process:

1.Starting up a project.

2.Directing a project.

3.Initiating a project.

4.Controlling a stage.

5.Managing product delivery.

6.Managing stage boundaries.

7.Closing a project.

All of these are adaptable to suit any project environment.

The PRINCE2 framework also defines specific project roles and responsibilities that are necessary to implement these principles, themes, and processes effectively, specifically:

•The Project Board, a group that is responsible for the overarching management of the project and ensuring that the project is continuing to deliver its intended business value for the organization (or authorizing the closure of the project if the intended business value is not being achieved). Minimally, the Project Board comprises three key participants:

∘The Executive, who represents the senior management interests of the organization and has the ultimate decision-making responsibility for the project.

∘The Senior User(s), who represent the target audience that will be using the outputs from the project work and are responsible for making key decisions regarding the capabilities that the project team delivers.

∘The Senior Supplier(s), who represent the internal or external team that is delivering the required outputs. Where work is being undertaken by multiple teams, e.g. an internal development team and an external software vendor, the Senior Supplier role may be filled by a key representative from each team.

Other Project Board members are included as required to represent key functions across the organization, e.g. Quality Assurance, Customer Support.

•The Project Manager, who is responsible for the project delivery in accordance with the terms established by the Project Board, including allocating work; providing status updates; managing issues and risks; monitoring time, budget, scope, benefit, and quality tolerances; and raising exceptions.

There are other roles identified in PRINCE2, e.g. the Team Manager. These will be elaborated upon further in the PRINCE2 Agile implementation sections of this book.

In addition to the principles, themes, processes, and roles described, PRINCE2 identifies a number of project artifacts that need to be developed to authorize the project to begin and to ensure effective ongoing project management, including the project brief, the project initiation documentation (PID), the project product description, the benefits review plan, stage plans, highlight reports, checkpoint reports, exception reports, the configuration item record, the issue register, and the risk register. These will also be elaborated upon in the implementation sections.

To ensure that PRINCE2 is executed effectively, there is a structured PRINCE2 qualification scheme that provides globally recognized confirmation of two levels of PRINCE2 knowledge:

1.Foundation

2.Practi...

Table of contents

• Cover
• Title
• Copyright
• Dedication
• Foreword
• Preface
• About the Author
• Acknowledgements
• Contents
• Introduction
• Chapter 1: Overview of PRINCE2
• Chapter 2: Overview of Agile
• Chapter 3: Overview of PRINCE2 Agile
• Chapter 4: Five keys to PRINCE2 Agile success
• Chapter 5: Step-by-step guidelines for all PRINCE2 Agile projects
• Chapter 6: Moving from PRINCE2 to PRINCE2 Agile
• Chapter 7: Merging Existing PRINCE2 and Agile Methods
• Chapter 8: Moving an existing waterfall project to PRINCE2 Agile
• Chapter 9: Implementing PRINCE2 Agile with no existing framework
• Chapter 10: Moving from Agile to PRINCE2 Agile
• Chapter 11: Further expansion of PRINCE2 Agile
• Bibliography
• Further reading