Project Management evolution timeline by era

The history of project management has evolved from ancient manual coordination to highly sophisticated, digital-first methodologies

Pre-20th Century: The Era of Ancient Marvels

During this era, project management was characterized by massive labour forces and basic resource coordination without standardized scheduling tools. 

  • 2570 BC: Completion of the Great Pyramid of Giza. Documentation shows managers were assigned to each of the four faces to oversee progress.
  • 208 BC: Construction of the Great Wall of China. Labour was systematically organized into groups of soldiers, civilians, and criminals.
  • 1850s: Construction of the Pacific Railroad. This is often cited as one of the first large-scale industrial project management undertakings in the U.S.. 

1900–1950: The Birth of Modern Project Management 

This era introduced scientific management principles and the first visual scheduling tools. 

  • 1911Frederick Taylor publishes The Principles of Scientific Management, focusing on efficiency and unskilled labour training.
  • 1917Henry Gantt develops the Gantt Chart, a radical tool for visualising schedules that remains a global standard today.
  • 1931–1936: Construction of the Hoover Dam. This project was a major early adopter of Gantt’s scheduling techniques.
  • 1942–1945The Manhattan Project. This complex R&D effort pioneered the use of large-scale task coordination and resource management. 

1950–1980: The Era of Management Science 

Driven by the Cold War and space race, this period saw the creation of mathematical scheduling techniques. 

  • 1956: AACE International is formed, focusing on cost engineering.
  • 1957–1958: Development of Critical Path Method (CPM) by DuPont and Program Evaluation and Review Technique (PERT) by the U.S. Navy.
  • 1962–1975: Introduction of Work Breakdown Structure (WBS) by the DoD, founding of IPMA and PMI, and development of PROMPT (later PRINCE). 

1980–2000: The Computing Revolution 

Personal computers allowed project management software to proliferate into the private sector. Key milestones included the early Scrum framework and the initial PMBOK Guide release. 

  • 1989–1997: Widespread adoption of Earned Value Management (EVM), release of PRINCE2, and development of Critical Chain Project Management (CCPM)

2000–Present: The Agile and Digital Era 

Modern project management emphasizes flexibility, speed, and digital tools. 

  • 2001: The Agile Manifesto is published.
  • 2012–2021: Release of ISO 21500, major updates to PRINCE2 and PMBOK to integrate Agile, and the shift to performance-based standards in PMBOK 7th Ed.

Project Management evolution timeline by era

Project management has evolved from ancient engineering feats to a highly structured, data-driven discipline. Below is a comprehensive timeline of its historical development and the evolution of its core methodologies. 

Ancient & Early Eras

  • 2570 BC: The Great Pyramid of Giza – Completed with record-keeping and oversight for each of the four faces, demonstrating early forms of planning and control.
  • 208 BC: The Great Wall of China – Built with a massive labour force organised into specific groups: soldiers, ordinary people, and criminals.
  • 1917: Gantt Chart – Developed by Henry Gantt, this scheduling diagram became a radical innovation for tracking project tasks chronologically. 

The Mid-20th Century: Formalization

  • 1956: AACE International Formed – Early practitioners of cost engineering and scheduling founded what is now the leading society for project control specialists.
  • 1957: Critical Path Method (CPM) – Invented by DuPont to address chemical plant maintenance; it saved the company $1 million in its first year.
  • 1958: PERT (Program Evaluation Review Technique) – Developed for the U.S. Navy’s Polaris project to analyse the minimum time needed for task completion.
  • 1962: Work Breakdown Structure (WBS) – Mandated by the U.S. Department of Defense as a hierarchical tree structure for project deliverables.
  • 1965: IPMA Founded – The world’s first project management association was started in Vienna as a global forum for networking.
  • 1969: Project Management Institute (PMI) Launched – Founded to advance the profession, PMI has since become the primary publisher of global standards. 

