In PRINCE2 Agile, the Starting Up a Project (SU) and Initiating a Project (IP) processes retain their core purpose but are adapted to work harmoniously with agile ways of working. Starting Up a Project focuses on determining whether the project is viable and worthwhile before committing significant resources. In an agile context, this process should be kept lightweight and rapid, avoiding excessive documentation. The Project Brief is created collaboratively, often through workshops, and captures high-level requirements as epics or user stories rather than detailed specifications. Emphasis is placed on understanding the product vision, customer needs, and the overall direction, embracing the agile principle of just enough planning upfront. Initiating a Project establishes solid foundations by creating the Project Initiation Documentation (PID). In agile, this remains important because it defines governance, tolerances, and the strategies for delivery, but it is produced with agile behaviours in mind. Requirements are prioritised using techniques like MoSCoW (Must, Should, Could, Won't), enabling flexibility in scope while protecting time and cost. The concept of flexing what is delivered is embedded here, ensuring the project can adapt while still meeting fixed constraints. Agile workshops play a vital role in both processes. Collaborative sessions such as visioning workshops, requirements workshops, and release planning help engage stakeholders, build shared understanding, and produce artefacts quickly. Techniques like the product breakdown structure, story mapping, and prioritisation exercises are used to define and organise work. The Cynefin framework and Agilometer may be applied to assess complexity and suitability of agile approaches. Overall, SU and IP in PRINCE2 Agile ensure the necessary control and direction from PRINCE2 while incorporating agile values of collaboration, iterative delivery, early stakeholder engagement, and responsiveness to change, striking a balance between upfront planning and the flexibility to adapt as the project progresses through its delivery stages.

Directing a Project with Agile Delivery is one of the seven PRINCE2 processes, owned by the Project Board, and it takes on specific characteristics when combined with agile ways of working. In PRINCE2 Agile, the Project Board provides governance and decision-making at key points while empowering teams to self-organise and deliver value incrementally. The board 'directs' rather than manages day-to-day work, applying the principle of 'manage by exception' more liberally to give delivery teams greater autonomy within agreed tolerances. In an agile context, tolerances are set primarily around scope and quality (using techniques like MoSCoW prioritisation) rather than time and cost, which are typically fixed. This allows teams to flex what is delivered while protecting deadlines and budgets. The Project Board authorises initiation, authorises the project, authorises stage or exception plans, gives ad hoc direction, and authorises project closure. With agile delivery, the board benefits from richer, more frequent information through techniques like information radiators, burn charts, and regular reviews, enabling faster, more informed decisions. The board must embrace agile behaviours such as trust, transparency, and collaboration, avoiding excessive interference in self-organising teams. During Agile Workshops, the board's role is discussed in terms of supporting frameworks like Scrum or Kanban, understanding how sprints or releases map to management stages, and how the Senior User and Senior Supplier engage with product owners and delivery teams. The board also ensures that the focus remains on delivering business value and that the project stays viable through continued business justification. Ultimately, Directing a Project with agile emphasises servant leadership, empowerment, and lean governance, ensuring that decisions add value without creating unnecessary bureaucracy. The board balances control with flexibility, allowing teams to respond to change while maintaining strategic oversight and alignment with the project's overall objectives and expected benefits throughout its lifecycle successfully.

In PRINCE2 Agile, the Controlling a Stage process is where the Project Manager monitors and controls day-to-day work, integrating agile concepts like releases and timeboxes to deliver value incrementally. A management stage in PRINCE2 may contain one or more releases, and each release is broken down into timeboxes (such as sprints or iterations), providing a structured yet flexible approach to delivery. Releases represent a deployable increment of the product that delivers tangible business value to the customer, aligning with agile's focus on frequent, valuable delivery. During Controlling a Stage, the Project Manager authorizes Work Packages, which typically correspond to releases or collections of timeboxes assigned to the delivery team. The team then self-organizes to plan and execute work within fixed-length timeboxes, protecting the delivery cadence. A key principle is that time and cost are fixed, while scope (features) is flexed using prioritization techniques like MoSCoW (Must have, Should have, Could have, Won't have). This ensures the timebox is never extended; instead, lower-priority requirements may be dropped to meet deadlines. Monitoring during this process uses agile tools such as burn charts, information radiators, and daily stand-ups, providing transparency on progress rather than relying solely on formal reports. The Project Manager works collaboratively, empowering the team while maintaining governance through tolerances and checkpoints. Agile workshops, including release planning and sprint/timebox planning, feed directly into this process, ensuring alignment between the delivery team and management levels. Frequent releases and feedback loops enable early inspection and adaptation, reducing risk. If issues arise, escalation follows PRINCE2's exception mechanisms. Ultimately, Controlling a Stage with releases and timeboxes blends PRINCE2's controlled governance with agile's iterative, value-driven delivery, ensuring products are delivered incrementally, quality is embedded through fixed timeboxes, and the customer receives usable increments frequently throughout each management stage.

