In PRINCE2 Agile Foundation, understanding the distinction between 'being agile' and 'doing agile' is fundamental to the Agile Mindset. 'Doing agile' refers to the mechanical adoption of agile practices, tools, and ceremonies—such as running daily stand-ups, using Kanban boards, conducting sprint reviews, or following Scrum events. Organizations that are merely 'doing agile' follow the rituals without truly internalizing the underlying values, often resulting in superficial transformation and limited benefits. In contrast, 'being agile' represents a deeper cultural and philosophical shift, where individuals and teams embody agile values and principles as defined in the Agile Manifesto. Being agile means embracing collaboration, transparency, trust, empowerment, adaptability, and a genuine focus on delivering customer value. It reflects a mindset that welcomes change, encourages continuous improvement, and prioritizes people and interactions over rigid processes. In the context of Project Management, PRINCE2 Agile emphasizes that lasting success comes from combining structured governance with an authentic agile mindset. Practitioners must go beyond executing techniques and instead cultivate behaviours such as self-organisation, iterative thinking, and responsiveness to feedback. This ensures that agile methods enhance rather than constrain project delivery. Regarding Organizational Change, 'being agile' is critical for sustainable transformation. Simply imposing agile practices without shifting organizational culture, leadership styles, and behaviours often leads to resistance and failure. True agility requires changes in mindset at all levels—leaders must foster psychological safety, empower teams, and support experimentation. PRINCE2 Agile encourages organizations to blend the discipline of PRINCE2 with the flexibility of agile, ensuring both control and adaptability. Ultimately, 'doing agile' is about actions and tools, while 'being agile' is about attitudes, values, and behaviours. Sustainable agility demands both, but the mindset ('being') is what makes the practices ('doing') genuinely effective, enabling organizations to respond confidently to complexity and change.

The Agile Manifesto, created in 2001, forms the philosophical foundation of the Agile mindset and is highly relevant to PRINCE2 Agile Foundation, project management, and organizational change. It consists of four core values and twelve supporting principles. The four values are: (1) Individuals and interactions over processes and tools, emphasizing collaboration and communication among people; (2) Working software over comprehensive documentation, prioritizing delivering functional products over excessive paperwork; (3) Customer collaboration over contract negotiation, focusing on partnership and continuous engagement with the customer; and (4) Responding to change over following a plan, valuing flexibility and adaptability. Crucially, the manifesto states that while there is value in the items on the right, the items on the left are valued more. In organizational change contexts, these values encourage empowering teams, fostering trust, and reducing bureaucracy. The twelve principles expand on these values, guiding practical behavior. They include satisfying the customer through early and continuous delivery of value, welcoming changing requirements even late in development, delivering working products frequently, and having business and technical people work together daily. Other principles emphasize building projects around motivated individuals, using face-to-face communication, measuring progress through working products, maintaining a sustainable pace, focusing on technical excellence, keeping things simple, encouraging self-organizing teams, and regularly reflecting to improve effectiveness. In PRINCE2 Agile, these values and principles complement the structured governance of PRINCE2, blending flexibility with control. The Agile mindset promotes iterative delivery, transparency, collaboration, and continuous improvement. For project management, this means shifting from rigid, plan-driven approaches toward adaptive, customer-focused delivery. For organizational change, adopting the Agile Manifesto encourages cultural transformation, empowering people to embrace uncertainty and respond quickly to evolving business needs. Understanding these values and principles helps practitioners balance discipline and agility, ensuring projects deliver genuine value while remaining responsive, collaborative, and adaptive throughout the entire lifecycle.

The Scrum Framework is a lightweight Agile approach used to deliver value iteratively, and it aligns well with PRINCE2 Agile's focus on flexibility within a controlled project environment. Scrum is structured around three pillars: Roles, Events, and Artifacts.

Roles: Scrum defines three accountabilities. The Product Owner maximizes product value by managing and prioritizing the Product Backlog, representing stakeholder and business interests—supporting organizational change by ensuring outcomes meet needs. The Scrum Master serves as a servant-leader, coaching the team, removing impediments, and promoting the Agile mindset of collaboration and continuous improvement. The Developers (Development Team) are cross-functional professionals who build the increment, self-organizing to deliver work.