Late 20th Century: Methodology Proliferation 

  • 1975: PROMPTII & “The Mythical Man-Month” – Guidelines were created for computer projects, while Fred Brooks’s Brooks’s law observed that adding manpower to late software projects makes them later.
  • 1984: Theory of Constraints (TOC) – Introduced by Dr. Eliyahu M. Goldratt, focusing on identifying system bottlenecks.
  • 1986: Scrum – First named as a project management style for software development in a Harvard Business Review paper.
  • 1987: PMBOK Guide First Published – PMI published the first “A Guide to the Project Management Body of Knowledge” as a white paper to standardise practices.
  • 1989: PRINCE & Earned Value Management – The PRINCE method was developed for UK government IT projects; meanwhile, Earned Value Management (EVM) became an essential part of procurement.
  • 1996: PRINCE2 – A more generic revision of PRINCE was published, applicable to any project type.
  • 1997: Critical Chain Project Management (CCPM) – Invented to keep resources levelly loaded and flexible. 

21st Century: Agile & Global Standards

  • 2001: The Agile Manifesto – Written by 17 developers in Utah, codifying the principles of lightweight, iterative software development.
  • 2006: Total Cost Management Framework – Released by AACE International as the first integrated process for portfolio and project management.
  • 2012: ISO 21500:2012 – The International Organisation for Standardisation released its global guidance on project management.
  • 2017: PMBOK 6th Edition & PRINCE2 Update – Updates reflected the integration of Agile practices into traditional project settings.
  • 2021: PMBOK 7th Edition – Shifted toward a principle-based approach to help practitioners be more proactive and innovative.

Project Management Mistakes and How to Avoid

Project Management Mistakes and How to Avoid

Is Microsoft MS Project Desktop (offline) app being retired?

No, Microsoft Project desktop is not being retired. It remains the “gold standard” for complex project scheduling and will continue to be supported and available for purchase. 

MS Project Templates can be downloaded in the template bundle, click on link at banner above

Confusion often arises because Microsoft has announced the retirement of several related cloud-based and web-based services. Here is the current status of the Microsoft Project ecosystem: 

Products Being Retired

  • Project Online: This service will officially retire on September 30, 2026. After this date, Project Online environments and data will no longer be accessible.
  • Project for the Web: Retired as a standalone brand and was fully merged into the new Microsoft Planner in 2024/2025.
  • Project/Roadmap Apps in Teams: These were retired in August 2025 and replaced by the unified Planner experience. 

Products Staying Active

  • Project Desktop (Project Professional/Standard): Not impacted by the cloud service retirements. You can still use it to manage .mpp files locally or connect it to alternative backend systems like Project Server SE.
  • Project Server Subscription Edition (SE): This on-premises/self-hosted version will remain supported through at least 2031. It is the recommended migration path for organizations that want to keep the “Project Web App” (PWA) interface without using the retired Project Online cloud service.
  • Microsoft Planner: Now serves as the primary cloud-based project management tool, absorbing the features of Project for the Web. 
MS Project Templates can be downloaded in the template bundle, click on link at banner above

Key Dates for Project Online Users:

  • October 1, 2025: End of sale for new Project Online subscriptions.
  • April 2, 2026: SharePoint 2013 workflows (which many Project Online users rely on) will be retired.
  • September 30, 2026: Full shutdown of Project Online.

Agile Scrum Evolution Timeline Overview

Agile and Scrum have evolved from specific product development theories into a global standard for project management. While Scrum predates the Agile Manifesto by several years, it has become the most widely adopted framework within the Agile umbrella. 

Agile Scrum Burn down and Burn up charts – can be downloaded from website banner