Managing Product Delivery (MP) is the PRINCE2 process where the actual work of creating products happens, and it is the natural home for agile ways of working like Scrum and Kanban. In this process, the Team Manager and delivery team accept, execute, and deliver Work Packages authorised by the Project Manager, and this is where agile delivery frameworks integrate seamlessly with PRINCE2's controlled environment. Scrum fits into MP by structuring work into fixed-length timeboxes called sprints, typically two to four weeks. The team pulls Product Backlog items into a Sprint Backlog during sprint planning, conducts daily stand-ups to synchronise progress, and delivers a potentially shippable increment at each sprint's end. Scrum events such as sprint reviews and retrospectives support inspection and adaptation, while roles like Product Owner and Scrum Master complement PRINCE2 roles. The Work Package in PRINCE2 maps well to a set of sprints or a release, providing boundaries and tolerances within which the self-organising team operates. Kanban, by contrast, focuses on visualising workflow using a Kanban board, limiting work in progress (WIP), and managing continuous flow rather than fixed timeboxes. It emphasises pulling work as capacity allows, reducing bottlenecks, and improving cycle time. Kanban suits environments where priorities change frequently or where a steady, continuous delivery stream is preferred over batch releases. Within MP, both approaches respect PRINCE2 controls: reporting through Checkpoint Reports, managing quality via the Quality Register, and escalating when tolerances are threatened. PRINCE2 Agile encourages tailoring, so teams may blend Scrum and Kanban (Scrumban) or use whichever best fits the context. Agile workshops, such as planning sessions, reviews, and retrospectives, provide collaborative forums for these activities. Ultimately, MP with Scrum or Kanban balances agile flexibility, empowerment, and frequent delivery with PRINCE2's governance, ensuring value is delivered incrementally while maintaining overall project direction and control.

In PRINCE2 Agile, the Managing a Stage Boundary process ensures the project remains viable and aligned with business objectives while accommodating agile delivery. Its core purpose is to provide the Project Board with sufficient information to review the current stage's success and approve the next stage, supporting the principle of managing by stages. In an agile context, this process is enriched by empirical feedback gathered from working software or products delivered during the stage, allowing decisions based on demonstrated progress rather than assumptions. When preparing for a stage boundary, teams use agile techniques such as reviewing the product backlog, assessing velocity, and evaluating what has been delivered versus what remains. This informs an updated Stage Plan and refined estimates for future work. Rather than viewing scope as fixed, agile delivery treats scope as flexible while protecting time and cost, so the boundary review confirms whether enough value has been delivered and whether priorities need adjusting. Retrospectives conducted during the stage feed lessons into the process, promoting continuous improvement. The frequency of feedback and releases means the Project Board gains confidence through tangible outputs. Key products created or updated include the End Stage Report, which summarises performance using agile metrics like burn charts and features completed; the next Stage Plan incorporating prioritised backlog items; and updated risk and quality registers. Exception situations may also trigger this process, where a revised plan is produced to recover or re-baseline. Agile workshops, such as release planning and sprint reviews, support the collaborative creation of these boundary artefacts, ensuring stakeholder engagement and transparency. Ultimately, Managing a Stage Boundary in agile delivery balances governance with flexibility, enabling the organisation to make informed go or no-go decisions. It combines PRINCE2's structured control with agile's adaptive, value-driven approach, ensuring the project continues to deliver benefits incrementally while remaining responsive to changing requirements and emerging feedback throughout.