Events (Ceremonies): Scrum uses time-boxed events to create regularity and reduce meetings. The Sprint is the container event, typically 1-4 weeks, delivering a usable increment. Sprint Planning defines what will be done and how. The Daily Scrum is a 15-minute synchronization for Developers to inspect progress and adapt. The Sprint Review inspects the increment with stakeholders, gathering feedback that drives change. The Sprint Retrospective focuses on improving processes, people, and relationships, reinforcing the Agile mindset of learning.

Artifacts: These provide transparency and enable inspection. The Product Backlog is an ordered, evolving list of everything needed in the product. The Sprint Backlog is the subset of items selected for the current Sprint plus the plan to deliver them. The Increment is the sum of completed backlog items, meeting the Definition of Done to ensure quality.

In PRINCE2 Agile Foundation terms, Scrum operates mainly within the delivery layer, while PRINCE2 provides governance, direction, and management. Combining them lets organizations balance control with agility, embracing an Agile mindset that values responding to change, delivering value early, and empowering self-organizing teams to support successful organizational change and project management outcomes.

Kanban is a popular agile way of working that focuses on visualising work, managing flow, and delivering value continuously. Within the PRINCE2 Agile Foundation context, Kanban is recognised as one of the common agile approaches teams may adopt alongside frameworks like Scrum. The term Kanban originates from Japanese, meaning 'signboard' or 'visual card', and it emphasises transparency and workflow management rather than fixed timeboxes. Kanban rests on core principles: visualise the workflow (typically using a Kanban board with columns representing stages such as 'To Do', 'In Progress', and 'Done'), limit work in progress (WIP), manage and measure flow, make process policies explicit, and continuously improve through feedback loops. Flow-based working, closely associated with Kanban, focuses on the smooth, steady movement of work items through the system from start to completion. Unlike iteration-based approaches that batch work into fixed sprints, flow-based working delivers items individually as they become ready, reducing bottlenecks and enabling faster response to change. Limiting WIP is central to this: by capping how many items are worked on simultaneously, teams reduce multitasking, improve focus, and expose blockers quickly. Key flow metrics include lead time (total time from request to delivery), cycle time (time actively spent working), and throughput (items completed per period). These metrics support forecasting and continuous improvement. In terms of the Agile Mindset, Kanban and flow embody principles of transparency, collaboration, incremental delivery, and responding to change. For Project Management, they provide predictability and control while remaining adaptive. In Organizational Change, Kanban is valuable because it is evolutionary rather than revolutionary; teams start with existing processes and improve gradually, which reduces resistance and eases adoption. This makes Kanban particularly suitable for organisations transitioning toward agile ways of working, supporting sustainable, incremental transformation while maintaining alignment with PRINCE2's governance and management-by-stages structure.

Lean Thinking and Lean Startup are two influential concepts within the Agile mindset that support PRINCE2 Agile, project management, and organizational change. Lean Thinking originates from the manufacturing world, particularly the Toyota Production System. It focuses on maximizing customer value while minimizing waste. In the context of projects and organizational change, Lean Thinking encourages teams to identify value from the customer's perspective, map the value stream, create flow, establish pull, and pursue perfection through continuous improvement. The core aim is to eliminate seven common types of waste, such as overproduction, waiting, unnecessary movement, defects, over-processing, excess inventory, and underutilized talent. By reducing waste, organizations become more efficient, responsive, and focused on delivering genuine value. Lean Thinking aligns with the Agile mindset by emphasizing customer collaboration, adaptability, and delivering value incrementally. Lean Startup, developed by Eric Ries, applies Lean principles to the creation of new products, services, and business ventures, especially under conditions of uncertainty. It introduces the concept of validated learning, where assumptions are tested through experimentation rather than lengthy upfront planning. A central practice is building a Minimum Viable Product (MVP), which is the simplest version of a product that allows teams to gather real customer feedback quickly. This feedback drives the Build-Measure-Learn cycle, enabling rapid iteration and informed decision-making. Teams can then decide whether to persevere with their current strategy or pivot to a new direction based on evidence. In organizational change and project management, Lean Startup reduces the risk of investing heavily in unproven ideas, promoting a fail-fast, learn-fast culture. Together, Lean Thinking and Lean Startup reinforce PRINCE2 Agile's emphasis on flexibility, value delivery, and continuous improvement. They encourage teams to remain customer-focused, minimize waste, experiment intelligently, and adapt quickly, making them essential tools for delivering successful projects in dynamic and uncertain environments.

