PRINCE2 Agile Foundation: Agile Mindset and Project Management

Topic snapshot

Sample questions

These are original PM Mastery practice questions aligned to this topic area. They are not official PeopleCert questions, copied live-exam content, or exam dumps. Use them to preview question style and explanation depth before continuing with topic drills, mixed sets, and timed mocks in PM Mastery.

Question 1

Topic: Agile Mindset and Change Management

A PRINCE2 Agile project has two agile teams. Senior stakeholders want a simple, regular view of overall status that supports alignment and transparency without day-to-day delivery detail. Which approach is MOST appropriate?

• A. Use a team dashboard with detailed iteration tasks and metrics.
• B. Use a project dashboard with project-level progress and exceptions.
• C. Use a retrospective summary as the main stakeholder status view.
• D. Use the product backlog as the primary governance report.

Best answer: B

What this tests: Agile Mindset and Change Management

Explanation: In PRINCE2 Agile, communication should fit the audience. A project dashboard gives senior stakeholders a clear project-level view for alignment and transparency, whereas a team dashboard is mainly for detailed team coordination.

In a PRINCE2 Agile context, effective communication supports alignment, collaboration, stakeholder engagement, and transparency by giving each audience the information it needs. Senior stakeholders usually need a concise view of overall progress, key exceptions, and whether the project remains on track. That is the purpose of a project dashboard. A team dashboard is more detailed and is mainly used by the delivery team to support day-to-day collaboration and visibility of team work. Using the right dashboard improves transparency without overwhelming stakeholders with unnecessary detail. The closest alternative is the team dashboard, but that communicates at the delivery-team level rather than the project-governance level.

A project dashboard is designed to communicate overall project status to stakeholders at the right level for alignment and transparency.

Question 2

Topic: Agile Mindset and Change Management

Which popular agile approach is best described as focusing on maximizing value, reducing waste, and improving flow of work?

• A. Scrum
• B. Kanban
• C. Lean
• D. Lean Startup

Best answer: C

What this tests: Agile Mindset and Change Management

Explanation: Lean is the best match because its core emphasis is value, waste reduction, and flow. In PRINCE2 Agile Foundation, this matters because Lean helps teams focus effort on what delivers benefit and avoid unnecessary activity.

Lean is a common agile approach that aims to maximize customer value, remove waste, and improve the flow of work. At PRINCE2 Agile Foundation depth, the important point is to recognize Lean as a simple but powerful way of thinking: do more of what creates value and less of what does not. This supports agile delivery because smoother flow and less waste can improve speed, focus, and efficiency.

Kanban is closely related because it strongly emphasizes visualizing work and managing flow, but the broader combination of value, waste reduction, and flow is the classic Lean description. Scrum is a team framework using roles, events, and artifacts, while Lean Startup focuses on learning and validation around products and ideas.

Lean is the agile approach associated with delivering value while reducing waste and improving flow.

Question 3

Topic: Agile Mindset and Change Management

In PRINCE2 Agile, what is the main purpose of the Lean Startup approach?

• A. To test assumptions quickly and gain validated learning from feedback
• B. To define completion criteria for finished work
• C. To organize delivery into short iterations with regular reviews
• D. To visualize workflow and limit work in progress

Best answer: A

What this tests: Agile Mindset and Change Management

Explanation: Lean Startup is used to learn quickly through experiments and feedback. In PRINCE2 Agile, this matters because it helps avoid investing heavily in ideas before there is evidence that they will deliver value.

The core idea of Lean Startup is validated learning. Teams test assumptions early, use rapid experimentation, and gather feedback so they can decide whether to continue, adjust, or stop an idea. At Foundation level in PRINCE2 Agile, the important point is that Lean Startup helps reduce waste and uncertainty by learning from evidence rather than relying only on upfront prediction.

This matters because projects often face uncertainty about what customers really need. Lean Startup supports an agile mindset by encouraging fast feedback and learning before larger commitments are made. By contrast, approaches such as Kanban or Scrum have different primary purposes.

Lean Startup focuses on rapid experimentation so the team can learn what users actually value before committing significant effort.

Question 4

Topic: Agile Mindset and Change Management

An organization is introducing PRINCE2 Agile. One team says, “We are agile now because we have started stand-ups, boards, and short iterations.” Another team says, “Those help, but real agile capability and mindset develop over time.”

Which statement BEST compares these two views?

• A. The first team is correct because agile maturity is achieved once agile practices start.
• B. The second team is correct because PRINCE2 Agile combines project management with agile ways of working, and maturity develops over time.
• C. The second team is incorrect because agile maturity should be fully in place before any transformation begins.
• D. The first team is correct because PRINCE2 Agile is mainly for speeding up business-as-usual work.

