LEARN. PRACTICE. GROW.Concept and mechanism
PRINCE2 Agile retains project processes while adapting collaboration and delivery. Starting up helps determine whether preparing the project is worthwhile; initiating creates a management basis; directing handles direction and authorization. During execution, controlling a stage oversees the stage and managing product delivery coordinates the commitment to deliver products. Do not confuse these purposes with meeting names. A workshop needs an objective, suitable participants, information, and a usable result. Format may vary with context and need not replicate a Scrum ceremony where it is not useful.
Guided application
During startup, bring business and operations together to clarify the problem and users. During initiation, connect a release view with assumptions, capacity, and controls. Detail increases as work approaches. When preparing an iteration, discuss the useful objective and capacity to produce a quality outcome. During the stage, expose dependencies and impediments early. A delayed external approval may require reordering, response, or escalation according to impact and limits. The board needs information to direct investment; the team needs autonomy to execute within authority, with communication supporting coordination.
A goals workshop avoids planning weeks of work for incompatible interpretations of the same request.
Common pitfalls
Workshop without an outcome; planning removed because of uncertainty; board involved in every task; impediment saved until the end.
Related topics: Reviews, stage boundaries, and closure · Product, operations, and AI support
Connect each discussion with a concrete decision, commitment, or learning outcome.
Reference: PRINCE2 Agile Foundation syllabus · Version 2; inspected syllabus 2.0 (May 2025); revision 2.1 comparison pending