Evolution Timeline

  • 1986: The Inspiration. Hirotaka Takeuchi and Ikujiro Nonaka publish “The New New Product Development Game” in Harvard Business Review, introducing the “rugby” approach to product development.
  • 1993: The First Scrum. Jeff Sutherland and his team at Easel Corporation implement the first official Scrum.
  • 1995: Public Presentation. Ken Schwaber and Jeff Sutherland formally present Scrum at the OOPSLA ’95 conference, introducing the concept of Sprints.
  • 2001: The Agile Manifesto. 17 software developers meet in Utah to sign the Manifesto for Agile Software Development, codifying the 4 values and 12 principles that define Agile.
  • 2002: Scrum Alliance Founded. The Scrum Alliance is established by Ken Schwaber, Mike Cohn, and Esther Derby to provide training and certifications like the Certified ScrumMaster (CSM).
  • 2009: Founding of Scrum.org. Ken Schwaber founds Scrum.org to provide a more consistent approach to Scrum training and assessments.
  • 2010: The First Scrum Guide. Sutherland and Schwaber publish the first Official Scrum Guide, providing a definitive, minimal definition of the framework.
  • 2011–2017: Iterative Refinements. Updates to the Scrum Guide clarify the Daily Scrum purpose (2013) and emphasize Scrum Values (2016).
  • 2020: The “Simplified” Guide. The latest 2020 Scrum Guide is released, focusing on making the framework less prescriptive and more applicable to non-software industries by removing technical jargon. 

Key Shifts in Scrum Maturity

  • Prescriptive to Descriptive: Early Scrum was highly prescriptive about meetings and roles; modern Scrum focuses on Empiricism (Transparency, Inspection, Adaptation).
  • Team Autonomy: The 2013 update pivoted from “selecting tasks” to focusing on the Sprint Goal, empowering teams to decide how to achieve the objective.
  • Scaling Frameworks: As organizations grew, frameworks like SAFe (2011) and LeSS (2013) emerged to apply Scrum across hundreds of teams.
Plan On a Page POaP for an Agile Scrum project, available for download above

Agile Development History Timeline Overview

Agile’s history is a transition from rigid, manufacturing-based “Waterfall” models to flexible, people-centric frameworks. While the term was coined in 2001, its roots trace back to early 20th-century industrial practices and the “software crisis” of the 1960s. 

Early Foundations (Pre-1990s)

Before Agile became a formal software methodology, its core principles of efficiency and iteration emerged from manufacturing and early computing.

  • 1896: Sakichi Toyota introduced the “Stop and Notify” concept (Jidoka), a foundational Lean/Agile practice for immediate problem-solving.
  • 1948: The Toyota Production System (TPS) established Lean manufacturing and the Kanban system to manage workflow.
  • 1957: IBM began using incremental development on large software projects.
  • 1970: Winston Royce published “Managing the Development of Large Software Systems,” which formalized the Waterfall Model but actually cautioned against its rigidity.
  • 1986: Takeuchi and Nonaka published The New New Product Development Game, introducing the “rugby” metaphor for team-based development that inspired Scrum

The Rise of “Lightweight” Methods (1990–2000) 

Frustrated by Waterfall’s slow delivery, practitioners developed several “lightweight” frameworks. 

  • 1991: Rapid Application Development (RAD) popularized timeboxing and iterations.
  • 1993: Jeff Sutherland and his team first implemented Scrum at Easel Corporation.
  • 1994: The Dynamic Systems Development Method (DSDM) was created as a vendor-independent RAD framework.
  • 1995: Ken Schwaber and Jeff Sutherland formally co-presented Scrum at the OOPSLA conference.
  • 1996: Kent Beck introduced Extreme Programming (XP), emphasizing practices like pair programming and continuous testing.
  • 1997: Feature-Driven Development (FDD) and Crystal Clear emerged as alternative iterative models. 

Formalisation & Modern Evolution (2001–Present)

The movement unified under a single name and eventually scaled to entire enterprises. 

  • 2001: 17 software leaders met at Snowbird, Utah, to draft the Agile Manifesto, establishing four core values and 12 principles.
  • 2003: The book Lean Software Development by Mary and Tom Poppendieck officially bridged Lean manufacturing and software agility.
  • 2009: The concept of DevOps emerged, extending Agile principles into IT operations and deployment.
  • 2011: The Scaled Agile Framework (SAFe) was introduced to help large organizations manage multiple Agile teams.
  • 2012–2015: Agile surpassed the 50% mark in global adoption, becoming the industry standard for development.
  • 2020s: Agile principles are now widely applied outside of tech, in fields like marketing, education, and HR

