Why P3M?
What's it all about?
Portfolio, Programme and Project Management (P3M) is a structured approach to delivering an organisation’s strategic objectives through coordinated change. Rooted in frameworks such as the Association for Project Management (APM) Body of Knowledge, P3M provides a hierarchy that links high-level strategy to practical delivery.
At its core, project management focuses on delivering specific outputs within defined constraints such as time, cost and quality. Projects are temporary endeavours with clear objectives—building a system, launching a product, or implementing a process.
Programme management sits above this, coordinating multiple related projects to achieve outcomes and benefits that would not be realised if the projects were managed independently.
Programmes are concerned less with outputs and more with outcomes and benefits, ensuring that change is integrated and aligned with organisational goals.
At the highest level, portfolio management ensures that all projects and programmes are collectively aligned with strategy. It involves prioritisation, resource allocation, risk balancing, and governance to maximise value across the organisation. Not every initiative can or should be pursued—portfolio management helps decide which ones matter most.
The APM Body of Knowledge emphasises that P3M is not just about processes, but about governance, leadership, and value delivery. Effective P3M requires clear decision-making structures, stakeholder engagement, and the ability to adapt to change. It also recognises the importance of benefits management—ensuring that intended improvements are actually realised.
In practice, P3M enables organisations to move from strategy to execution in a controlled and coherent way. By integrating projects, programmes, and portfolios, it ensures that effort is not wasted, risks are managed holistically, and outcomes contribute meaningfully to long-term success.
In short, P3M is the discipline that connects what an organisation wants to achieve with how it actually gets there.
Peter Benton ChPP, CEng, CITP
www.linkedin.com/in/peter-benton-7015672
Understanding Projects, Programmes and Portfolios
What's the difference and when would you use each one?
A project can be defined as, “a unique, transient endeavour undertaken to bring about change and to achieve planned objectives” (APM Body of Knowledge 8th Edition).
A programmes, however, can be defined as, “a unique, transient strategic endeavour undertaken to achieve beneficial change and incorporating a group of related projects and business as usual (steady state) activities” (APM Body of Knowledge 8th Edition).
We can see that the two key differences are
- projects tend to be "tactical" in nature, whereas programmes usually deliver more strategic change
- projects are generally "endeavours" in themselves, whereas programmes deal with a set of related projects or other activities
We would often use a project to bring about a point change or deliverable, but use a programme to effect something with a wider reach or at a "higher" level.
Of course, the above are generalisations, there are grey areas and the vehicle used is often a matter of judgement. But we do have a choice, and although this will be dependent on a range of factors, a general guide might be to choose the one that gives the best results.
A portfolio can be defined as “a collection of projects and/or programmes used to structure and manage investments at an organistional or functional level to optimise strategic benefits or operational efficiency” (APM Body of Knowledge 8th Edition).
A portfolio can be thought of as an overall structure that binds together and guides all of the change initiatives in an organisation (or function) to ensure that best value and best benefit is being realised from the investment made in money, time and other resources.
Portfolio management is often conducted by a separate team and/or at C-suite level, and needs to be flexible so that as internal and external conditions change, outcomes and benefits are optimised.
Peter Benton ChPP, CEng, CITP
What is Project Management and Why is it Different?
Why would we use it when we have "normal" management?
Project management is "the application of processes, methods, skills, knowledge and experience to achieve specific project objectives for change" (definition from APM Body of Knowledge 8th edition).
We might also add that this needs to be according to the project acceptance criteria within agreed parameters. This almost always means that project management involves producing final deliverables that are constrained to a finite timescale and budget. (See https://www.apm.org.uk/resources/what-is-project-management/)
Therefore, we can see that a key factor that distinguishes project management from just 'management' is that it has this final deliverable and a finite timespan, unlike management which is an ongoing process. Because of this a project professional needs a wide range of skills - often technical skills, and certainly people management skills and good business awareness.
But why is project management different from other forms of management?
One answer to this is that project management differs from other forms of management because it is fundamentally concerned with delivering change, rather than maintaining ongoing operations. Drawing on the APM Body of Knowledge, this distinction lies at the heart of what makes project management unique.
Unlike operational or functional management, which focuses on repetitive activities and steady-state performance, project management deals with temporary endeavours. Projects have a defined start and end, specific objectives, and are often characterised by uncertainty and risk. This means project managers must work within constraints—typically time, cost, and quality—while navigating ambiguity.
Another key difference is the focus on outputs and objectives. Operational managers are responsible for sustaining business-as-usual activities, ensuring efficiency and consistency. In contrast, project managers are tasked with creating something new—whether a product, service, or capability—that delivers a defined outcome.
Project management also requires a high degree of cross-functional coordination. Projects often cut across organisational boundaries, bringing together diverse teams, stakeholders, and expertise for a limited period. This contrasts with traditional management roles, which are usually tied to a specific department or function.
The APM Body of Knowledge highlights the importance of governance, stakeholder engagement, and risk management in projects. Because projects are inherently uncertain and involve change, they demand structured decision-making and proactive management of risks and opportunities.
Finally, success in project management is measured differently. While operational management focuses on ongoing performance metrics, project success is typically judged by whether the project delivers its intended outputs and contributes to desired outcomes and benefits.
In essence, project management is distinct because it is about managing change in a controlled way—turning ideas into reality—while other forms of management are primarily concerned with sustaining and optimising what already exists.
Peter Benton ChPP, CEng, CITP
Project Lifecycles
How can we get from the beginning to the end?
Introduction
A project life cycle describes the structured phases a project passes through from initiation to completion. According to the APM Body of Knowledge, life cycles provide a framework for managing work, controlling risk, and ensuring that outputs and outcomes are delivered effectively. While all projects follow a life cycle, the form it takes can vary significantly depending on the nature of the work.
We will briefly look at three types:
- Linear (or "predictive", sometimes known as "waterfall" or "stage gate")
- Iterative (or "adaptive")
- Hybrid
Linear (Predictive) Life Cycle
A linear life cycle—often called predictive or waterfall—is a sequential approach where each phase is completed before the next begins. It is best suited to projects where requirements are well understood from the outset.
Typical phases include:
- Concept / Initiation
- Definition / Planning
- Development / Execution
- Handover / Closure
An example is shown in the diagram below.
Key characteristics include:
- Clear structure and documentation
- Limited flexibility once underway
- Strong governance and control
- Suitable for construction, infrastructure, or regulated environments
The strength of this approach lies in its predictability, but it can struggle when requirements change.
Iterative (Adaptive) Life Cycle
An iterative life cycle is designed for environments with uncertainty or evolving requirements. Work is delivered in repeated cycles (iterations), allowing for feedback and refinement along the way.
Key characteristics include:
- Incremental delivery of outputs
- Continuous stakeholder feedback
- Flexibility to adapt scope and design
- Emphasis on learning and improvement
This approach is common in software development and innovation projects, where it is difficult to define all requirements upfront. The trade-off is less predictability in scope and sometimes cost. The diagram below shows a "scrum" type variant of an iterative life cycle, often used in software development.
Hybrid Life Cycle
A hybrid life cycle combines elements of both linear and iterative approaches. It recognises that different parts of a project may require different levels of certainty and flexibility.
Key characteristics include:
- Structured phases with iterative components
- Flexibility where needed, control where required
- Tailored approach based on project complexity
- Increasingly common across industries
For example, a project might use a linear approach for overall governance and milestones, while adopting iterative methods for specific stages, for example development of specific components like software or user interfaces. This is shown in the sample diagram below.
Choosing the Right Life Cycle
The APM Body of Knowledge emphasises that selecting a life cycle is not about preference, but about fitness for purpose. Factors influencing this choice include:
- Clarity of requirements
- Level of uncertainty
- Stakeholder needs
- Risk profile
- Regulatory constraints
Conclusion
Project life cycles provide the backbone for managing delivery. Whether linear, iterative, or hybrid, each approach offers different strengths. The key is understanding the context of the project and applying the most appropriate structure to balance control, flexibility, and value delivery.
In practice, the most effective project managers are those who can adapt the life cycle to the situation, rather than rigidly following a single model.
Peter Benton ChPP, CEng, CITP
Project, Programme and Portfolio Governance
Maintaining Overall Accountability and Control
Governance is the framework of authority and accountability that defines and controls the outputs, outcomes and benefits from projects, programmes and portfolios. It is the mechanism whereby the investing organisation exerts financial and technical control over the deployment of the work and the realisation of value. (Definition from APM Body of Knowledge 8th edition).
See https://www.apm.org.uk/resources/what-is-project-management/what-is-governance/
Project governance arrangements define how decisions are made, authority is exercised, and accountability is maintained throughout the life of a project. Effective governance ensures that projects remain aligned with organisational strategy while being delivered in a controlled, transparent, and ethical manner.
At its core, project governance provides a framework for oversight and direction. It establishes clear roles, responsibilities, and reporting lines so that everyone involved understands who has the authority to make decisions and how those decisions are escalated. This typically includes defined roles such as the project sponsor, project manager, and governance boards or steering groups.
A key element of governance arrangements is the definition of decision points and controls. These are often implemented through stage gates or review points, where progress is assessed against agreed criteria. At these points, decisions are made to continue, change, or stop the project, ensuring that resources are used effectively and risks are managed proactively.
The APM Body of Knowledge emphasises the importance of accountability and assurance. Governance arrangements should provide independent oversight to confirm that the project is being managed properly and that it remains viable. This may involve audits, health checks, or assurance reviews that provide confidence to stakeholders.
Another critical aspect is alignment with organisational governance. Projects do not operate in isolation—they must fit within wider corporate governance structures, including financial controls, risk management frameworks, and strategic priorities. Strong alignment ensures consistency and supports better decision-making across the organisation.
Stakeholder engagement is also central to effective governance. Governance arrangements should ensure that the right stakeholders are involved at the right time, with clear communication channels in place. This helps to build trust, manage expectations, and support informed decision-making.
Finally, governance must be proportionate and tailored to the project’s complexity, risk, and importance. Overly rigid governance can slow progress, while insufficient governance can lead to poor control and increased risk. The APM highlights the need to strike the right balance, adapting governance arrangements to suit the specific context.
In summary, project governance arrangements provide the structure that enables projects to be directed, controlled, and assured. When designed effectively, they support better decisions, improved accountability, and successful delivery of outcomes aligned with organisational objectives.
Peter Benton ChPP, CEng, CITP
Project Sustainability
Thinking of the Long Term
Project sustainability refers to the consideration of environmental, social, and economic impacts throughout the life cycle of a project and beyond. The APM Body of Knowledge (8th edition) highlights sustainability as a key responsibility of project professionals, ensuring that projects not only deliver outputs and benefits, but do so in a way that supports long-term value and minimises harm.
At its core, project sustainability is about balancing short-term delivery with long-term consequences. Projects often create change that extends well beyond their completion, so decisions made during planning and execution can have lasting effects on communities, resources, and the environment. Sustainable project management seeks to ensure that these impacts are understood and managed responsibly.
A key element is the integration of environmental considerations. This includes reducing carbon emissions, minimising waste, and using resources efficiently. Projects should assess their environmental footprint and look for opportunities to adopt more sustainable practices, such as low-impact materials, energy-efficient processes, and circular economy principles.
Equally important are social factors. The APM emphasises the need to consider how projects affect people—both directly and indirectly. This includes health and safety, community impact, equality, and ethical working practices. Sustainable projects aim to create positive social outcomes while avoiding harm or unintended negative consequences.
The third pillar is economic sustainability, which focuses on delivering value over the long term. This goes beyond immediate cost efficiency to consider whole-life value, including maintenance, operation, and eventual disposal. Projects should aim to optimise benefits in a way that is financially viable and supports organisational and societal goals.
The APM Body of Knowledge also highlights the importance of governance and decision-making in sustainability. Sustainability considerations should be embedded into project governance arrangements, business cases, and decision criteria. This ensures that sustainability is not treated as an afterthought, but as a core aspect of how projects are selected and delivered.
Stakeholder engagement plays a crucial role. Understanding the expectations and concerns of stakeholders—such as customers, communities, regulators, and investors—helps ensure that sustainability objectives are relevant and achievable. Transparent communication also supports accountability and trust.
Finally, sustainability requires a whole-life perspective. Project teams should consider not just delivery, but the operation, use, and end-of-life of project outputs. This life cycle thinking helps to identify opportunities for improvement and avoid shifting problems into the future.
In summary, project sustainability is about ensuring that projects deliver lasting value in a responsible way. By integrating environmental, social, and economic considerations into decision-making, project professionals can contribute to outcomes that are not only successful, but also sustainable for the future.
Peter Benton ChPP, CEng, CITP
Financial Management
Managing the Money
Project financial management is concerned with planning, controlling, and monitoring the financial resources required to deliver a project successfully. The APM Body of Knowledge (8th edition) positions financial management as a critical discipline that ensures projects are both affordable and deliver value in line with organisational objectives.
At its core, financial management involves establishing a robust business case. This sets out the justification for the project, including expected costs, benefits, and value for money. It provides the foundation for investment decisions and is used throughout the project to assess ongoing viability.
A key element is cost estimating and budgeting. Early estimates provide an indication of affordability, while more detailed budgets are developed as the project progresses. These budgets allocate funding across different activities and time periods, forming a baseline against which performance can be measured.
Closely linked is cost control, which ensures that expenditure remains within approved limits. This involves tracking actual costs, forecasting future spend, and managing variances. Techniques such as earned value management may be used to integrate cost, schedule, and performance data, providing insight into project health.
The APM Body of Knowledge also emphasises the importance of financial governance and assurance. Projects must operate within organisational financial controls, including approval processes, audit requirements, and reporting standards. Regular financial reporting provides transparency and supports informed decision-making by sponsors and governance bodies.
Another important aspect is benefits and value management. Financial management is not just about controlling costs—it is also about ensuring that the project delivers the expected financial and non-financial benefits. This includes assessing return on investment, whole-life costs, and the timing of benefits realisation.
Risk and uncertainty play a significant role in financial management. Projects often face cost-related risks, such as price fluctuations, scope changes, or unforeseen events. Contingencies and risk allowances are therefore built into budgets, and financial plans are regularly reviewed and updated.
Finally, financial management requires integration with wider project controls. It must align with scheduling, resource management, procurement, and risk management to provide a coherent view of project performance. This integrated approach supports better forecasting and more effective decision-making.
In summary, project financial management ensures that projects are planned, funded, and controlled effectively, delivering value while maintaining financial discipline. When applied well, it enables organisations to make sound investment decisions and maximise the benefits of their projects.
Peter Benton ChPP, CEng, CITP
Business Cases
Justifying the Investment
A business case provides the justification for undertaking a project, setting out why the investment is needed and how it will deliver value. The APM Body of Knowledge (8th edition) defines the business case as a living document that supports decision-making throughout the project life cycle, from initial concept through to benefits realisation.
At its core, a business case explains the rationale for change. It identifies the problem or opportunity being addressed and outlines how the proposed project aligns with organisational strategy. This ensures that projects are not undertaken in isolation, but contribute meaningfully to wider objectives.
A key component is the assessment of options. Rather than assuming a single solution, a robust business case evaluates multiple approaches, including the “do nothing” option. Each option is analysed in terms of costs, benefits, risks, and feasibility, enabling informed comparisons and selection of the most appropriate course of action.
The business case also sets out the expected benefits and value. These may be financial, such as increased revenue or reduced costs, or non-financial, such as improved customer satisfaction or enhanced capability. Clear definition of benefits provides a basis for measuring success and supports ongoing justification of the project.
Equally important is the consideration of costs, risks, and uncertainties. The business case includes estimates of investment required, along with an assessment of potential risks and their impact on viability. This helps decision-makers understand not only the potential rewards, but also the level of exposure involved.
The APM Body of Knowledge emphasises that the business case should be continually reviewed and updated. As the project progresses and more information becomes available, assumptions may change. Regular reviews—often at stage gates—ensure that the project remains viable and aligned with its original objectives, or that corrective action is taken if necessary.
Governance and ownership are also critical. The business case is typically owned by the project sponsor, who is accountable for ensuring that it remains valid and that the anticipated benefits are realised. This reinforces the link between strategic intent and project delivery.
Finally, the business case adopts a whole-life perspective, considering not just the cost of delivery, but also the operational, maintenance, and end-of-life implications of the project’s outputs. This ensures that decisions are based on long-term value rather than short-term gains.
In summary, the business case is the foundation for informed investment decisions, providing a structured and evidence-based justification for projects. When managed effectively, it ensures that resources are committed to initiatives that deliver real and lasting value.
Peter Benton ChPP, CEng, CITP
Portfolio Shaping
Determining the Content of the Portfolio
Portfolio shaping is the process of selecting, prioritising, and balancing an organisation’s projects and programmes to ensure alignment with strategic objectives and optimal use of resources. In the APM Body of Knowledge (8th edition), portfolio shaping is a key aspect of portfolio management, focused on deciding what change initiatives should be undertaken.
At its core, portfolio shaping is about strategic alignment. Organisations typically have more potential initiatives than they can realistically deliver, so choices must be made about where to invest. Portfolio shaping ensures that selected projects and programmes directly support business goals and contribute to long-term value.
A key element is the evaluation and selection of initiatives. Proposals are assessed using defined criteria, such as expected benefits, costs, risks, and strategic fit. This often involves comparing different options and making trade-offs to determine which initiatives offer the greatest value.
Closely linked is prioritisation. Not all initiatives are equally important or urgent, so portfolio shaping establishes a clear order of precedence. This helps ensure that limited resources—such as funding, people, and time—are allocated to the most valuable work.
The APM Body of Knowledge also highlights the importance of balancing the portfolio. A well-shaped portfolio considers a mix of factors, such as:
- Short-term vs long-term benefits
- High-risk vs low-risk initiatives
- Mandatory vs discretionary work
- Innovation vs operational improvement
This balance helps organisations manage risk while still pursuing opportunities for growth and transformation.
Resource capacity and constraints are another critical consideration. Portfolio shaping must take into account what the organisation can realistically deliver. Overcommitting resources can lead to delays, reduced quality, and failure to realise benefits. Effective shaping ensures that demand does not exceed capacity.
The process is not static—portfolio shaping requires ongoing review and adjustment. As organisational priorities change or new information emerges, the portfolio may need to be reshaped. This can involve starting new initiatives, reprioritising existing ones, or stopping projects that no longer deliver sufficient value.
Governance and decision-making play a central role. Portfolio boards or senior leadership teams are typically responsible for shaping decisions, supported by robust data and analysis. Clear governance ensures transparency, accountability, and consistency in how decisions are made.
In summary, portfolio shaping is about choosing the right work at the right time. By aligning initiatives with strategy, balancing risk and reward, and managing resource constraints, organisations can ensure that their portfolio delivers maximum value and supports long-term success.
Peter Benton ChPP, CEng, CITP
Project Procurement
Obtaining Goods and Services from Outside the Organisation
Project procurement is the process of acquiring goods, services, or works from external suppliers to support the delivery of a project. The APM Body of Knowledge (8th edition) highlights procurement as a critical function that enables organisations to access expertise, resources, and capabilities that are not available internally.
At its core, project procurement is about making informed decisions on how and from whom to obtain what the project needs. This begins with defining requirements clearly—what is to be procured, the expected quality, and the outcomes to be achieved. Well-defined requirements are essential for ensuring that suppliers can deliver effectively and that expectations are aligned.
A key element is the selection of an appropriate procurement strategy. This includes decisions about contract types, supplier relationships, and risk allocation. For example, organisations may choose between fixed-price, cost-reimbursable, or target-cost contracts depending on the level of uncertainty and the desired balance of risk between client and supplier.
The APM Body of Knowledge emphasises the importance of supplier selection and evaluation. This typically involves a structured process such as tendering or negotiation, where potential suppliers are assessed against criteria including capability, cost, quality, and experience. The aim is to select suppliers who can deliver value and align with the project’s objectives.
Once a supplier is appointed, contract management becomes essential. Contracts define the terms of engagement, including scope, responsibilities, payment mechanisms, and performance expectations. Effective contract management ensures that both parties meet their obligations and that any issues are addressed promptly.
Risk management is a central consideration in procurement. External suppliers introduce additional risks, such as delays, cost overruns, or performance issues. Procurement strategies and contracts should therefore allocate and manage these risks appropriately, ensuring that they are borne by the party best able to control them.
The APM Body of Knowledge also highlights the importance of relationships and collaboration. Successful procurement is not just transactional—it often depends on strong working relationships between the project team and suppliers. Collaborative approaches can improve communication, enhance problem-solving, and lead to better outcomes.
Governance and compliance are equally important. Procurement activities must adhere to organisational policies, legal requirements, and ethical standards. Transparent processes and clear documentation help ensure fairness, accountability, and value for money.
Finally, procurement should be aligned with the project’s overall objectives and constraints, including schedule, cost, and quality. It must also integrate with other project management functions, such as risk, scheduling, and financial management, to support effective delivery.
In summary, project procurement is about acquiring the right resources, in the right way, at the right time. When managed effectively, it enables projects to leverage external expertise, manage risk, and deliver value in line with organisational goals.
Peter Benton ChPP, CEng, CITP
Project Reviews
How are We Doing?
Project reviews are structured assessments conducted at key points during a project’s life cycle to evaluate progress, performance, and ongoing viability. The APM Body of Knowledge (8th edition) identifies project reviews as an essential component of governance, providing assurance that a project remains aligned with its objectives and continues to deliver value.
At their core, project reviews are about informed decision-making. They provide stakeholders with the information needed to determine whether a project should proceed as planned, be adjusted, or, in some cases, be stopped. This ensures that resources are used effectively and that projects remain justified.
A key element is the use of formal review points, often aligned with stage gates. At these points, the project is assessed against predefined criteria such as performance against schedule and budget, risk exposure, quality of outputs, and alignment with the business case. These reviews act as control mechanisms, ensuring that progress is transparent and accountable.
The APM Body of Knowledge highlights different types of reviews, including:
- Gate reviews, which support decision-making at key transition points
- Health checks, which provide a snapshot of project performance
- Assurance reviews, which offer independent verification of project status
- Post-project reviews, which capture lessons learned and evaluate success
Independence and objectivity are important characteristics of effective reviews. While project teams may conduct internal assessments, independent reviewers can provide unbiased insights and challenge assumptions, increasing confidence in the findings.
Another critical aspect is the focus on performance and learning. Reviews are not only about identifying issues but also about recognising good practice and opportunities for improvement. Lessons learned can be applied both within the current project and across future initiatives.
Stakeholder involvement is also essential. Reviews should engage the right stakeholders, including sponsors, governance bodies, and subject matter experts. This ensures that decisions are informed by a range of perspectives and that there is shared understanding of project status.
The APM Body of Knowledge emphasises that reviews should be proportionate and timely. Too many reviews can create unnecessary burden, while too few can reduce visibility and control. The frequency and depth of reviews should reflect the project’s complexity, risk, and importance.
Finally, project reviews support ongoing alignment with the business case. By regularly reassessing whether the project remains viable and desirable, organisations can ensure that they continue to invest in initiatives that deliver value.
In summary, project reviews provide a structured way to monitor, evaluate, and improve project performance. When applied effectively, they enhance governance, support better decisions, and contribute to successful project outcomes.
Peter Benton ChPP, CEng, CITP
Project Assurance
Getting That Nice Warm Feeling (or Not)
Project assurance is the process of providing independent and objective confidence that a project is being managed effectively and is likely to achieve its objectives. The APM Body of Knowledge (8th edition) identifies assurance as a key element of governance, ensuring that projects remain viable, controlled, and aligned with organisational goals.
At its core, project assurance is about building confidence for stakeholders. It provides evidence that appropriate processes, controls, and standards are in place, and that the project is progressing as intended. This enables sponsors and governance bodies to make informed decisions with greater certainty.
A defining feature of assurance is its independence. Unlike project controls or internal reporting, assurance is typically carried out by individuals or teams who are separate from the project’s day-to-day management. This independence allows for objective assessment and constructive challenge, helping to identify issues that may not be visible from within the project team.
The APM Body of Knowledge highlights several key areas that assurance activities may cover, including:
- Governance and decision-making structures
- Alignment with the business case and strategic objectives
- Risk management and controls
- Performance against scope, schedule, cost, and quality
- Compliance with organisational policies and standards
Assurance can take many forms, such as audits, health checks, peer reviews, and gateway reviews. These activities may be scheduled at key points in the project life cycle or triggered by specific risks or concerns. Each provides a different level of depth and focus, but all aim to improve confidence in project delivery.
Another important aspect is the role of assurance in early identification of issues. By providing independent scrutiny, assurance helps to highlight risks, weaknesses, or deviations from plan before they escalate into significant problems. This enables timely corrective action and supports better project outcomes.
Stakeholder communication is also central to effective assurance. Findings from assurance activities are typically reported to sponsors and governance bodies, ensuring transparency and accountability. Clear, evidence-based reporting helps decision-makers understand the project’s status and any actions required.
The APM Body of Knowledge emphasises that assurance should be proportionate and risk-based. The level of assurance applied should reflect the project’s complexity, scale, and risk profile. High-risk or strategically important projects will typically require more rigorous and frequent assurance activities.
Finally, project assurance contributes to continuous improvement. Insights gained from assurance reviews can inform better practices, both within the current project and across the organisation’s wider portfolio.
In summary, project assurance provides independent confidence that a project is on track and under control. When applied effectively, it strengthens governance, supports informed decision-making, and increases the likelihood of successful delivery.
Peter Benton ChPP, CEng, CITP
Capability Development
Looking to the Future
Capability development is the process of building and enhancing an organisation’s ability to deliver projects, programmes, and portfolios effectively. The APM Body of Knowledge (8th edition) recognises capability development as essential for improving performance, enabling consistent delivery, and supporting long-term organisational success.
At its core, capability development is about strengthening the skills, systems, and structures needed to deliver change. It goes beyond individual competence to include organisational processes, tools, governance, and culture. The aim is to create an environment where projects can be delivered efficiently and consistently.
A key element is the development of people and competencies. This includes training, professional development, and the establishment of clear career pathways for project professionals. Frameworks such as competency models help define the knowledge, skills, and behaviours required for effective performance.
The APM Body of Knowledge also highlights the importance of standardised processes and methodologies. By adopting consistent approaches to project delivery—such as common life cycles, governance frameworks, and reporting structures—organisations can improve efficiency, reduce risk, and enable better collaboration across teams.
Another critical aspect is the use of tools and systems. Effective capability development includes implementing appropriate technologies to support planning, scheduling, risk management, and performance tracking. These tools provide visibility and enable better decision-making.
Organisational learning plays a central role. Lessons learned from previous projects should be captured, shared, and applied to future work. This continuous learning approach helps organisations improve over time and avoid repeating mistakes.
The APM Body of Knowledge emphasises the importance of leadership and culture in capability development. Strong leadership supports the adoption of best practices, while a positive culture encourages collaboration, accountability, and continuous improvement. Without these, even well-designed processes may not be effective.
Governance and maturity assessment are also important. Organisations often use maturity models to assess their current capabilities and identify areas for improvement. This provides a structured approach to capability development, helping to prioritise initiatives and measure progress.
Finally, capability development must be aligned with organisational strategy. Investments in people, processes, and tools should support the organisation’s strategic objectives and future needs, ensuring that capability is developed where it adds the most value.
In summary, capability development is about building the foundations for effective project delivery. By enhancing skills, standardising practices, and fostering a culture of learning and improvement, organisations can increase their ability to deliver successful outcomes consistently and sustainably.
Peter Benton ChPP, CEng, CITP
Transition Management
Working Towards the New Business as Usual
Transition management is the process of ensuring that the outputs of a project are successfully integrated into business-as-usual operations so that intended benefits can be realised. The APM Body of Knowledge (8th edition) highlights transition management as a critical link between project delivery and operational value, ensuring that change is adopted, embedded, and sustained.
At its core, transition management is about moving from delivery to use. While projects create outputs—such as systems, facilities, or processes—these only deliver value when they are effectively adopted by the organisation. Transition management ensures that the receiving environment is prepared, capable, and ready to operate the new capability.
A key element is planning for transition early in the project life cycle. Transition is not something that happens at the end—it must be considered from the outset. This includes defining how outputs will be handed over, what support is required, and how success will be measured in operational terms.
The APM Body of Knowledge emphasises the importance of stakeholder readiness and engagement. Users, operators, and support teams must be involved throughout the project to ensure they understand the change and are prepared to adopt it. This may include training, communication, and change management activities to build confidence and capability.
Another critical aspect is operational readiness. This involves ensuring that processes, systems, resources, and support arrangements are in place before handover. Readiness assessments or acceptance criteria are often used to confirm that the organisation can sustain the new capability effectively.
Handover and acceptance are central to transition management. Clear criteria should be established to define when outputs are complete and acceptable. Formal acceptance processes help ensure that responsibilities are transferred appropriately from the project team to operational teams.
The APM Body of Knowledge also highlights the importance of benefits realisation. Transition management supports the tracking and delivery of benefits after project completion, ensuring that the intended value is achieved. This may involve ongoing monitoring and adjustments as the new capability is embedded.
Risk management remains important during transition. Risks such as user resistance, operational disruption, or inadequate support must be identified and managed to ensure a smooth transition.
Finally, transition management requires alignment between project and operational governance. Clear roles, responsibilities, and communication channels help ensure continuity and accountability as the project moves into business-as-usual.
In summary, transition management ensures that project outputs are successfully adopted and deliver real value. By focusing on readiness, handover, and benefits realisation, it bridges the gap between project completion and operational success.
Peter Benton ChPP, CEng, CITP
Benefits Management
Delivering the Promised Made in the Business Case
Benefits management is the process of identifying, planning, tracking, and realising the benefits that a project or programme is intended to deliver. The APM Body of Knowledge (8th edition) positions benefits management as central to ensuring that projects create real, measurable value, rather than simply delivering outputs.
At its core, benefits management is about linking outputs to outcomes. While projects produce deliverables—such as systems, products, or infrastructure—benefits arise from how those deliverables are used. Effective benefits management ensures that this connection is clearly understood and actively managed.
A key element is the identification and definition of benefits. Benefits should be clearly articulated, measurable where possible, and aligned with organisational objectives. This includes both tangible benefits, such as cost savings or increased revenue, and intangible benefits, such as improved customer satisfaction or enhanced capability.
The APM Body of Knowledge emphasises the importance of benefits planning. This involves mapping how project outputs will lead to outcomes and ultimately deliver benefits, often using tools such as benefits maps or profiles. It also includes defining ownership, timelines, and measures for each benefit.
Another critical aspect is benefits ownership and accountability. Benefits are typically realised outside the project, within operational areas of the organisation. As such, responsibility for achieving them often lies with business owners rather than the project manager. Clear accountability ensures that benefits are actively pursued after project delivery.
Monitoring and tracking are essential to ensure that benefits are realised as expected. This involves measuring performance against defined indicators and reviewing progress over time. Regular reporting provides visibility and supports informed decision-making.
The APM Body of Knowledge also highlights the need for ongoing review and adaptation. As circumstances change, expected benefits may need to be reassessed. Some benefits may take longer to materialise, while others may no longer be achievable. Continuous review ensures that the focus remains on delivering value.
Integration with governance and the business case is another key consideration. Benefits management should be embedded within governance arrangements and used to inform decisions at stage gates and reviews. The business case should be updated to reflect changes in expected benefits, ensuring that the project remains justified.
Finally, benefits management adopts a whole-life perspective, extending beyond project completion. Realising benefits often requires sustained effort, monitoring, and sometimes additional change initiatives after handover.
In summary, benefits management ensures that projects deliver meaningful and measurable value. By focusing on outcomes, accountability, and continuous tracking, it helps organisations move beyond delivery to achieve the benefits that justify investment in the first place.
Peter Benton ChPP, CEng, CITP
Stakeholder and Communications Management
Navigating Power and Interest
Stakeholder and communications management is the process of identifying, analysing, and engaging individuals or groups who can influence or are affected by a project, and ensuring that information is communicated effectively to support successful delivery. The APM Body of Knowledge (8th edition) highlights this as a critical discipline for building support, managing expectations, and enabling informed decision-making.
We might say that a stakeholder is someone (or a group) who has either power or interest (or both) in a project, programme or portfolio.
At its core, stakeholder and communications management is about understanding people and their needs. Projects operate within complex environments involving sponsors, users, suppliers, regulators, and other interested parties. Each stakeholder may have different expectations, levels of influence, and concerns, all of which must be recognised and managed.
A key element is stakeholder identification and analysis. This involves determining who the stakeholders are, assessing their interests, influence, and attitudes, and understanding how they may impact—or be impacted by—the project. Tools such as stakeholder mapping help prioritise engagement efforts.
The APM Body of Knowledge emphasises the importance of engagement and relationship management. Effective engagement goes beyond simply informing stakeholders—it involves building trust, addressing concerns, and fostering collaboration. This may include regular meetings, workshops, and feedback mechanisms to ensure stakeholders are actively involved where appropriate.
Closely linked is communications planning. A structured communications plan defines what information will be shared, with whom, how often, and through which channels. This ensures that stakeholders receive the right information at the right time, supporting transparency and alignment.
Tailoring communication is another critical aspect. Different stakeholders require different types and levels of information. Senior decision-makers may need concise, high-level summaries, while project teams may require detailed operational information. Effective communication adapts to these needs to maximise clarity and impact.
The APM Body of Knowledge also highlights the role of listening and feedback. Communication is a two-way process, and actively seeking and responding to stakeholder feedback helps identify issues early, improve decision-making, and strengthen relationships.
Managing expectations and conflict is an inherent part of stakeholder management. Projects often involve competing interests, and differences of opinion may arise. Skilled stakeholder management helps to negotiate, influence, and resolve conflicts in a constructive way.
Finally, stakeholder and communications management must be integrated with governance and leadership. Clear communication supports effective decision-making, while strong leadership helps align stakeholders around shared objectives and vision.
In summary, stakeholder and communications management ensures that the right people are engaged in the right way at the right time. When done well, it builds trust, enhances collaboration, and significantly increases the likelihood of project success.
Peter Benton ChPP, CEng, CITP
Conflict Resolution
What Happens Meaningful Differences Exist?
Conflict resolution is the process of identifying, addressing, and resolving disagreements that arise between individuals or groups during a project. The APM Body of Knowledge (8th edition) recognises conflict as a natural and often unavoidable aspect of project work, given the diversity of stakeholders, competing priorities, and inherent pressures of delivery.
At its core, conflict resolution is about managing differences constructively. Projects bring together people with varied perspectives, objectives, and interests, which can lead to tension. Effective conflict resolution does not seek to eliminate disagreement, but to handle it in a way that supports collaboration and project outcomes.
A key element is the early identification of conflict. Recognising signs of disagreement—such as miscommunication, reduced cooperation, or opposing views—allows issues to be addressed before they escalate. Proactive management helps prevent conflict from negatively impacting performance.
The APM Body of Knowledge emphasises the importance of understanding the root causes of conflict. These may include differences in objectives, resource constraints, unclear roles, or interpersonal issues. By identifying underlying causes rather than just symptoms, more effective and lasting solutions can be achieved.
Communication and active listening are central to resolving conflict. Creating an environment where individuals feel heard and understood helps to build trust and openness. Encouraging constructive dialogue allows parties to express their concerns and work towards mutual understanding.
Another important aspect is the use of appropriate resolution strategies. These may include:
- Collaboration, where parties work together to find a mutually beneficial solution
- Compromise, where each side makes concessions
- Accommodation, where one party yields to maintain harmony
- Avoidance, used selectively to allow time for reflection
- Competition, where a decisive outcome is required
The choice of approach depends on the situation, the importance of the issue, and the relationships involved.
The APM Body of Knowledge also highlights the role of leadership and emotional intelligence. Project leaders must be able to manage their own emotions, understand those of others, and facilitate constructive interactions. Strong leadership helps create a culture where conflict is addressed openly and respectfully.
Governance and clarity of roles can also reduce conflict. Clearly defined responsibilities, decision-making authority, and escalation routes help minimise misunderstandings and provide structured ways to resolve disputes when they arise.
Finally, conflict resolution contributes to team performance and learning. When handled effectively, conflict can lead to better ideas, improved relationships, and stronger team cohesion. It can also highlight areas for improvement in processes or communication.
In summary, conflict resolution is about turning disagreement into positive outcomes. By addressing issues early, understanding their causes, and applying appropriate strategies, project professionals can manage conflict in a way that supports collaboration and successful delivery.
Peter Benton ChPP, CEng, CITP
Project Leadership
Vision, Alignment and Empowerment
Project leadership is the ability to guide, influence, and inspire individuals and teams to achieve project objectives and deliver successful outcomes. The APM Body of Knowledge (8th edition) identifies leadership as a critical capability that goes beyond management processes, focusing on people, vision, and direction.
At its core, project leadership is about creating clarity and purpose. Leaders establish a clear vision for the project, aligning team members and stakeholders around shared goals. This sense of purpose helps motivate individuals and ensures that efforts are directed towards achieving meaningful outcomes.
A key element is the ability to influence and engage people. Unlike traditional line management, project leadership often involves working with individuals who do not report directly to the project manager. This requires strong interpersonal skills, including communication, negotiation, and the ability to build trust and credibility.
The APM Body of Knowledge emphasises the importance of adaptability and situational leadership. Different projects, teams, and contexts require different leadership styles. Effective leaders are able to adjust their approach depending on factors such as team maturity, complexity, and organisational culture.
Decision-making and accountability are also central to project leadership. Leaders must be able to make informed and timely decisions, often in uncertain or high-pressure environments. They are responsible for guiding the project through challenges and ensuring that it remains aligned with its objectives.
Another important aspect is developing and supporting the team. Project leaders create an environment where individuals can perform at their best, providing direction, support, and feedback. This includes fostering collaboration, encouraging innovation, and addressing any issues that may affect team performance.
The APM Body of Knowledge also highlights the role of emotional intelligence. Understanding and managing emotions—both one’s own and those of others—enables leaders to handle conflict, build strong relationships, and maintain a positive team environment.
Ethical behaviour and professionalism are fundamental to effective leadership. Project leaders must act with integrity, fairness, and transparency, setting the standard for how the project is conducted. This helps build trust with stakeholders and supports sound decision-making.
Finally, project leadership must be aligned with governance and organisational objectives. Leaders play a key role in ensuring that the project remains strategically aligned and that decisions are made in the best interests of the organisation.
In summary, project leadership is about inspiring people and guiding delivery. By combining vision, influence, adaptability, and integrity, effective leaders enable teams to overcome challenges and achieve successful project outcomes.
Peter Benton ChPP, CEng, CITP
Project Team Management
Building and Maintaining Effective Teams
Project team management is the process of forming, developing, and leading a group of individuals to deliver project objectives effectively. The APM Body of Knowledge (8th edition) highlights team management as a critical discipline, recognising that successful delivery depends not just on processes, but on how people work together.
At its core, project team management is about bringing together the right people and enabling them to perform. Projects often involve individuals from different functions, organisations, and backgrounds, requiring careful coordination to ensure that skills and expertise are aligned with project needs.
A key element is team formation and structure. This includes defining roles and responsibilities, establishing reporting lines, and ensuring that the team has the necessary capabilities. Clear role definition helps avoid confusion and supports accountability across the project.
The APM Body of Knowledge emphasises the importance of team development. Effective teams do not form automatically—they require time, support, and leadership to become high-performing. This includes building trust, establishing shared ways of working, and developing a collaborative culture.
Communication and collaboration are central to team management. Open and effective communication enables team members to share information, resolve issues, and coordinate activities. Collaborative working practices help integrate different perspectives and improve overall performance.
Another important aspect is performance management. This involves setting clear expectations, monitoring progress, and providing feedback. Recognising good performance and addressing underperformance helps maintain motivation and ensures that the team remains focused on delivering objectives.
The APM Body of Knowledge also highlights the role of motivation and engagement. Project environments can be demanding, so maintaining team morale is essential. This may involve recognising achievements, providing opportunities for development, and creating a supportive working environment.
Conflict management is often part of team management. Differences in opinion or working styles can lead to tension, and effective team management involves addressing these issues constructively to maintain cohesion and productivity.
Leadership plays a crucial role in shaping team culture and behaviour. Project leaders set the tone for how the team operates, promoting values such as trust, accountability, and respect. A positive team culture supports better collaboration and resilience.
Finally, project team management must be adaptable. Teams may change over the course of a project, and the approach to management should evolve accordingly. Flexibility ensures that the team remains effective as the project progresses.
In summary, project team management is about creating and sustaining a high-performing team. By focusing on people, relationships, and performance, it enables projects to be delivered successfully and efficiently.
Peter Benton ChPP, CEng, CITP