Best answer: B

What this tests: Agile Mindset and Change Management

Explanation: The stronger view is that agile maturity is a transformation success factor that develops over time. PRINCE2 Agile is not just doing agile practices; it matters because it combines PRINCE2 project management with agile ways of working to help teams become more agile progressively.

At Foundation level, PRINCE2 Agile can be understood simply as PRINCE2 project management integrated with agile ways of working. This matters because projects still need direction, control, and governance while delivery teams use agile behaviors and techniques.

Agile maturity is not reached the moment a team starts stand-ups, boards, or iterations. Those are signs of doing agile. Capability develops over time as teams build experience, improve collaboration, learn from feedback, and strengthen an agile mindset, which is closer to being agile.

So, in an agile transformation, early use of practices is helpful, but lasting success depends on growing maturity over time rather than assuming it appears immediately.

PRINCE2 Agile is about using agile ways of working within PRINCE2 project management, and agile maturity grows progressively rather than appearing immediately.

Question 5

Topic: Agile Mindset and Change Management

PRINCE2 Agile differs from generic agile delivery because it combines agile delivery approaches with PRINCE2 ____.

• A. product backlog
• B. daily stand-ups
• C. project governance
• D. story points

Best answer: C

What this tests: Agile Mindset and Change Management

Explanation: PRINCE2 Agile is the combination of PRINCE2 project governance with agile delivery approaches. Generic agile delivery may use agile practices on its own, but PRINCE2 Agile adds governance, roles, control, and continued business justification at project level.

The missing term is project governance. PRINCE2 Agile is not just agile delivery with PRINCE2 terminology added. Its defining idea is that agile ways of working are used within a PRINCE2 project management and governance framework. That means the project still has PRINCE2 direction and control, while delivery teams can use agile techniques such as backlogs, timeboxes, and iterative development.

Generic agile delivery usually focuses on how teams deliver work. PRINCE2 Agile goes further by linking that delivery to project-level governance, decision-making, and oversight. That governance layer is what makes PRINCE2 Agile distinct.

PRINCE2 Agile adds PRINCE2 governance and control to agile delivery methods, which is the key distinction from generic agile delivery.

Question 6

Topic: Agile Mindset and Change Management

Which TWO statements correctly describe the difference between being agile and doing agile? Select TWO.

• A. Doing agile removes the need for an agile mindset.
• B. Being agile means using a defined framework exactly as written.
• C. Being agile is about mindset and behaviors, such as welcoming change to protect value.
• D. Doing agile is about using practices and techniques, such as backlogs or retrospectives, to organize delivery work.

Correct answers: C, D

What this tests: Agile Mindset and Change Management

Explanation: Being agile and doing agile are related but different. Being agile is the mindset and way of thinking; doing agile is the use of practical techniques and ways of working. PRINCE2 Agile emphasizes that practices work best when supported by the right mindset.

The core difference is that being agile describes the mindset, values, and behaviors that support flexibility, collaboration, and focus on value, while doing agile describes the visible use of agile practices, techniques, and artifacts. A team may be doing agile by using a backlog, stand-ups, or retrospectives, but it is only being agile if it also shows the attitudes that support learning, adaptation, and responsiveness to change.

In simple Foundation-level terms:

• Being agile = mindset and behavior
• Doing agile = methods and techniques
• Effective agile working usually needs both

The closest trap is the idea that following a framework exactly is the same as being agile; that describes doing agile at best, not the mindset itself.

This is correct because being agile focuses on attitudes and behaviors that support adaptability and customer value.

This is correct because doing agile refers to applying specific agile methods, practices, and artifacts in delivery.

Question 7

Topic: Agile Mindset and Change Management

Which TWO statements correctly reflect the Agile Manifesto values? Select TWO.

• A. Processes and tools are preferred to individuals and interactions.
• B. Comprehensive documentation is preferred to working software.
• C. Customer collaboration is preferred to contract negotiation.
• D. Responding to change is preferred to following a plan.

Correct answers: C, D

What this tests: Agile Mindset and Change Management

Explanation: The Agile Manifesto expresses preferences, not the rejection of items on the right. Two of its values clearly favor customer collaboration over contract negotiation and responding to change over following a plan.

The four Agile Manifesto values state that, while the items on the right still have value, agile ways of working place greater emphasis on the items on the left. In this question, the correct statements are the ones that reflect those left-over-right preferences. Agile favors customer collaboration over contract negotiation and responding to change over following a plan. By contrast, it does not place comprehensive documentation above working software, and it does not place processes and tools above individuals and interactions. The key point is that agile prefers collaboration, adaptability, and human interaction while still recognizing the supporting value of plans, contracts, documentation, and tools.