Agile’s evolution is not just a 21st-century phenomenon but a response to decades of “software crises” and rigid industrial processes. Below is a comprehensive historical breakdown of Agile’s journey. 

1. Pre-Digital Foundations (1910s – 1940s)

Long before software, the concepts of efficiency and waste reduction were born in manufacturing. 

  • 1911: Scientific Management. Frederick Taylor encouraged managers to adopt worker suggestions for efficiency, opposing rigid habits.
  • 1940s: Lean Manufacturing (Toyota). Toyota pioneered the “Just-in-Time” method and Kaizen (continuous improvement) after observing American supermarkets.
  • 1948: Toyota Production System. Introduction of Kanban for visual workflow management. 

2. Early Iterative Development (1950s – 1970s)

The 1950s saw the first departures from strictly sequential “waterfall” planning. 

  • 1957: Incremental Development. IBM and Motorola teams, including Gerald Weinberg, used iterative methods indistinguishable from modern Extreme Programming (XP) for Project Mercury.
  • 1968: NATO Software Engineering Conference. Formally identified the “Software Crisis” (projects being late and over budget), sparking a search for better methodologies.
  • 1970: Waterfall Formalised (and Critiqued). Winston Royce described the Waterfall model but notably advocated for iterative releases to reduce risk. 

3. The Proliferation of “Lightweight” Methods (1980s – 1990s) 

Frustration with heavyweight, document-heavy processes led to several “Agile” precursors. 

  • 1986: “The New New Product Development Game.” Takeuchi and Nonaka published this HBR article, introducing the “Rugby” approach (teamwork over relay-race handoffs), which directly inspired Scrum.
  • 1991: Rapid Application Development (RAD). James Martin introduced RAD, emphasising fast prototyping and client feedback.
  • 1993–1995: The Birth of Scrum. Jeff Sutherland and Ken Schwaber formalised Scrum, presenting it at the OOPSLA ’95 conference.
  • 1996: Extreme Programming (XP). Kent Beck introduced XP at Chrysler, focusing on technical excellence through practices like Pair Programming and Test-Driven Development

4. The Agile Manifesto & Formalisation (2001 – 2010)

Agile moved from a collection of “lightweight” methods to a global standard. 

  • 2001: The Agile Manifesto. 17 developers met in Snowbird, Utah, to draft the Manifesto for Agile Software Development, establishing four core values and 12 principles.
  • 2003: Lean Software Development. Mary and Tom Poppendieck adapted Toyota’s Lean principles specifically for software engineering.
  • 2009: Software Craftsmanship. The Software Craftsmanship Manifesto emerged to refocus the community on the quality of the “craft” rather than just project management.
  • 2010: The First Scrum Guide. Published as the definitive resource on Scrum framework rules. 

5. Scaling and Modern Business Agility (2011 – Present) 

Agile expanded beyond coding into enterprise-wide strategy. 

  • 2011: Scaled Agile Framework (SAFe). Dean Leffingwell launched SAFe to help large corporations apply Agile at scale.
  • 2015–2017: Project Management Integration. Major bodies like AXELOS released PRINCE2 Agile, and the PMI introduced the Agile Certified Practitioner (ACP).
  • 2020s: Beyond Software. Agile principles are now standard in marketing, HR, and hardware development through concepts like Business Agility

Putting Together a Project Plan Overview

Putting Together a Project Plan Overview

Microsoft PowerPoint Development Timeline History

Microsoft PowerPoint was originally developed as “Presenter” by Forethought, Inc. in 1987 for the Apple Macintosh. Microsoft acquired it just three months later for $14 million, marking their first major acquisition. 

MS PowerPoint Plan On a Page POaP templates downloaded at website banner