Closing a Project in an Agile context within PRINCE2 Agile retains the core purpose of the standard PRINCE2 Closing a Project process while adapting to iterative, incremental delivery. The main objective is to confirm the project's products have been accepted, verify that acceptance criteria are met, and ensure benefits realisation is on track. In an agile environment, much of the acceptance work happens continuously throughout the project rather than solely at the end. Frequent delivery of releases and features means products are reviewed and accepted incrementally during each sprint or timebox, so formal closure often confirms what has already been validated. Key activities include preparing planned closure, handing over products to operations and maintenance, evaluating the project, and recommending project closure to the Project Board. The End Project Report and Lessons Report capture valuable insights, and in agile teams these are enriched by retrospectives held throughout delivery, promoting continuous learning. Because agile embraces changing requirements, some functionality may have been descoped or reprioritised; closure documents what was actually delivered versus the baseline, emphasising delivered value over strict scope completion. The concept of 'fix time and resources, flex features' means the project may close on a fixed date with the highest-priority requirements met. Follow-on action recommendations may include a backlog of remaining features for future work or ongoing product evolution. During Agile Workshops, teams often discuss how closure integrates with frameworks like Scrum, ensuring the release is production-ready and the definition of done is satisfied. Handover should be smooth, supported by proper documentation and stakeholder engagement. Ultimately, closing a project in an agile context ensures accountability, formal sign-off, and a clear transition, while celebrating the collaborative, adaptive nature of delivery and capturing lessons that improve future agile projects and organisational maturity, ensuring benefits continue to be measured post-project.

In PRINCE2 Agile, Visioning and Kick-off Workshops are collaborative events used to establish shared understanding and alignment at the start of a project or delivery phase, bridging PRINCE2's structured governance with agile's collaborative ethos. A Visioning Workshop typically occurs early, often during the Starting Up a Project (SU) or Initiating a Project (IP) processes. Its purpose is to create a clear, compelling vision that articulates the project's overall goal, expected benefits, and desired outcomes. It brings together key stakeholders, the project board, business representatives, and delivery teams to align on the 'big picture', ensuring everyone understands why the project matters and what success looks like. Techniques such as product visioning, prototyping, and workshops help translate the Business Case into a tangible direction, supporting the PRINCE2 principle of focusing on products and continued business justification. A Kick-off Workshop, by contrast, focuses on preparing the team to begin actual delivery, commonly aligned with the Managing a Stage Boundary or Controlling a Stage processes, and at the start of releases or sprints. It ensures the delivery team understands the scope, priorities, ways of working, roles, timeboxes, and quality expectations. Kick-off workshops often cover the Definition of Done, the prioritised requirements (using MoSCoW), team norms, and agile working agreements. They help establish trust, transparency, and self-organisation within the team, reinforcing agile behaviours and the PRINCE2 principle of managing by stages and defined roles and responsibilities. Both workshops embody agile's emphasis on communication and collaboration over documentation, while respecting PRINCE2's need for defined direction and control. Visioning sets the strategic 'why' and 'what', whereas Kick-off addresses the practical 'how' and 'who'. Together, they reduce ambiguity, foster engagement, and create a strong foundation for iterative, incremental delivery. Effective facilitation, clear objectives, and inclusive participation are essential to maximise their value in a PRINCE2 Agile environment.

