Project Management Body of Knowledge (PMBOK) ^® – Book Review

IntroductionAgile Manifesto

The PMBOK[1]^{®, which says teams should value:} Guide, brought to the world by the Individuals and interactions over processes and tools;Project Management InstituteWorking software over comprehensive documentation; (PMI)Customer collaboration over contract negotiation;^{®Responding to change over following a plan.}, is a seminal resource in project management. Since its introduction in 1996, it has undergone numerous revisions, the latest one in 2021 being particularly transformative.Essentially what the agile manifesto focuses on is:

The 7Face to face communication amongst the team, often using very visual tools such as post-it notes, whiteboards and flipcharts;^{thDelivering outputs as quickly as possible;} edition represents a monumental shift, addressing significant changes in project management over the past two decades. The recent edition has enhanced its relevance, making it an invaluable tool for project managers.Working with the customer – often daily – to better understand what needs to be delivered;

Whilst another article Being flexible based upon the changing needs of the customer.compares PRINCE2 and the PMBOKAs a marketer, you should learn to become ^®agile, this article will explore some of the main improvements in the PMBOK too. Your competitors aren’t standing still, so it’s better that you step up and learn modern, effective techniques to deliver better digital marketing outcomes.^{®To get you started on your agile journey, here are 8 simple techniques to start using now:} 7Backlog^{thA backlog contains a list of requirements which need to be done either as part of a project, or as part of your regular ongoing digital marketing. These requirements might be things such as writing the copy for an article, developing an infographic, publishing an ebook, or any other digital marketing output.} edition, and how it has stolen some of the clothes of its closest rival, You can create a backlog using some very simple tools. A shared spreadsheet on a cloud file-sharing service is usually fine. You might also decide to keep it extra simple and visual by creating a backlog on a whiteboard in your office.PRINCE2Each item in the backlog needs to be prioritised (see later) and can be described by using a user story..User stories

Standard for Project ManagementUser stories

The PMBOK should be written by the customer in the form:^{®As a …., I want to be able to ….., so that I can …..} 7They must be written in a way that makes it easy for the person doing the task to understand what they need to do.^{thFor example, let’s say your company offers lots of types of widgets – both old and new. Maybe some of your audience collect old widgets and you want to write an article which explains the best web sites to find secondhand widgets.} edition retains its association with the You could write your Standard for Project Managementuser story which comes in three parts: like this:

1. 1. Introduction As a widget collector, I want to know where I can find secondhand widgets, so that I can add to my collection.

      This introduces foundational concepts associated with projects , programmesThis very simple story tells the author who the audience of the article is, and how their needs will be fulfilled., and User stories should specify what will make it ‘done’. For example, it might be considered done when the article contains 1,000+ words, has links to 10 different secondhand widget web sites, has been proof-read and spell-checked and has been published on the company’s blog. ‘Doneness’ indicates when the output created from the user story can be considered finished.portfoliosYou can write .user stories

   2. Value delivery on post-it notes and stick them on your whiteboard backlog or use a free tool to share amongst your team.

      This expounds on the importance of value in organizational contexts and highlights the roles that contribute to this value generation, especially in projects.Sprints

   3. Project management principlesSprints are very common in the

      This sheds light on 12 fundamental principles that guide strategies, decision-making, and problem-solving in projects.Scrum method

Read together, these three sections lead nicely into the PMBOK. A sprint is a fixed time period in which work is completed. It might be two weeks, a month or any other amount of time.^{®The key thing about sprints is that they should be of equal length and at the end of the sprint there must be some finished outputs which can then be used by the team – e.g. the widget collector’s article has been published and is attracting engagement from users.} itself and sets the context for the remainder of the PMBOKBefore planning each sprint, the team reviews the last sprint before deciding what to work on in the coming sprint. Sprint planning works best when used alongside a Kanban board, so everyone can visualise which tasks were completed last sprint and then choose the tasks to work on next sprint.^®Kanban itself.Kanban

Inside the PMBOK is a visual work management system using cards to represent each task. If you’re using user stories to capture your company’s requirements the Kanban tasks are your user stories.^{®A typical Kanban board consists of three columns: to-do, in progress and complete. If you’re using a whiteboard for your backlog, you can draw these columns on the whiteboard after your backlog.} 7Tasks are moved from the backlog into the to-do column on the Kanban board. This happens when planning the sprint. Each task is assigned to someone on the team.^{thEach task starts off in the to-do column and ends up in the complete column.} editionIndividuals should not multi-task, as this causes blockages to the flow of work and is less productive. When used correctly, Kanban minimises wasted effort and keeps the team focused and organised.

The structure of the latest PMBOKYou can use an online Kanban board instead of a physical board in the office. Check out Trello or KanbanFlow if you want to use an online board.^®MoSCoW edition is segmented into four primary sections and five appendices:The

1. 1. IntroductionMoSCoW technique

      Details the changes in this edition and its alignment with the Standard for Project Management. helps teams prioritise requirements and tasks on the Kanban board. It stands for:

   2. Project performance domainsM

      This introduces the eight project performance domains, a revolutionary feature of the recent edition.ust: these requirements are critical for the current sprint/project to be a success.

   3. TailoringS

      A detailed exposition on customizing project management, governance, and processes in tune with the specific project environment.hould: these requirements are important but not necessary for delivery in the current sprint/project.

   4. Models, methods, and artifactsCo

      Gives a panoramic view of popular models, methods, and artifacts and their applicability in different performance domains.uld: these requirements are desirable but not necessary in the current sprint/project and could improve user experience or customer satisfaction for little development cost.

Appendices X1 to X5W