Foundational Years (1984–1990) 

  • 1984: The idea for a presentation program is conceived by Robert Gaskins.
  • 1987 (April): PowerPoint 1.0 launches for Macintosh, supporting only black and white slides.
  • 1987 (July): Microsoft acquires Forethought.
  • 1990 (May): The first Windows version (PowerPoint 2.0) is released, coinciding with Windows 3.0. 

Office Integration (1992–2003) 

MS PowerPoint Plan On a Page POaP templates downloaded at website banner
  • 1992: PowerPoint 3.0 introduces video transitions and sound.
  • 1994: PowerPoint 4.0 begins deep integration with the Microsoft Office suite, sharing interface components with Word and Excel.
  • 1997: PowerPoint 97 brings significant upgrades like “Custom Animation” and the “Office Assistant” (Clippy).
  • 2003: PowerPoint 2003 focuses on collaboration and improved “Package for CD” features. 

Modernization & Cloud (2007–Present)

MS PowerPoint Plan On a Page POaP templates downloaded at website banner
  • 2007: Introduces the Ribbon interface and the XML-based .pptx file format.
  • 2010: Adds video export, section organization, and co-authoring capabilities.
  • 2013: PowerPoint for Web is released, alongside the first dedicated mobile apps for iOS and Android.
  • 2016–2021: Features focus on AI-driven design (PowerPoint Designer), Morph transitions, and real-time collaboration via Microsoft 365.
  • 2023+: Integration of AI tools like Copilot for automated slide generation and DALL-E 2 for image creation. 

Microsoft PowerPoint Development Timeline History

MS PowerPoint Plan On a Page POaP templates downloaded at website banner

Microsoft Excel Development Timeline History

Microsoft Excel has evolved from a niche Apple Macintosh tool into the world’s most dominant spreadsheet software. Its history is marked by strategic shifts, such as jumping from the MS-DOS era to graphical interfaces to outmanoeuvre then-leader Lotus 1-2-3

Timeline of Major Excel Milestones

Agile Templates available at download link at website banner
  • 1982: Multiplan (The Predecessor) – Microsoft’s first spreadsheet program. While popular on CP/M systems, it struggled against Lotus 1-2-3 on MS-DOS.
  • 1985: Excel 1.0 (Macintosh Exclusive) – Realising they couldn’t beat Lotus on DOS, Microsoft built a graphical spreadsheet for the new Mac. It introduced the ability to adjust cell heights, widths, and fonts.
  • 1987: Excel 2.0 (First Windows Version) – Launched alongside the first Windows environments, it introduced color support (like red for negative numbers) and was significantly faster than competitors.
  • 1990: Excel 3.0 – Added 3D charts, toolbars, and drawing tools, helping Excel finally overtake Lotus 1-2-3 as the market leader.
  • 1993: Excel 5.0 – A major turning point that introduced Visual Basic for Applications (VBA), allowing users to automate tasks with macros.
  • 1997: Excel 8.0 (Office 97) – Introduced the Paperclip Assistant (“Clippy”) and the first version of the modern VBA environment.
  • 2007: Excel 12.0 (The Ribbon Era) – Replaced menus with the Ribbon interface and dramatically increased grid capacity to 1,048,576 rows by 16,384 columns.
  • 2010: Excel 14.0 – Introduced Slicers for PivotTables and Sparklines (mini charts inside cells).
  • 2013-2016: Data Intelligence – Added Power Query, Power Pivot, and new chart types like Waterfall, Pareto, and Treemap to support advanced data modeling.
  • 2019-Present: AI & Cloud Integration – Modern versions focus on seamless collaboration, dynamic arrays (like XLOOKUP), and AI-powered insights that can extract data directly from images. 

Technological Evolution Highlights

MS Excel templates available on bundle download at website banner
  • Architecture: Shifted from 16-bit to 32-bit with Excel 95, greatly improving stability.
  • Collaborative Features: Modern Version History and “Show Changes” now allow teams to track every edit in real-time.
  • Visualisation: Excel now supports complex timelines via SmartArt or custom Scatter charts with error bars for professional project tracking.

Microsoft Excel Development Timeline History

