PRINCE2 Practitioner Agile Flashcards

1
Q

What is a project and what are the five characteristics of a project?

A

A project is a temporary, flexible organisation that introduces change. It can be independent or within a larger programme of work. A business has to balance new projects with BAU operations. A project has five characteristics:

  1. Temporary
  2. Handles uncertainty
  3. Implements change
  4. Cross-functional
  5. Unique
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the integrated elements of PRINCE2 and how do they relate to one another?

A

Environment, process, themes, principles.

Principles guide best practice. The themes are the areas the principles can be practised. The processes are a stepwise flow of actions, and the environment is the context in which the project exists in.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the four management levels in a PRINCE2 project and the roles of each?

A

Corporate / Programme Management - provide Project Mandate, responsible for project finances and have final say on all decisions

Project Board (Project Executive, Senior User, Senior Supplier) - consists of the primary stakeholders from each respective party. Responsible for Project Assurance, progressing at state boundaries, delivering the project on time, within spec, and at the agreed cost and quality, change management. They are NOT responsible for day-tp-day running of the project.

Project Manager - responsible for day-to-day running of the project, change management (within tolerances set by the PB), and managing the Team Manager.

Team Manager - Optional role. PM delegates delivery of a smaller work package to the TM. Also responsible;e for quality checks and reporting and handling risks (within tolerances).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What should a good PB have?

A

Authority, credibility, capacity, ability to delegate

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are the three PM support roles and what are their responsibilities?

A

Project Assurance - role appointed by the PB (who are responsible for PA) and sits outside of the PM team. Responsible fo ensuring processes are implemented properly, quality f product, and each role is performed properly. Reports directly back to the PB.

Change Authority - Individual(s) appointed b the PB to authorisae changes to the timeline and scope of the project (they are the delegated authority). CA responsibility can be absorbed by any PM team role including the PM.

Project Support - administrative support for the PM team

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is a PM framework?

A

A project management framework is a structured approach that provides the foundational guidelines, principles, and practices for managing a project. It outlines the phases, processes, and tools that can be applied to a project but does not dictate how to execute the project in detail.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is a PM methodology?

A

A project management methodology is a specific, prescriptive approach to managing a project that includes defined steps, processes, and practices within a framework. It details how to accomplish the work within the framework, often with specific roles, responsibilities, and deliverables.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is the overall goal of the DP process and what principle does it support?

A

The Directing a Project (DP) process enables the PB to remain responsible for the project, ensure continued business justification and exercise overall control, whilst delegating day-to-day managing and non-critical decisions to less senior employees (manage by exception).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What are the four objectives of the DP process?

A

The four objectives of the DP stage are:

  1. Ensure there is proper authority to initiate, lead and close a project
  2. Deliver the project products
  3. Ensure project direction and controls are managed
  4. Review post-project benefits of product
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

When does the Directing a Project (DP) process start?

A

The Directing a Project (DP) process starts when the PB approves the Project Brief at the end of SU and continues until project closure.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What are the four points DP interacts with the project?

A
  1. Authorising Project Initiation (at the stage boundary of the SU and IP processes)
  2. Authorising a Stage Boundary or Exception Plan
  3. Authorising Project Closure (APC)
  4. Ad Hoc Guidance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

When does “Authorising Project Initiation” occur?

A

At the stage boundary of the SU and IP processes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

When does “Authorising a Stage Boundary or Exception Plan” occur?

A

A project can only move from one stage to the next with approval from the PB. At the end of each stage, the PB reviews the performance of the project against the BC, assesses CBJ and plans the next stage before making their decision.

During a stage, if the project deviates outside of the tolerances set by the PB, the PM must submit an Exception Report to the PB. This triggers the Stage Boundary process.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

When does “Authorising Project Closure (APC)” occur?

A

Normally occurs at the end of a project, but can occur sooner if approved by the PB.

APC is the last activity undertaken by the PB. It may require endorsement from C/P.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

When does “Ad-hoc Direction” occur and what are the five formats?

A

The PB may give informal advice to the PM team at any time, particularly during IP and at SB’s, in many formats:

  • Informal request - seek advice from the C /P and assist the PM
  • Escalated Issue Report - make decisions that fall within tolerances, but escalate to C/P if needed
  • Exception Report - Change to a key area of the project. Seek advice from C/P if necessary. Approve or decline the change, or terminate the project
  • Highlight report - Review project to ensure it is within specification and on-time, and report back to the C/P
  • General advice - Keep the PM informed of any relevant changes that may impact the project

The PM is responsible for deciding whether to escalate information to the PB.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the differences between PRINCE2 Agile and pure PRINCE2 related to the DP process?