This matches the value that emphasizes working with the customer over relying mainly on formal contract discussions.

This matches the value that favors adaptability when circumstances change rather than rigid adherence to a plan.

Question 8

Topic: Agile Mindset and Change Management

Which TWO statements correctly describe the effect of addressing the people element in PRINCE2 Agile? Select TWO.

• A. Effective communication and change leadership help stakeholders adopt agile ways of working.
• B. Clear relationships between governance and delivery roles help faster backlog priority decisions.
• C. Frequent team communication makes stakeholder engagement less necessary.
• D. Self-organizing teams remove the need for defined PRINCE2 Agile roles.

Correct answers: A, B

What this tests: Agile Mindset and Change Management

Explanation: The people element in PRINCE2 Agile emphasizes clear roles, good relationships, active communication, and change leadership. In practice, this improves decision flow and helps stakeholders understand and accept agile working methods.

PRINCE2 Project Management addresses the people element by defining roles and responsibilities, encouraging effective working relationships, supporting communication, and leading change. In a PRINCE2 Agile context, that has practical effects on how decisions are made and how change is accepted. Clear links between governance roles and delivery roles help decisions such as backlog priority or scope trade-offs happen quickly and with the right authority. Strong communication and change leadership also support OCM by helping stakeholders understand why agile ways of working are being introduced and what behavior changes are needed.

Self-organizing teams still operate within defined PRINCE2 Agile roles, and frequent team communication does not replace broader stakeholder engagement.

Defined role relationships improve communication and speed decision-making about backlog priorities.

Good communication and change leadership support organizational acceptance of agile change.

Question 9

Topic: Agile Mindset and Change Management

A PRINCE2 Agile project team uses a product backlog, daily stand-ups, and two-week iterations. Which TWO observations show the team is only doing agile practices without being agile?

Select TWO.

• A. User change requests are discouraged to protect the original detailed plan.
• B. Work must be approved by the manager before team members act.
• C. The team updates the backlog after customer feedback in reviews.
• D. Retrospectives are used to improve how the team works.

Correct answers: A, B

What this tests: Agile Mindset and Change Management

Explanation: Doing agile means using agile practices, but being agile also requires the mindset behind them. The clearest clues that the team is not being agile are resistance to change and command-and-control behaviour instead of adaptation and empowerment.

In PRINCE2 Agile, being agile is more than using stand-ups, backlogs, or iterations. It also means showing an agile mindset through collaboration, responsiveness to change, trust, and continuous learning. In this scenario, discouraging change requests to protect an original detailed plan shows a predictive mindset rather than an adaptive one. Requiring manager approval before team members act shows low empowerment and weak self-organization. By contrast, updating the backlog after feedback and using retrospectives both support agile ways of working because they encourage adaptation and improvement. The key distinction is that agile practices alone are not enough if behaviour still reflects control, rigidity, and resistance to change.

Resisting change to preserve a fixed plan shows process compliance without the agile mindset of adapting to feedback.

Heavy manager control shows low empowerment, which is a sign of doing agile activities without being agile.

Question 10

Topic: Agile Mindset and Change Management

If people have learned a new visual board tool but still resist transparency and collaboration, the unresolved issue is mainly one of ____.

• A. tool configuration
• B. process training
• C. culture
• D. progress reporting

Best answer: C

What this tests: Agile Mindset and Change Management

Explanation: The team already knows how to use the tool, so the remaining problem is not simple adoption of a process or system. In PRINCE2 Agile, resistance to agile behaviours such as openness and collaboration is mainly a culture-related OCM concern.

In PRINCE2 Agile, culture refers to the shared behaviours, attitudes, and norms that affect how people work together. If a team can use a tool but still avoids transparency and collaboration, the gap is not mainly about learning a process step or configuring software. It is about changing behaviours and mindsets so people can work in a more agile way, which sits within organizational change management (OCM). Process training and tools can support change, but they do not by themselves address deeper resistance rooted in habits or local culture. The key distinction is that tools help people do agile activities, while culture and OCM help people accept and sustain agile ways of working.

Resistance to transparency and collaboration after tool training points to shared behaviours and norms, which is a culture-related OCM issue.

Continue in the web app

Use PM Mastery for interactive P2 Agile Fdn practice with mixed sets, timed mocks, topic drills, explanations, and progress tracking.

Related focused pages

• Free P2 Agile Fdn Full-Length Practice Exam
• P2 Agile Fdn: PRINCE2 Agile Principles and Practices
• P2 Agile Fdn: PRINCE2 Agile Processes and Workshops
• P2 Agile Fdn: PRINCE2 Agile Wider Context

Practice next step

Use the PM Mastery web app above when you want interactive practice beyond this static page.