Microsoft Excel templates available at banner above, FREE upgrades

Project Management Templates Bundle FREE Upgrades

Mark Whitfield’s project management templates offer a range of timeline and planning views designed for Agile, Waterfall, and PRINCE2 delivery. These templates typically include a high-level Plan on a Page (POaP) and detailed Microsoft Project (MPP) or Excel schedules. 

Example Plan on a Page POaP

Timeline & Planning Views

  • Plan on a Page (POaP): A high-level summary view (often in PowerPoint or Excel) used to communicate key phases and milestones to stakeholders without the clutter of a full Gantt chart.
  • Detailed Gantt Charts: Provided in both Microsoft Project (MPP) and Excel, these timelines include task dependencies, resource allocations, and critical path tracking.
  • Agile Sprint Timelines: Specialized views for tracking 2–4 week sprints, daily stand-ups, and sprint retrospectives within a broader project framework.
  • SDLC Progression: The templates are often structured around a typical Software Development Life-cycle (SDLC), moving from Inception to Transition and Early Live Support (ELS). 

Key Timeline Components

The templates are pre-configured with several essential timeline elements: 

  1. Project Start & End Dates: Easily adjustable fields that automatically update durations and downstream tasks.
  2. Milestones & Gateways: Visual markers for critical sign-off points and delivery stages.
  3. Task Dependencies: Pre-built links that show how delays in one area (e.g., hardware delivery) impact the overall project finish date.
  4. Resource View: Timelines integrated with resource calendars to account for holidays and leave. 

You can find the full package of over 200 editable templates, which include these timeline views and RAID logs, on Mark Whitfield’s official website or via his Etsy store

Project Management Templates Bundle FREE Upgrades

PRINCE2 – PRojects IN Controlled Environments – Timeline

PRINCE2 (PRojects IN Controlled Environments) has evolved from a rigid, IT-specific framework into a globally recognised, flexible project management standard. 

Historical Evolution Timeline

  • 1975: PROMPT Origins – Simpact Systems Ltd developed PROMPT (Project Resource Organisation Management and Planning Techniques) to address IT project overruns.
  • 1989: The Birth of PRINCE – The UK’s Central Computer and Telecommunications Agency (CCTA) licensed PROMPT, renaming it PRINCE (originally “PROMPT II IN the CCTA Environment”).
  • 1996: PRINCE2 Launch – Developed with input from 150 European organisations, PRINCE2 was released as a generic, scalable framework suitable for any industry.
  • 2000–2013: Ownership Shifts – Ownership moved from the CCTA to the Office of Government Commerce (OGC) in 2000, then to AXELOS Ltd (a joint venture) in 2013.
  • 2009: Major “Refresh” – Introduced the seven core principles and made the method more customisable.
  • 2017: 6th Edition Update – Formerly known as the “2017 Update,” this version focused heavily on scalability and tailoring to specific project needs.
  • 2021–Present: PeopleCert Era – PeopleCert acquired AXELOS in 2021. In 2023, PRINCE2 7 was launched, introducing a greater emphasis on people management and sustainability. 

Comprehensive Project Timeline Breakdown

A standard PRINCE2 project follows a lifecycle defined by seven processes

  1. Pre-Project: Starting up a Project (SU)
    • Ensures the project is viable and worthwhile.
    • Key Output: Project Brief.
  2. Initiation: Initiating a Project (IP)
  3. High-Level Oversight: Directing a Project (DP)
    • An ongoing process where the Project Board provides guidance and makes key decisions without managing day-to-day tasks.
  4. Day-to-Day Management: Controlling a Stage (CS)
    • The Project Manager monitors work, manages risks, and reports progress for each individual stage.
  5. Technical Delivery: Managing Product Delivery (MP)
    • The Team Manager ensures products (deliverables) are created, tested, and handed over according to specifications.
  6. Transition: Managing a Stage Boundary (SB)
  7. Finalisation: Closing a Project (CP)
    • The formal decommissioning of the project, ensuring all products are accepted and lessons are documented. 