A
  1. In PRINCE2, the PB receive information from the PM via reports. In PRINCE2 Agile, there is less reporting and the PB is encouraged to check the information themselves via Information Radiators (e.g. Jira boards, joining daily stand-ups).
  2. One can still have standard documentation and some PRINCE2 documentation is still needed, but one principle of the Agile manifesto “working software” and “customer collaboration” over “documentation”.
  3. Agile very much leans into the PRINCE2 principle of “Manage by Exception”. Teams and leadership with low Agile experience need to understand that features can be dropped to stick to time and cost.
17
Q

What is an important consideration for PRINCE2 Agile related to the DP process?

A

It is important to set expectations on product delivery at the start.

18
Q

What is a timebox?

A

Finite period of time with a hard deadline, in wich the team works towards a set goal. Time should not be changed the the work contained within should be prioritised and pushed to keep to the time restraint,

19
Q

What are the use cases for PRINCE2 and Agile

A

PRINCE2 is exclusively for projects and must be managed by a PM.

Agile is to manage BAU.

A lot of Agile principles and concepts can be brought into PRINCE2.

20
Q

What are the four points of the Agile Manifesto?

A

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

21
Q

What is Agile?

A

Agile is a set of related frameworks, concepts, techniques, and behaviours. It was a presented as an alternative to Waterfakll which was documentation heavy and not good at handling change.

Agile can be an iterative and timeboxed approach to delivery, a group of management products and check-ins (ways of working), or a set methodology (Scrum, Kanban, XP)

22
Q

What is a release?

A

A set of features, fixes, or improvements that are built, managed, tested, and released to the production environment together.

The term “Deployment” can also be used interchangeably, but not in PRINCE” Agile.

23
Q

What is flow-based working?

A

Way of working that does not rely on putting work into timeboxes, but instead pulling from the backlog when needed

24
Q

Describe the Agile DevOps way of working.

A

Collaborative approach that brings Development and Operations as close together as possible, ideally in the same team.

25
Q

Describe the Agile Kanban way of working.

A

A methodology that allows backlog and sprint visualisation and active management and limitation of WIP via the use of columns.

26
Q

Describe the Agile Scrum way of working.

A

Iterative, timeboxed methodology of product delivery.

27
Q

Describe the Agile Lean way of working.

A

An approach that focuses on efficiency, reducing waste, and maximising value through process streamlining.

28
Q

Describe the Agile Lean Start-Up way of working.

A

Agile-based approach to setting up a team or a company.

29
Q

Describe the SAFe (Scaled Agile Framework) framework

A

Large-scale application of Agile across an organisation, or within a large or complex project.

30
Q

Why can’t DSDM or Agile PM be used inside of PRINCE2?

A

Because DSDM / AgilePM is already a framework.

31
Q

What are the Agile behaviours?

What is another name for “behaviours”?

A

Being collaborative, self-organising, customer-focused, empowered, trusting and not blaming.

Principles, values, mindset

32
Q

What are the Agile concepts?

What is another name for “behaviours”?

A

Prioritising what is being delivered, working iteratively and incredementally, not delivering everything at the expense of time, time-focused, “inspect and adapt”, Kaizen, liming work in progress

Fundamentals

33
Q

What are the Agile techniques?

What is another name for “behaviours”?

A

Burn charts, user stories, retrospectives, timeboxing, measuring flow

34
Q

What is Agile agnostic and how does this support project delivery?

A

Agile agnostic refers to the concept that Agile or PRINCE2 Agile does not favour particular concepts, behaviours, or techniques. Those selected should b=e unique to each project and support the particular requirements and demands of the project.

35
Q

How do PRINCE2 and Agile complement each other?

A

PRINCE2 provides a framework to run the project and details good project documentation, but does not speciify how to deliver the project on a day-to-day basis.

Agile does not have the wider perspective of the entire project, but does guide best practise and day-to-day delivery of the project.

It is a blending rather than the two systems working in parallel.

Every working on a PRINCE2 Agile project must embrace Agile behaviours, concepts and techniques, and also stick to PRINCE2’s principles and processes

36
Q

What are the five considerations one needs to make in a PRINCE2 Agile project?

A
  1. PRINCE2 7 is built to be compatible with Agile. Tailoring a PRINCE2 Agile project should not involve removing or adding core elements from the framework and methodology, but emphasising and de-emphasising certain aspects.
  2. PRINCE2 has a reputation for being bureaucratic and documentation-heavy. This reputation should not influence of PRINCE2 Agile as being able to handle levels of informality and fast-moving projects.
  3. PRINCE2 and Agile methodologies / approaches were developed in an IT setting, but it can be used in any industry
  4. Scrum and Kanban are the most widely-used Agile methodologies. They do not specify the role of a PM and are insufficient to manage the whole project (just day-to-day delivery). They need to be employed within a PRINCE2 (or similar) framework.
  5. The degree of Agile integration into a team or project is a variable scale and not an all-or-nothing status
37
Q
A