In PRINCE2 Agile Foundation, understanding the distinction between Projects and Business as Usual (BAU) is fundamental to applying the right management approach. A project is a temporary organization created for the purpose of delivering one or more business products according to an agreed Business Case. Projects have a defined start and end, are unique in nature, involve a degree of uncertainty and risk, and require dedicated resources and governance. They introduce change by creating new capabilities, products, or services. Once the project's objectives are achieved, the temporary structure is dissolved. Business as Usual, by contrast, represents the ongoing, repetitive operational activities that keep an organization running day-to-day. BAU is continuous, relatively stable, and predictable, focusing on maintaining and optimizing existing services rather than delivering new outcomes. Examples include payroll processing, customer support, and routine maintenance. From an Agile Mindset perspective, this distinction is important because Agile methods like Scrum and Kanban can operate in both contexts, but their application differs. In projects, Agile enables iterative, incremental delivery of change while embracing flexibility and collaboration. In BAU, Agile approaches such as Kanban support continuous flow and steady improvement of ongoing work. In Organizational Change, projects act as the vehicle for delivering transformation, while BAU is where the benefits are ultimately realized and sustained. A key challenge is transitioning outputs from the project environment into operational BAU, ensuring people, processes, and systems are ready to adopt and embed the change. PRINCE2 Agile emphasizes that project teams must consider BAU stability and the impact of change on operations, balancing the pace of delivery with the organization's ability to absorb change. Recognizing whether work is project-based or BAU helps organizations choose appropriate governance, funding models, and delivery frameworks, ensuring that change is both effectively delivered and successfully operationalized for lasting business value.

Blending PRINCE2 and Agile is most appropriate when an organization needs the governance, control, and strategic direction of PRINCE2 combined with the flexibility, collaboration, and responsiveness of Agile delivery. This hybrid approach, known as PRINCE2 Agile, is ideal in environments where projects operate within larger corporate structures requiring formal reporting, defined roles, and clear accountability, yet still benefit from iterative, incremental product development.

You should consider blending them when the project has a clear business case and defined objectives, but the detailed requirements are uncertain or likely to evolve. PRINCE2 provides the 'what' and 'why' through its principles, themes, and processes, offering stable governance at the project level. Agile, using frameworks like Scrum or Kanban, provides the 'how' at the delivery level, enabling teams to adapt quickly and deliver value frequently.

Blending is particularly valuable during organizational change initiatives where stakeholders demand both predictability and adaptability. PRINCE2's stage boundaries and management by exception align well with Agile's fixed timeboxes and empowered teams, allowing senior management to maintain oversight without micromanaging delivery.

However, blending should only occur when the organization possesses a genuine Agile mindset, valuing collaboration, transparency, self-organization, and continuous improvement. Without this cultural foundation, imposing Agile ceremonies onto rigid PRINCE2 controls creates conflict rather than synergy.

Appropriate scenarios include projects with fixed deadlines or budgets but flexible scope, environments requiring regulatory compliance alongside rapid iteration, and organizations transitioning from traditional to Agile ways of working. It is less suitable for purely operational work, extremely small teams, or when either full governance or full agility alone would suffice.

Ultimately, blend PRINCE2 and Agile when you need to balance direction with responsiveness, ensuring strategic control coexists with adaptive delivery, thereby maximizing both business assurance and the frequent delivery of usable, valuable products to stakeholders.

