Project Management Core Knowledge Areas PMBOK Aligned

Project Management – Core Knowledge Areas, PMBOK Aligned
Project Management – Knowledge Areas – PMBOK Aligned

Project Management Institute (PMI) – World’s leading professional association for the project management profession

The Project Management Institute (PMI), founded in 1969, is the world’s leading professional association for the project management profession. Headquartered in the United States, it serves millions of professionals across 208 locations through over 300 local chapters, developing industry standards and globally recognised certifications. 

Complete Overview

  • Mission: To maximize project success to elevate the world by creating products, services, and experiences that power the profession.
  • Vision: A world where every project lives up to its full potential for positive impact.
  • Core Functions:
    • Standards: Publishing the PMBOK Guide, a globally recognised standard for project management.
    • Certifications: Offering credentials such as the PMP (Project Management Professional) and CAPM.
    • Community: Managing a network of over 600,000 members and 10,000 volunteers globally.

Detailed Historical Timeline

Era 1: Foundations & The Scheduling Era (1960s – 1979)

During this period, project management emerged as a distinct discipline in the aerospace, construction, and defence industries. 

  • 1968: E.A. “Ned” Engman sends a letter of invitation to form an organization dedicated to project management.
  • 1969PMI is founded in Atlanta, Georgia, by James Snyder, Eric Jenett, Gordon Davis, E.A. Engman, and Susan Gallagher.
  • 1969: First Seminars & Symposium, “Advanced Project Management Concepts,” held in Atlanta with 83 attendees.
  • 1971: First PMI chapter established in Houston, Texas.
  • 1975: PMI releases its first set of official organizational goals.
  • 1977: Concept for PMI Seminars and Symposiums further developed by Susan Gallagher. 

Era 2: Standardization & Professionalization (1980 – 1999)

This era focused on uncertainty reduction and the formalization of global standards. 

  • 1984PMP Certification launched; co-founder Eric Jenett is the first to be certified.
  • 1987: First publication of A Guide to the Project Management Body of Knowledge (PMBOK Guide) as a white paper.
  • 1996: First formal edition of the PMBOK Guide published.
  • 1998: PMBOK recognized as an ANSI Standard

Era 3: Global Outreach & Diversification (2000 – 2018)

PMI expanded its global footprint and adapted to new methodologies. 

  • 2002CAPM Certification introduced for entry-level professionals.
  • 2007: PgMP (Program Management Professional) credential launched.
  • 2011PMI-ACP (Agile Certified Practitioner) introduced.
  • 2017PMBOK Guide 6th Edition incorporates “Agile” content. 

Era 4: Future Forward & Digital Transformation (2019 – Present) 

Focusing on strategic agility and technological advancements. 

  • 2021: PMBOK Guide 7th Edition released, shifting to principle-based frameworks.
  • 2024: Launch of PMI:Next strategy and AI-powered PMI Infinity.

Project Management Institute (PMI) – world’s leading professional association for the project management profession

Project Plan vs Project Management Plan, the Difference

Project Plan vs Project Management Plan, the Difference

Agile Backlog Refinement Activities and Business Analyst BA

Agile Backlog Refinement Activities & Business Analyst

PMBOK 6 vs PMBOK 7, what changes are there between version 6 and 7

What changes are there between PMBOK version 6 and 7

The transition from the PMBOK Guide 6th Edition to the 7th Edition represents a fundamental shift from a prescriptive, process-oriented framework to a flexible, principles-based one. While the 6th Edition focused on “how” to manage projects through specific steps, the 7th Edition focuses on “why” and “what” outcomes are being achieved. 

Key PMBOK structural changes