Highlight contributors, responsibilities of project sponsors, the role of a on’t: these are the least-critical, lowest-payback items, or not appropriate at the time.PMODuring sprint planning, the team can use MoSCoW to prioritise each task. The priority can then be assigned to each task on the Kanban board., insights on product development, and the update evolution of the Standard for Project Management.Another way to use MoSCoW is with your stakeholders in a brainstorming session. After agreeing a list of requirements with them, you can get them to decide the priority of each using MoSCoW. This helps clarify what are the most and least important requirements.

PRINCE2 Agile addressed agile concepts and iterative projects a decade ago, the treatment of agile in the PMBOK^®

practice provides mechanisms to stop the project if the justification no longer exists and provides post-project mechanisms to measure the expected benefits later.Simon Buehring

The language in the 719 Feb 2026^th edition of the PMBOKUncover the roles and activities in Scrum development post-planning. Enhance your understanding of Scrum by reading on.^® now very closely aligns itself with PRINCE2 in its discussion of products (deliverables) and outcomes. The PMBOK ^® however uses agile’s narrower concept of value whereas PRINCE2 uses the broader concept of benefits.

Project management roles

One significant limitation in earlier versions of the PMBOKHow to become a Scrum Master^® was its inadequate coverage of Simon Buehringproject management roles19 Feb 2026. The PMBOK ^{®Becoming a certified Scrum Master is straightforward. Learn about the role and its requirements by reading further.} predominantly concentrated on the project manager and project sponsor roles. This oversight remains uncorrected in the 7 ^th edition. However, the Standard for Project Management does outline several roles (or ‘functions’) associated with a project.

Those familiar with PRINCE2 recognize its comprehensive delineation of responsibilities for its nine project management team roles. While the 7 ^th edition of the PMBOK ^® introduces these ‘functions,’ it stops short of specifying their responsibilities. Yet, a detailed look suggests that these ‘functions’ align quite closely with many roles defined in PRINCE2.Agile transformation: What should ‘good’ look like (and what to be wary of)?

^{thAre Agile courses worth it?} edition, depicted the project life cycleSimon Buehring. It’s refreshing to see their exclusion in the 723 Feb 2026^th edition. This change is crucial because while these groups may align with a linear predictive (waterfall) life cycle, they are ill-suited for adaptive (agile) or hybrid life cycles.Find out if Agile courses are worth the investment and how they can fast-track your career. Scroll down for more details.

Another tiresome aspect of past PMBOK ^® editions was the redundant, detailed descriptions of the inputs, tools/techniques, and outputs (ITTOs) for each process. In comparison to the more straightforward PRINCE2 processes , PMBOK’s approach felt overly intricate. Those who’ve studied for the Project Management Professional (PMP) ^{®Lean management} exam, based on the PMBOK ^{®Simon Buehring}, can attest to the dreariness of trying to remember these ITTOs.19 Feb 2026

The departure of the process groups and processes in the 7 ^{thDelve into Lean management, a philosophy of continuous improvement and learning. Read more on how it transforms businesses.} edition was unexpected, but I, for one, am glad to bid them farewell.

Project performance domains

The 7 ^th edition introduces the concept of project performance domains. Comprising eight domains, this new concept signifies a transition from a process-driven standard to one grounded in principles.

These eight project performance domains encompass activities vital for the successful realization of project outcomes. They represent interactive and mutually dependent areas of focus that work together throughout the project to achieve its desired outcomes.

As an individual with a PRINCE2 project management background, what stands out to me about the 7 ^{thThe top 15 Agile books you should read} edition is its seeming incorporation of numerous concepts directly from PRINCE2. This similarity is especially evident in the characterization of the 8 project performance domains, with each domain closely aligning with one or more of the PRINCE2 practicesSimon Buehring.19 Feb 2026

However, the PRINCE2 business case practice doesn’t find a counterpart among the project performance domains. If the authors of this new edition had introduced a domain mirroring the PRINCE2 business case practice, the PMBOK ^{®Explore our top 15 Agile book recommendations to enhance your understanding and skills. Read on to choose your next read.} Guide might have too closely mirrored PRINCE2.

Planning performance domain

A welcome improvement in the latest edition is its departure from the assumption that every project requires a work breakdown structure (WBS). While a WBS may be typical for a predictive (waterfall) life cycle, the new edition illustrates how iterative or incremental approaches tend to prioritize high-level epics. These epics can then be broken down into features or user stories , which become items on a backlog.

Planning in these approaches often involves timeboxing strategies, such as sprints, where prioritized items are systematically pulled from a backlog. These iterative development approaches, along with concepts like epics and user stories, have their roots in the agile realm. Their integration into the PMBOKWhat is Agile?^® underscores the authors’ intent to encompass all life cycles, moving beyond just the Simon Buehringwaterfall approach19 Feb 2026.

Measurement performance domainDiscover the essentials of agile and hear from industry expert Narinder Dhaliwal. Watch the video and gain practical insights from this engaging webinar.

Another area where the latest edition of the PMBOK ^® mirrors PRINCE2 is in its adoption of the concepts of tolerance and exceptions. While these notions have been central to PRINCE2 for nearly 30 years, they’ve only been incorporated into the PMBOK

, which contains its own tailoring principle. This principle in PRINCE2 is formulated to steer clear of a rigid, one-size-fits-all or “manage by template” approach in project management.

projects 20 Old Bailey, London, EC4M 7AN, England, United Kingdom. and Knowledge Train are experts in project management, PRINCE2, agile and change management training and certification. Choose from a full range of instructor-led and self-paced project managementproject management courses at large.