PRINCE2-Agile-Foundation Exam Questions & Answers

The Project Closure Workshop is the formal forum used to reflect on lessons learned during the project lifecycle. It is held towards the end of the project and provides an opportunity for the project team, stakeholders, and sponsors to review successes, challenges, and areas for improvement.

Capturing lessons learned supports organizational learning, helps avoid repeating mistakes, and improves future projects and agile adoption. This reflective practice aligns with PRINCE2's focus on continuous improvement and governance requirements.

Other workshops such as team planning (A) focus on upcoming work, agile enablement (B) on agile adoption, and project kickoff (C) on project initiation, none of which prioritize lessons learned reflection.

The project closure workshop is a vital practice to ensure knowledge retention and maturity in both traditional and agile project environments.

A well-recognized challenge when merging traditional project management with Agile approaches is the use of different terminology, making option B the correct answer. Agile Foundation materials highlight that traditional project management and Agile have evolved from different perspectives, each with its own language, concepts, and assumptions. When these approaches are combined within the same organization or project, misunderstandings often arise due to terminology differences rather than fundamental conflicts in intent.

Traditional project management commonly uses terms such as scope, milestones, deliverables, baselines, and change control, while Agile uses concepts like backlog, iterations, increments, velocity, and value delivery. Even when the underlying goals are aligned, different terminology can create confusion among stakeholders, project managers, Agile teams, and senior leadership. This confusion may lead to misaligned expectations, incorrect reporting, or resistance to Agile practices, as people may interpret the same words differently or assume conflicting meanings.

Option A, lack of clear processes, is generally not a common issue because both project management and Agile provide structured approaches, albeit in different forms. Option C, lack of guidance at the project level, is also not accurate, as Agile Foundation guidance increasingly addresses how Agile can operate at team, project, and organizational levels. Option D, the use of a flexible framework, is actually a benefit of Agile rather than a challenge.

Agile Foundation documents emphasize that overcoming terminology differences requires education, shared understanding, and alignment rather than choosing one approach over the other. By establishing a common language, clarifying roles and expectations, and focusing on value delivery rather than labels, organizations can successfully integrate Agile ways of working with project management governance. Addressing terminology differences early helps reduce friction, improves collaboration, and enables a more effective hybrid or Agile-informed project environment.