Major Insights into the Changes

  • From Processes to Principles: PMBOK 7 replaces the 49 prescriptive processes with 12 Project Management Principles (e.g., Stewardship, Team, Stakeholders, Value, Tailoring) that serve as foundational guidelines for behavior and decision-making in any environment.
  • Performance Domains: The 10 Knowledge Areas are replaced by 8 Performance Domains (Stakeholders, Team, Development Approach, Planning, Project Work, Delivery, Measurement, and Uncertainty). These domains focus on critical activity groups for delivering outcomes rather than step-by-step tasks.
  • Value Delivery System: The 7th Edition introduces a “system for value delivery,” shifting focus from just managing project deliverables to how projects contribute to an organization’s overall strategy and business goals.
  • Tailoring: While always part of project management, tailoring is now a core principle and has its own dedicated chapter in PMBOK 7. It encourages project managers to adapt their approach based on the specific project context, complexity, and organizational needs.
  • Agile and Hybrid Integration: PMBOK 7 fully integrates agile and hybrid practices into the core text, whereas PMBOK 6 largely treated them as an appendix or a separate guide.
  • Models, Methods, and Artifacts: The rigid ITTO structure of PMBOK 6 is replaced by a broader section on Models, Methods, and Artifacts. This provides a high-level grouping of tools without prescribing exactly when or how they must be used. 

PMP Exam Context

PMBOK 7 does not make PMBOK 6 obsolete. For the Project Management Professional (PMP) exam, both editions remain relevant reference materials. PMBOK 6 provides the technical workflow “checklist,” while PMBOK 7 provides the “mindset” and measurement strategies for modern, complex projects. 

Project Management Methodologies Summarised

Project Management Methodologies Summarised

Types of Product Managers Overview

Types of Product Managers Overview

Project Management Methodologies, historical timeline by era and year

This is a detailed, comprehensive historical timeline of project management methodologies, tracing the evolution from ancient practices to modern adaptive frameworks.

I. Pre-Modern Era (Before 1900): Foundation of Task Coordination

  • 2570 BC (Great Pyramid of Giza): Completion of the pyramids, demonstrating early project organization with managers for each of the four faces, planning, and logistics.
  • 208 BC (Great Wall of China): Construction of the Great Wall, involving massive workforce organization divided into soldiers, citizens, and criminals.
  • 1850s (Transcontinental Railroad): US railroad projects requiring large-scale resource and schedule management.
  • 1896 (Harmonogram): Karol Adamiecki developed the harmonogram, a predecessor to the Gantt chart (published in 1931). 

II. Early Modern Era (1910s–1950s): The Scientific Management Era 

This era brought “scientific management” to project control, focusing on efficiency and visualization. 

  • 1910s (Gantt Chart): Henry Gantt developed the Gantt chart, a visual tool for scheduling tasks over time.
  • 1911 (Scientific Management): Frederick Taylor published The Principles of Scientific Management, focusing on efficiency and time-saving.
  • 1931–1936 (Hoover Dam): One of the first large-scale applications of Gantt charts for complex scheduling.
  • 1942–1945 (Manhattan Project): Development of the atomic bomb, creating a need for rapid, complex planning and large-scale team coordination. 

III. The “Golden Age” of Project Management (1950s–1960s): Formal Methodologies 

This era introduced mathematical models for managing complex, interdependent tasks. 

  • 1956 (AACE Formed): The American Association of Cost Engineers (now AACE International) was formed, specializing in cost control and scheduling.
  • 1957 (Critical Path Method – CPM): Developed by Dupont Corporation to manage chemical plant maintenance shutdowns.
  • 1958 (Program Evaluation and Review Technique – PERT): Created by the US Navy Special Projects Office for the Polaris missile submarine project to manage task time and risk.
  • 1962 (Work Breakdown Structure – WBS): The US Department of Defense mandated the use of WBS for large, complex projects.
  • 1965 (IPMA Founded): The International Project Management Association (IPMA) was launched, the world’s first project management association.
  • 1969 (PMI Founded): The Project Management Institute (PMI) was launched to promote the profession, later developing the PMP certification. 