In PRINCE2 Agile, Sprint Planning and Timebox Planning are essential collaborative events that bridge agile delivery with PRINCE2's structured governance. Timebox Planning is the broader PRINCE2 Agile concept, where a fixed period of time (a timebox) is allocated to deliver a set of features or products. A Sprint is a specific type of timebox used in Scrum, typically lasting 1-4 weeks. Sprint Planning is the ceremony held at the start of each Sprint where the delivery team decides what work to undertake and how to achieve it. During Sprint Planning, the team reviews the prioritised backlog, selects items they can realistically complete within the timebox, and defines a Sprint Goal. This aligns with PRINCE2's 'Managing Product Delivery' process, ensuring work packages are agreed and understood. The team collaboratively estimates effort, breaks user stories into tasks, and commits to a Sprint Backlog. Timebox Planning in PRINCE2 Agile emphasises fixing time and cost while flexing scope, using prioritisation techniques like MoSCoW (Must have, Should have, Could have, Won't have) to ensure the most valuable features are delivered first. This protects deadlines and budgets, key concerns for PRINCE2 governance. In Agile Workshops, these planning sessions promote collaboration, transparency, and shared understanding among team members, the Project Manager, and stakeholders. They support PRINCE2 principles such as 'manage by stages' and 'focus on products'. The Project Manager sets tolerances and constraints, while the delivery team self-organises within those boundaries. Both approaches reinforce empirical control through frequent inspection and adaptation. By combining Sprint Planning's tactical detail with Timebox Planning's disciplined time-boxing and prioritisation, PRINCE2 Agile achieves predictable delivery within controlled parameters. This ensures agility remains aligned with organisational governance, enabling teams to deliver working products incrementally while maintaining the accountability and control that PRINCE2 provides throughout the project lifecycle.

Daily Stand-ups are a core agile ceremony within the PRINCE2 Agile framework, designed to support effective communication and self-organisation within delivery teams. Also known as 'daily scrums', these are short, time-boxed meetings—typically lasting no more than 15 minutes—held at the same time and place each day. Their primary purpose is to synchronise the team's activities, share progress, and identify any impediments or blockers that may hinder delivery. During a Daily Stand-up, each team member typically addresses three key questions: What did I accomplish yesterday? What will I work on today? Are there any obstacles or impediments in my way? This structure keeps the meeting focused and ensures that the entire team remains aligned on progress toward sprint or timebox goals. In PRINCE2 Agile, Daily Stand-ups fit naturally into the 'Managing Product Delivery' process, where the delivery team executes work packages agreed with the Project Manager. They reinforce the agile behaviours of transparency, collaboration, and continuous communication that PRINCE2 Agile promotes. The stand-up empowers teams to self-organise and adjust their plans dynamically, supporting frequent delivery and rapid response to change. Importantly, stand-ups are for the team, facilitating peer accountability rather than serving as status reports to management. Detailed problem-solving discussions are deferred to separate follow-up conversations to keep the meeting brief and efficient. Visual tools such as Kanban boards, burn-down charts, or task boards often accompany stand-ups to enhance transparency and make progress visible. Within Agile Workshops and ceremonies, Daily Stand-ups complement other events like sprint planning, reviews, and retrospectives. By fostering regular, disciplined communication, they help maintain momentum, reduce risk, and ensure the team stays focused on delivering value. In the PRINCE2 Agile context, they bridge governance and agility, ensuring both structured control and flexible, collaborative working practices coexist effectively throughout the project lifecycle.

Sprint Reviews and Demos are key agile events that align well with PRINCE2 Agile's blend of structured governance and agile delivery. In PRINCE2 Agile, these events primarily occur within the 'Managing Product Delivery' process, where the delivery team develops and demonstrates working products. A Sprint Review is a collaborative event held at the end of each sprint (timebox) to inspect the increment of work completed and gather feedback from stakeholders, including the customer or Project Board representatives. It supports the PRINCE2 principle of 'Learn from experience' and 'Continued business justification' by ensuring the product delivered still meets business needs. The Demo is a component of the Sprint Review where the team showcases the actual working product features developed during the sprint. This encourages transparency, one of the five agile behaviours emphasised in PRINCE2 Agile, and provides tangible evidence of progress rather than relying solely on documentation or status reports. Demos allow stakeholders to see real functionality, ask questions, and provide immediate feedback, which informs the prioritisation of the product backlog for future sprints. In relation to PRINCE2 processes, feedback from Sprint Reviews feeds into 'Controlling a Stage' and 'Managing a Stage Boundary', helping the Project Manager assess whether the project remains viable and on track. The frequent inspection supports flexibility around what is delivered while protecting fixed elements like time and cost, reflecting PRINCE2 Agile's focus on fixing time and quality but flexing scope. During Agile Workshops, Sprint Reviews and Demos are often practised to reinforce collaboration, communication, and the importance of delivering value early and often. Ultimately, they bridge agile's empirical, feedback-driven approach with PRINCE2's emphasis on control, governance, and business justification, ensuring products are fit for purpose, aligned with acceptance criteria, and delivered incrementally to maximise value while managing risk effectively throughout the project lifecycle.

In PRINCE2 Agile, retrospectives are a fundamental agile practice used to inspect and adapt the way of working, promoting continuous improvement throughout the project lifecycle. A retrospective is a structured meeting, typically held at the end of a timebox, sprint, or iteration, where the team reflects on their recent work to identify what went well, what did not go well, and what could be improved. This aligns strongly with the PRINCE2 principle of 'learn from experience', embedding a culture of ongoing learning into the project. Within the PRINCE2 Agile framework, retrospectives support the 'Managing a Stage Boundary' and 'Controlling a Stage' processes by feeding lessons directly into subsequent stages and delivery cycles, rather than waiting until the end of the project. This ensures that improvements are actioned quickly and iteratively. During agile workshops, retrospectives are often facilitated using techniques such as 'Start, Stop, Continue', timelines, or the 'Sailboat' exercise to encourage open, honest, and blame-free discussion. The focus is on the process and collaboration, not on individual performance. A key output of a retrospective is a small set of concrete, actionable improvement items that the team commits to implementing in the next timebox. Retrospectives reinforce agile values such as transparency, collaboration, and self-organisation, empowering teams to own their processes. They also complement the PRINCE2 lessons log, ensuring that valuable insights are captured formally and shared across the wider project or organisation. By holding retrospectives regularly, teams avoid repeating mistakes and steadily enhance productivity, quality, and morale. In summary, retrospectives bridge agile ceremonies with PRINCE2 governance, providing a lightweight yet powerful mechanism for teams to continuously reflect, adapt, and improve, which ultimately increases the likelihood of delivering value and meeting project objectives within the controlled PRINCE2 Agile environment.

Workshop facilitation techniques within PRINCE2 Agile are essential skills for guiding collaborative sessions that support project delivery. Facilitation ensures that agile workshops—such as sprint planning, retrospectives, reviews, and requirement-gathering sessions—run effectively and produce valuable outcomes. A skilled facilitator remains neutral, encourages participation, and helps the team reach consensus without imposing personal views. Key techniques include timeboxing, where sessions are given fixed durations to maintain focus and momentum, aligning with PRINCE2 Agile's emphasis on fixing time and cost while flexing scope. Another core technique is the use of visualisation tools, such as whiteboards, sticky notes, Kanban boards, and information radiators, which make progress and problems transparent to all stakeholders. Facilitators often employ techniques like brainstorming to generate ideas, dot voting or MoSCoW prioritisation to make decisions collectively, and round-robin methods to ensure every participant contributes. Active listening, open questioning, and paraphrasing help clarify understanding and surface hidden concerns. Managing group dynamics is crucial; facilitators must handle dominant personalities, encourage quieter members, and defuse conflict constructively. Techniques such as setting ground rules, parking irrelevant topics in a 'parking lot', and using icebreakers create a safe, productive environment. PRINCE2 Agile stresses collaboration and the servant-leadership approach, so facilitators empower self-organising teams rather than directing them. Preparation is vital: defining clear objectives, inviting the right participants, and arranging an appropriate space or virtual platform. During the workshop, facilitators keep discussions on track, summarise agreements, and capture actions with clear ownership. After the session, they document outcomes and follow up on commitments. Effective facilitation supports PRINCE2 Agile behaviours of transparency, collaboration, self-organisation, and exploration. Ultimately, these techniques enhance communication, accelerate decision-making, build shared understanding, and strengthen team engagement, ensuring workshops deliver tangible value that supports both the agile ways of working and the overarching PRINCE2 governance framework throughout the project lifecycle.