PRINCE2 (PRojects IN Controlled Environments) is a structured project management method that provides a scalable and tailorable framework for managing projects of any size or type. Its fundamentals rest on four integrated elements: principles, themes, processes, and the project environment. The seven principles form the foundation and must all be applied for a project to be considered PRINCE2: continued business justification, learn from experience, defined roles and responsibilities, manage by stages, manage by exception, focus on products, and tailor to suit the project. The seven themes describe aspects of project management that must be continually addressed: Business Case (why), Organization (who), Quality (what), Plans (how, how much, when), Risk (what if), Change (what impact), and Progress (where are we now, where are we going). The seven processes provide a step-by-step journey through the project lifecycle: Starting up a Project, Directing a Project, Initiating a Project, Controlling a Stage, Managing Product Delivery, Managing a Stage Boundary, and Closing a Project. In the context of PRINCE2 Agile, these fundamentals remain intact but are blended with agile ways of working, allowing teams to combine PRINCE2's governance and control with agile's flexibility, collaboration, and responsiveness. This integration supports an agile mindset by emphasizing delivery of value, embracing change, and empowering self-organizing teams while maintaining the necessary structure for organizational accountability. For organizational change, PRINCE2 offers clear direction and control, ensuring changes are justified, planned, and delivered with measurable benefits. It separates management activities (governance) from specialist delivery work, enabling the fixing of parameters like time and cost while flexing scope through agile techniques. Ultimately, PRINCE2 fundamentals provide a common language and consistent approach that improves communication, reduces risk, and increases the likelihood of successful project outcomes across diverse business and change environments.

Organizational Change Management (OCM) refers to the structured approach used to transition individuals, teams, and organizations from a current state to a desired future state. Within the context of PRINCE2 Agile Foundation, OCM is critical because projects deliver products, but it is the effective adoption of those products that generates real business value. A key concept is the distinction between the technical delivery of a solution and the people-side of change. PRINCE2 Agile recognizes that even successful project outputs fail if stakeholders resist or do not adopt them. Therefore, OCM emphasizes communication, engagement, and support throughout the project lifecycle. Central concepts include stakeholder analysis, which identifies who is affected and their level of influence or resistance, and communication management, which ensures transparent, timely, and tailored messaging. The Agile Mindset complements OCM by valuing collaboration, responsiveness to change, and continuous feedback, enabling organizations to adapt more fluidly. Agile's iterative delivery allows change to be introduced incrementally, reducing shock and enabling gradual adoption. Another key concept is the role of leadership and sponsorship. Visible, committed leadership drives cultural change and reinforces new behaviors. Change models, such as ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement) or Kotter's eight-step model, are often integrated to structure the human transition. Managing resistance is also fundamental; understanding why people resist change allows managers to address concerns proactively. Additionally, embedding change ensures that new ways of working become permanent through training, reinforcement, and measurement of adoption. In PRINCE2 Agile, the concept of 'value' is closely tied to benefits realization, which depends on successful organizational change. By blending PRINCE2's governance and control with Agile's flexibility and people-centric focus, OCM ensures that projects not only deliver outputs but achieve lasting outcomes and sustained benefits, aligning changes with strategic organizational goals and enhancing overall project success and stakeholder satisfaction effectively.