IV. The “Silver Age” (1970s–1980s): Systems and Controls 

  • 1970s (Waterfall Introduction): While used informally earlier, the Waterfall methodology was formalized for software development in the 1970s, emphasizing sequential phases.
  • 1975 (PROMPTII): Simpact Systems Ltd created PROMPTII, a methodology to handle cost overruns in computer projects, which later formed the basis of PRINCE.
  • 1975 (Mythical Man-Month): Fred Brooks published his seminal work on software engineering project management.
  • 1978 (Toyota Production System): Lean production and Kanban techniques, used in manufacturing, began to influence project workflow.
  • 1984 (Theory of Constraints – TOC): Dr. Eliyahu Goldratt published The Goal, introducing the Theory of Constraints for managing constraints (bottlenecks).
  • 1986 (Scrum): Takeuchi and Nonaka defined Scrum as a project management style for fast-paced development.
  • 1987 (PMBOK Guide): The Project Management Institute published the first Project Management Body of Knowledge (PMBOK) white paper.
  • 1989 (PRINCE): The UK government launched PRojects IN Controlled Environments (PRINCE), the standard for information systems projects. 

V. Rebirth and Modern Era (1990s–2000s): Agile and Adaptive Methods 

  • 1994 (CHAOS Report): The Standish Group published the first report documenting high IT project failure rates.
  • 1995 (Scrum Formalization): Jeff Sutherland and Ken Schwaber formally defined the Scrum framework.
  • 1996 (PRINCE2): PRINCE was updated to PRINCE2 to become a generic, more flexible methodology applicable to all project types.
  • 1997 (Critical Chain Project Management – CCPM): Eliyahu Goldratt invented CCPM, based on the Theory of Constraints.
  • 1998 (PMBOK Standard): The American National Standards Institute (ANSI) recognized PMBOK as a standard.
  • 2001 (Agile Manifesto): 17 software developers met to publish the Manifesto for Agile Software Development, prioritizing collaboration and adaptability over rigid plans.
  • 2007 (Kanban for Software): David Anderson adopted Kanban for software development, focusing on visualizing work and limiting work-in-progress. 

VI. The Contemporary Era (2010s–Present): Hybrid, AI, and Speed 

  • 2012 (ISO 21500): The International Organization for Standardization published ISO 21500:2012, “Guidance on Project Management”.
  • 2017 (PMBOK 6th Ed & PRINCE2 Update): PMI introduced Agile/adaptive practices into PMBOK, while AXELOS released a more flexible PRINCE2.
  • 2018 (PRINCE2 Agile): PRINCE2 Agile was launched to combine the governance of PRINCE2 with the flexibility of Agile.
  • 2021 (PMBOK 7th Ed): A major shift in PMI standards, moving from process-based to principle-based, focusing on project outcomes.
  • 2020s–Present (AI/Hybrid): Rise of AI-driven project management, automated reporting, and hybrid methodologies combining Waterfall stability with Agile speed. 

Project Management Methodologies, historical timeline by era and year

PMBOK Project Management Body of Knowledge summary and detailed historical timeline by era and year

The PMBOK (Project Management Body of Knowledge) Guide, published by the Project Management Institute (PMI), is the globally recognized standard for project management best practices. Its evolution reflects the shift from rigid, industrial-era scheduling to flexible, value-driven, and hybrid methodologies. 

Summary of PMBOK Evolution

  • 1980s (Origins): PMI sought to standardize knowledge, starting with a white paper in 1983 and the first “Body of Knowledge” document in 1987.
  • 1996 (1st Edition): The first official PMBOK Guide was published, introducing a foundational process framework.
  • 2000s (Expansion): The 2nd (2000) and 3rd (2004) editions expanded on integration and finalized the standard for project management.
  • 2010s (Integration): The 4th (2008) and 5th (2012) editions added stakeholder management and aligned with enterprise needs. The 6th Edition (2017) formally bridged predictive (waterfall) and agile practices.
  • 2020s (Transformation): The 7th Edition (2021) marked a massive shift from process-based to principle-based, focusing on project outcomes rather than just outputs. The 8th Edition (2025) reintroduces practical, tailored process guidance alongside principles. 