PRINCE2 – PRojects IN Controlled Environments

Mark Whitfield IT Career Timeline, AI generated from Google

The technical timeline for 

Mark Whitfield, an SC cleared, Senior IT Project Manager and Engagement Manager, spans over 30 years and transitions from specialized banking software development to high-level project leadership and cloud migrations. 

Professional Career Timeline

  • 1990 – 1994: Programmer at The Software Partnership (later Deluxe Data). Developed electronic banking software (sp/ARCHITECT-BANK) on Tandem Computers (now HPE NonStop) for major banks like TSB and Bank of Scotland.
  • 1994 – 1995: Lead Analyst at Deluxe Data International, continuing support and development for banking customer systems.
  • 1995 – 2013: Project Manager of Strategic Technical Initiatives at Insider Technologies Limited. Oversaw projects involving Reflex 80:20, Sentra development, and corporate website authoring.
  • 2013 – 2014: Project Manager (Banking Division) at Wincor Nixdorf Limited, focusing on professional services for the banking sector.
  • 2014 – 2016: Senior Digital Project Manager at Betfred Limited, managing the Online and Mobile Division.
  • 2016 – Present:Engagement Manager / Senior PM at Capgemini UK.
    • 2016: Led a £4.3M data centre migration for Royal Mail (RMG) involving 1,100+ interfaces.
    • 2018 – 2019: Augmented into MuleSoft as a Delivery Manager for the Anypoint Platform.
    • 2020 – Present: Leading a £13.5M cloud migration program moving 130 UK government apps to Azure and AWS. 

Technical Training & Education

Whitfield maintains an active Professional Training timeline to adapt to changing technologies:

  • 1990: Graduated in Computing.
  • 1995: HP NonStop TAL Programming and Performance Tuning.
  • 1997: C/C++ Programming at Comtec.
  • 2006 – 2009: Deep dive into security and databases, including Cryptography, Thales e-Security, and Microsoft SQL 2000.
  • 2011: Java and Google Android programming using Eclipse IDE.
  • 2014 – 2024: Advanced Microsoft Excel and AI-focused refreshers. 

He is also a Certified Engagement Manager and a registered PRINCE2 Practitioner proficient in both Agile Scrum and Waterfall methodologies.

Project Management Terms Explained Overview

Project Management Terms Explained Overview

Web Development Stack from Browser to Database

Web Development Stack from Browser to Database

Why Projects Fail

Why Projects Fail

A Successful Project Plan Approach includes

A Successful Project Plan Approach includes

Agile Development – Continuous Integration CI, Continuous Delivery/Deployment CD

Agile Development – Continuous Integration CI, Continuous Delivery/Deployment CD

Project Management Soft Skills Overview

Project Management Soft Skills Overview

PRINCE2 7 Process Model, 2026 – 7th Edition

In 2026, the PRINCE2 7 (7th Edition) remains the current global standard for the methodology. The core diagram, known as the PRINCE2 Process Modelillustrates how the 7 processes interact across the four management levels: Corporate, Direction, Management, and Delivery

The PRINCE2 7 Process Model

The diagram typically visualises the project lifecycle from a “Project Mandate” to “Project Closure” through these processes: 

  • Starting Up a Project (SU): The pre-project process where a mandate is converted into a project brief.
  • Directing a Project (DP): The Project Board’s high-level oversight, running from project start to finish.
  • Initiating a Project (IP): Establishing firm foundations, including the Project Initiation Documentation (PID) and the Business Case.
  • Controlling a Stage (CS): The daily management of a stage by the Project Manager.
  • Managing Product Delivery (MP): The link between the Project Manager and Team Managers to ensure products are built.
  • Managing a Stage Boundary (SB): Occurs at the end of each management stage to plan the next one and review the current.
  • Closing a Project (CP): The final process for a formal decommissioning of the project. 
PRINCE2 7 Process Model, 2026 – 7th Edition

Project Management Types Summarised, Overview

Project Management Types Summarised, Overview

Project Management videos

Project Management videos