Stakeholder engagement in Agile projects, within the PRINCE2 Agile Foundation context, focuses on continuous collaboration, transparency, and communication throughout the project lifecycle. Unlike traditional approaches where stakeholders are consulted at defined stages, Agile emphasizes ongoing involvement to ensure delivered products meet evolving business needs. The Agile mindset promotes trust, empowerment, and responsiveness to change, which requires stakeholders to be active participants rather than passive observers. In PRINCE2 Agile, stakeholder engagement bridges the structured governance of PRINCE2 with the flexibility of Agile delivery. Key stakeholders such as the customer, users, suppliers, and the business are integrated into the project through defined roles and frequent interaction. Techniques like Scrum ceremonies (sprint reviews, daily stand-ups) and Kanban visualization enable regular feedback and shared understanding. This ensures priorities remain aligned with business value and that requirements can adapt as circumstances shift. From a Project Management perspective, effective engagement reduces risk, prevents misunderstandings, and increases the likelihood of delivering acceptable products on time. PRINCE2 principles such as 'continued business justification' and 'focus on products' rely on stakeholders providing input on scope, quality, and priorities, often expressed through prioritization tools like MoSCoW (Must, Should, Could, Won't). In Organizational Change, stakeholder engagement is critical because Agile projects frequently transform working practices, culture, and systems. Engaging stakeholders early and often builds buy-in, reduces resistance, and supports smoother transitions. Change is managed collaboratively, with stakeholders contributing to defining benefits and validating outcomes. Communication management approaches ensure information flows appropriately across all levels, maintaining transparency. Ultimately, strong stakeholder engagement in Agile projects fosters collaboration between customers and delivery teams, ensures the right product is built, and enables organizations to realize benefits efficiently. It combines PRINCE2's disciplined stakeholder management with Agile's people-centric, adaptive approach, creating a balanced framework for delivering value amid complexity and change.

Servant Leadership and Team Empowerment are foundational concepts within the PRINCE2 Agile framework and the broader Agile Mindset, playing a crucial role in Project Management and Organizational Change. Servant Leadership represents a shift away from traditional command-and-control management towards a supportive, facilitative approach. In this model, the leader's primary role is to serve the team by removing impediments, providing resources, offering guidance, and creating an environment where individuals can thrive. Rather than dictating tasks, the servant leader focuses on empowering the team to make decisions and take ownership of their work. Within PRINCE2 Agile, this leadership style complements the disciplined governance of PRINCE2 while embracing the flexibility of Agile. It bridges the gap between structured management and self-organising teams, ensuring that projects remain aligned with organisational objectives while allowing teams the autonomy to deliver value effectively. Team Empowerment is closely linked to servant leadership. It involves granting teams the authority, trust, and responsibility to self-organise, make decisions, and determine how best to accomplish their goals. Empowered teams are more motivated, engaged, and productive because they feel a genuine sense of ownership over outcomes. In Agile, empowerment is essential for enabling rapid responses to change, fostering innovation, and encouraging continuous improvement. From an Organizational Change perspective, adopting servant leadership and team empowerment requires a cultural transformation. Organisations must move away from hierarchical structures towards collaborative, trust-based relationships. This transition can be challenging, as it demands new behaviours from both leaders and team members. However, when successfully implemented, these principles create resilient, high-performing teams capable of delivering quality products iteratively. Ultimately, servant leadership and team empowerment work together to support the Agile values of collaboration, adaptability, and customer focus, while maintaining the control and direction provided by PRINCE2, resulting in more successful and sustainable project delivery across the organisation and beyond.

Team Culture and Working Agreements are foundational concepts in PRINCE2 Agile that support the agile mindset and effective project delivery. Team Culture refers to the shared values, behaviors, attitudes, and norms that define how a team collaborates and interacts. In an agile context, a healthy team culture emphasizes trust, transparency, collaboration, self-organization, and continuous improvement. It aligns with the agile mindset by fostering psychological safety, where team members feel empowered to experiment, fail fast, learn, and openly share ideas without fear of blame. A strong culture enables teams to embrace change, respond flexibly to customer needs, and maintain motivation and engagement throughout the project lifecycle. Working Agreements, sometimes called team charters or team norms, are explicit, mutually agreed-upon guidelines that establish how team members will work together. These are typically co-created by the team to ensure ownership and commitment. Common elements include communication protocols, meeting cadences, definitions of 'done', decision-making processes, conflict resolution methods, core working hours, and expectations around collaboration and respect. In PRINCE2 Agile, Working Agreements help operationalize the culture by making implicit expectations explicit, reducing ambiguity, and preventing misunderstandings. In the realm of Project Management and Organizational Change, Team Culture and Working Agreements bridge the gap between traditional governance (PRINCE2 principles, themes, and processes) and agile flexibility. They support the 'behaviors' aspect central to PRINCE2 Agile, which includes transparency, collaboration, rich communication, self-organization, and exploration. As organizations transition toward agile ways of working, establishing positive culture and clear agreements reduces resistance to change, accelerates adoption, and improves team performance. Together, these concepts create an environment where teams can deliver value iteratively while remaining aligned with project controls and organizational objectives. They ensure that agility is not chaotic but disciplined, enabling sustainable, high-quality outcomes that satisfy both business needs and stakeholder expectations effectively.