Detailed Historical Timeline by Era and Year

Ancient Era to Pre-Modern (Before 1950s)

  • 2570 BC: Completion of the Great Pyramid of Giza, requiring complex organization, planning, and control.
  • 208 BC: Construction of the Great Wall of China, demonstrating massive, orchestrated labour management.
  • 1917: Henry Gantt developed the Gantt chart, a foundational scheduling tool still used today.

The Foundation Era (1950s – 1960s) 

  • 1956: American Association of Cost Engineers (now AACE International) formed.
  • 1957: Critical Path Method (CPM) invented by Dupont.
  • 1958: Program Evaluation and Review Technique (PERT) developed by the U.S. Navy for the Polaris missile program.
  • 1962: U.S. Dept of Defense mandated the Work Breakdown Structure (WBS) approach.
  • 1969: Project Management Institute (PMI) founded to promote the profession and set standards. 

The Formalization Era (1970s – 1980s) 

  • 1975: PROMPTII method created (later becoming PRINCE).
  • 1984: Dr. Eliyahu M. Goldratt introduced the Theory of Constraints (TOC) in his book “The Goal”.
  • 1986: Scrum named as a project management style.
  • 1987: First PMBOK Guide published by PMI as a white paper, attempting to standardize practices. 

The Standardization Era (1990s – 2000s)

  • 1991: Navy A-12 Avenger II Program cancelled due to poor performance detected by EVM.
  • 1996: 1st Edition of the PMBOK Guide released, establishing it as the foundational standard.
  • 1997: Critical Chain Project Management (CCPM) invented.
  • 1998: PMBOK recognized as a standard by ANSI (American National Standards Institute) and IEEE.
  • 2000: 2nd Edition of the PMBOK Guide released, adding more practical, in-depth material.
  • 2001: Agile Manifesto written, focusing on adaptability in software development.
  • 2004: 3rd Edition of the PMBOK Guide released, changing focus from “generally accepted” to “good practice”. 

The Modern Age & Agility Era (2010s – Present)

  • 2008: 4th Edition of the PMBOK Guide released, improving consistency and introducing new processes.
  • 2012: 5th Edition of the PMBOK Guide released, introducing the 10th Knowledge Area: Project Stakeholder Management.
  • 2017: 6th Edition of the PMBOK Guide released, incorporating Agile, Iterative, and Adaptive methodologies into every knowledge area.
  • 2021: 7th Edition of the PMBOK Guide released, a major shift towards a principle-based, value-delivery approach.
  • 2025: 8th Edition of the PMBOK Guide released, reintroducing tailored, practical processes along with principles.

PMBOK Project Management Body of Knowledge summary and detailed historical timeline by era and year

Free Upgrade Project Management Templates Download by focus area

Mark Whitfield provides a comprehensive suite of over 200 editable project management templates designed for both Agile and Waterfall delivery. These tools are built based on 21+ years of IT project delivery experience and are formatted for Microsoft Office (Excel, Word, PowerPoint) and Microsoft Project (MPP).

 

Core Planning & Tracking Templates

  • Detailed Project Plans: Comprehensive MPP and Excel files covering the full Software Development Life-cycle (SDLC), including Waterfall and Agile Scrum sprints.
  • Plan on a Page (POaP): High-level visual summaries in PowerPoint or Excel for client reporting and executive snapshots.
  • RAID Log: A central tracker for Risks, Actions, Issues, and Dependencies, often including tabs for Decisions, Opportunities, and Lessons Learned.
  • RACI Matrix: A tracker to define roles and responsibilities (Responsible, Accountable, Consulted, Informed). 

Financial & Resource Management

  • Project Finance Tracker: Tools for managing project budgets, including forecasts vs. actuals, margin analysis, and variation tracking.
  • Resource Planning: Grid templates for costing project resources per phase and tracking team allocations.
  • Benefits Realisation: A spreadsheet to compare initial project goals against actual business outcomes and costs. 

Reporting & Communication

  • Status Reports: Weekly and monthly templates in Word and PowerPoint that include milestone dashboards, project health indicators, and “next steps”.
  • Organisation Charts: Templates for visualising the project hierarchy and stakeholder contacts.
  • Agile Dashboards: Excel-based Burn Down and Burn Up charts for teams that do not have access to tools like Jira. 

Methodology Support

  • PRINCE2 7th Edition: Specific MPP and Excel templates aligned with the latest PRINCE2 standards.
  • Agile Frameworks: Templates for Sprint Planning, Daily Stand-ups, and Sprint Retrospectives. 

These templates are available for purchase on Mark Whitfield’s official site and typically include free lifetime upgrades. 

Free Upgrade Project Management Templates Download by focus area

Editable Project Management Templates for Agile and Waterfall projects

Mark Whitfield’s project management (PM) template collection is a comprehensive professional toolkit containing over 200 editable templates. Designed for both Agile Scrum and PRINCE2/Waterfall delivery, the set is built on over 24 years of real-world experience and is available for purchase on his official website and Etsy

Core Planning & Tracking Templates

  • Detailed Project Plans: Comprehensive Microsoft Project (MPP) and Excel plans mapped to the Software Development Life Cycle (SDLC).
  • Plan on a Page (POaP): High-level visual summaries for client presentations, provided in both Excel and PowerPoint.
  • RAID Log: A robust Excel tracker managing Risks, Assumptions, Issues, and Dependencies, often including tabs for Change Requests and Lessons Learned.
  • Financial Trackers: Detailed spreadsheets for tracking project forecasts, actuals, variance, and resource costing.
  • RACI Matrix: Essential for defining roles (Responsible, Accountable, Consulted, Informed) within the project team. 

Methodology-Specific Artifacts

  • Agile Scrum: Includes burn-down and burn-up charts, sprint planning logs, and templates for daily stand-ups and retrospectives.
  • PRINCE2/Waterfall: Tailored plans for 7th Edition standards, including project mandates, transition plans, and close-out checklists. 

Reporting & Documentation

  • Status Reports: Weekly and monthly templates in Word and PowerPoint to communicate project health to stakeholders.
  • Walkthrough Guides: The ZIP package includes Microsoft Word documents explaining how to use and customise each major template.
  • Additional Tools: Benefits realisation plans, resource trackers, project organisation charts, and dependency logs. 

Key Features

  • Format: Primarily Microsoft Office (Excel, Word, PowerPoint, Project) for compatibility across desktop and mobile.
  • Lifetime Value: A one-time purchase typically includes FREE upgrades for life; users can re-contact the author for updated versions of the toolkit.
  • Customisability: All files are fully editable to suit specific project or organizational needs.

Editable Project Management Templates for Agile and Waterfall projects

Building a Product on Paper and in Reality

Building a Product on Paper and in Reality

Project Management LinkedIn Group

Project Management LinkedIn Group

https://www.linkedin.com/groups/163300

Project Management Café, PRINCE2 Agile SCRUM Kanban MPP MSP Templates ITIL LEAN DevOps PMP Six Sigma

This is a Project Management Group Café for PM students, graduates and professionals looking to either locate, discuss or contribute ideas for PM templates for; Agile, Scrum, Kanban, PRINCE2 Waterfall projects, e.g. Plan on a Page (POaP), RACI, MPP, RAID logs, finance trackers, status reports, org charts etc. etc.

Project Management LinkedIn Group

Project Management Plan Components, PMBOK

Project Management Plan Components, PMBOK