Category: Uncategorized

Mark Whitfield, Website Author – Background and Career Timline

Mark Whitfield is a Senior IT Project Manager and Engagement Manager with over 30 years of experience in the software development lifecycle (SDLC). He is currently a SC-cleared Engagement Manager at Capgemini UK. 

Professional Background by Era

  • 1990–1995: Early Programming (The Software Partnership/Deluxe Data)
    • Role: Programmer/Lead Analyst.
    • Focus: Developed electronic banking software (sp/ARCHITECT-BANK) on Tandem Mainframe Computers (now HPE NonStop).
  • 1995–2013: Senior Development & Product Management (Insider Technologies)
    • Role: Progressed from Senior Programmer to Project Manager for Strategic Technical Initiatives.
    • Focus: Developed platform health and diagnostic modules for the “Reflex” monitoring product.
  • 2013–2014: Project Management (Wincor Nixdorf)
    • Role: Project Manager, Professional Services – Banking Division.
    • Focus: Managed the Wincor Nixdorf workstream for Lloyds Banking Group’s Self-Service Software Replacement (SSSR) programme.
  • 2014–2016: Digital Project Management (Betfred)
    • Role: Senior Digital Project Manager, Online and Mobile Division.
    • Focus: Delivered payment gateways, sportsbooks, and virtual gaming components for iOS, Android, and Windows.
  • 2016–Present: Senior Engagement Management (Capgemini)
    • Role: Engagement Manager (A8), Custom Bespoke Solutions.
    • Focus: Leading digital transformation and cloud migration projects for public and private sector clients. 

Technologies & Frameworks

  • Project Methodologies: Agile SCRUM, PRINCE2 (Practitioner), Waterfall, ITIL, and ISO QA.
  • Mainframe & Infrastructure: HPE NonStop (Tandem), IBM ESB, UNIX shell scripting, and Cloud (MS Azure/AWS).
  • Programming & Databases: C/C++, MS SQL, Java, COBOL85, TAL, TACL, and SCOBOL.
  • Tools: MS Project, MS Excel/Office, MuleSoft Anypoint Platform, and Jira. 

Major Projects & Customers

  • UK Government: Managed a £13.5m cloud migration of 130 applications and the £1m+ Fish Export Service (FES) to CHIP portal.
  • Royal Mail Group (RMG): Managed a £4.3m data centre migration project involving over 1,100 interfaces.
  • Lloyds Banking Group (LBG): Led a £5m+ self-service software replacement project.
  • Other Notable Clients: Jaguar Land Rover (JLR), Heathrow, NATS (Air Traffic Control), Barclays, HSBC, Deutsche Bank, and Euroclear. 

Awards & Education

  • Awards:
    • C&CA UK’s Communications & Engagement Award (2022) at Capgemini UK.
    • Project Recognition Award from Wincor Nixdorf for achievements on the LBG SSSR project.
  • Education:
    • HND in Computer Studies (Distinction) from the University of Greater Manchester (formerly BIHE), 1988–1990.
    • A-Levels in Computer Science and Biology from Leigh College. 

Project Management Templates

Whitfield provides a library of over 200 editable resources through his site, PROject Templates, designed for Agile, Waterfall, and PRINCE2 7th Edition delivery. Key items include: 

  • Plan on a Page (POaP): Over 35+ executive-level summary slides.
  • Detailed Project Plans: Templates in MS Project (MPP) and Excel for SDLC tracking.
  • RAID Logs: Comprehensive registers for risks, actions, issues, and dependencies. 

Mark Whitfield Background and Career Timline

PRINCE2 Management Products Templates Overview and Historical Timeline

PRINCE2 management products are the 26 standard documents (templates) used to manage a project throughout its lifecycle. They are categorised into Baselines (plans and definitions), Records (registers and logs), and Reports (periodic updates). 

PRINCE2 Microsoft Project & Excel templates

Management Products Overview

The core templates provided in the methodology ensure consistent project control. Official templates are often available through accredited providers, this website or the official AXELOS website. 

  • Baselines: Used to define the project foundation (e.g., Business Case, Project Initiation Document, Plan).
  • Records: Dynamic logs to track day-to-day data (e.g., Risk Register, Issue Register, Lessons Log).
  • Reports: Snapshots of progress or specific events (e.g., Highlight Report, Checkpoint Report, Exception Report). 

Historical Timeline of Templates & Methodology

The evolution of these products reflects a shift from rigid, IT-specific documents to flexible, industry-agnostic templates. 

The Pre-PRINCE Era (1975 – 1988) 

  • 1975: PROMPT II (Project Resource Organisation Management and Planning Techniques) was developed by Simpact Systems Ltd.
  • Key Focus: Introduced the concept of project phases (Initiation, Specification, Design) but was strictly for IT. 

The PRINCE Era (1989 – 1995) 

  • 1989: PRINCE (PROMPT II in the CCTA Environment) launched by the UK Government’s CCTA.
  • Key Focus: Added Critical Path Analysis and formal management roles, but remained IT-heavy and rigid. 

The PRINCE2 Emergence (1996 – 2008)

  • 1996: PRINCE2 (1st Edition) was released as a generic framework.
  • Key Change: IT-specific jargon was removed to make templates applicable to any industry.
  • 2002/2005: Minor updates (3rd and 4th Editions) focused on minor refinements based on user feedback. 

The Revision Era (2009 – 2022)

  • 2009: PRINCE2:2009 Refresh (5th Edition) introduced the seven core principles.
  • Key Change: Templates were simplified and made more customisable to reduce “prowess-driven” bureaucracy.
  • 2017: PRINCE2 6th Edition (formerly the 2017 Update) launched.
  • Key Change: Emphasis on Tailoring and scalability for different project sizes. 

The Modern Era (2023 – Present)

  • 2023: PRINCE2 7th Edition was released.
  • Key Change: Added a “People” element and introduced three new management approaches: Sustainability, Commercial, and Digital & Data. 

Template Kits & Resources

For those seeking pre-formatted digital versions:

  • PRINCE2 7th Edition Template Bundle: Comprehensive sets including MS Project MPP, Excel Gantt charts, and Word artifacts are available at Etsy and eBay.
  • Specialised Packs: Focused collections like the PRINCE2 Control & Monitoring Pack can be found at WorkFlo Design.
  • Individual Documents: Individual templates like the Project Initiation Document (PID) are often sold separately for specific project needs. 
  • PRINCE2 Templates can be purchased directly from this website including a Microsoft Project Plan in MPP format and also a Microsoft Excel Project Plan in XLS format, see below and website link.

PRINCE2 Management Products Templates Overview and Historical Timeline

PRINCE2 Microsoft Project MPP file template
PRINCE2 Microsoft Excel XLS template 1
PRINCE2 Microsoft Excel XLS template 2

PRINCE2 Templates FREE Upgrades

Mark Whitfield’s PRINCE2 template collection is a comprehensive set of over 200 editable Microsoft Office documents designed to support both waterfall and agile project delivery. These templates are classified into several key categories, ranging from core PRINCE2 management products to advanced planning and tracking tools. 

Example Microsoft Project MPP file template

Core PRINCE2 Management Product Templates

This category includes the standard documentation required by the PRINCE2 methodology, often provided in MS Word (.doc) format. 

  • Project Initiation & Definition:
    • Project Brief: Initial summary used to gain approval for the initiation stage.
    • Project Initiation Document (PID): A comprehensive document containing the project definition, approach, business case, and management strategies.
    • Business Case: The primary justification for the project’s existence.
  • Registers and Logs:
    • Risk Register: For identifying and managing project risks.
    • Issue Register & Issue Report: For tracking and detailing specific project problems.
    • Lessons Log & Lessons Report: To capture and share knowledge gained throughout the project.
    • Daily Log: For the Project Manager to record informal issues or activities.
  • Reporting and Progress:
    • Highlight Report: Periodic progress updates for the Project Board.
    • Checkpoint Report: Updates from the Team Manager to the Project Manager.
    • End Stage & End Project Reports: Summaries of performance at key project milestones.
    • Exception Report: Used when a project is forecast to exceed its tolerances.
  • Quality and Configuration:
    • Product Description: Detailed specifications for each project deliverable.
    • Quality Register: Records all planned and completed quality activities.
    • Configuration Item Record: Tracks the status and version of project products. 

Advanced Planning and Tracking Templates 

Whitfield provides specialized tools for visual scheduling and financial management, primarily in MS Excel and MS Project (.mpp) formats. 

  • Project Planners:
    • PRINCE2 Waterfall Project Planner: A detailed Gantt-view planner in Excel for those without MS Project licenses.
    • MS Project (MPP) Templates: Pre-configured plans for PRINCE2 7th Edition, including end-to-end tasks and lifecycle stages.
    • Plan on a Page (POaP): High-level visual summaries of project timelines.
  • Resource and Financial Management:
    • Project Financial Tracker: Monitors forecast vs. actual costs, including margins and expenses.
    • Resource Costing Grid: Detailed grids for calculating costs per project phase.
    • RACI Tracker: Defines Roles and Responsibilities (Responsible, Accountable, Consulted, Informed). 

Operational and Agile Support

These supplemental templates assist with daily project operations and hybrid agile environments. 

  • RAID Log: A centralized tracker for Risks, Actions, Issues, and Dependencies.
  • Agile Specifics: Burn-down/up charts and sprint-view Gantt charts for scrum-based delivery.
  • Stakeholder Analysis Plan: Tools to map stakeholder influence versus impact.
  • Mobilisation/On-boarding Kit: PowerPoint templates for team kick-offs and onboarding. 

Visual Classification (Font Coding) 

In many of Whitfield’s automated plans, tasks are color-coded for quick visual breakdown: 

  • Black: Traditional PRINCE2 stage or activity.
  • Blue: Creation of a PRINCE2 artefact (e.g., creating a log).
  • Purple: Updating an existing artefact.
  • Green: Formal closing of an artefact. 

The full bundle is available for purchase on Mark Whitfield’s Official Website or through his Etsy Store. 

PRINCE2 Templates FREE Upgrades

Waterfall Methodology in Project Management, a Timeline History

The Waterfall methodology is a linear, sequential project management approach where progress flows steadily downward through defined phases, such as requirements, design, implementation, and testing. Each stage must be completed and approved before the next begins, making it highly structured but often inflexible to changes. 

Waterfall template available on this website

Historical Timeline by Era and Year

The history of the Waterfall model spans from early post-WWII engineering to its formalisation in software and eventual institutionalisation in government standards. 

The Pre-Formal Era (1950s – 1969)

During this period, software development borrowed heavily from established engineering and manufacturing processes. 

  • 1956: Herbert D. Benington presents a paper on the Semi-Automatic Ground Environment (SAGE) project, describing a structured process that many consider the true technical origin of the sequential approach.
  • Late 1960s: Major NASA projects and government software systems for rockets (e.g., Apollo missions) utilise rigid specifications and linear development due to the high cost of changes.
  • 1968: The NATO Software Engineering Conference identifies the “software crisis”—projects consistently running over budget and time—leading to a push for more disciplined models. 

The Formalisation Era (1970 – 1979)

The methodology was formally described, ironically as a cautionary tale, and finally given its name. 

  • 1970: Dr. Winston W. Royce publishes “Managing the Development of Large Software Systems”. He presents the sequential diagram but explicitly critiques it as “risky and invites failure,” suggesting a more iterative approach instead.
  • 1976: The term “Waterfall” is officially coined in a paper by Bell and Thayer, “Software Requirements: Are They a Problem?”. 

The Institutional Era (1980 – 1999)

Waterfall becomes the global standard for large-scale and regulated industries. 

  • 1985: The U.S. Department of Defense (DoD) adopts DOD-STD-2167, which mandates the use of the Waterfall model for all software development contractors. This cements Waterfall as the “one true way” for government and aerospace projects.
  • 1989: The UK Government creates PRINCE2, a process-based method largely rooted in Waterfall principles, still widely used in the public sector today.
  • 1991: In response to Waterfall’s rigidity, James Martin introduces Rapid Application Development (RAD), one of the first major departures from the linear model. 

The Modern & Hybrid Era (2000 – Present)

As Agile became dominant, Waterfall shifted from the default choice to a specialised or hybrid tool. 

  • 2001: The Agile Manifesto is published, marking a significant industry-wide shift away from traditional Waterfall toward iterative development.
  • 2009: Major institutions like George Washington University and others begin documenting their Project Management Lifecycle (PMLC) to standardise Waterfall and hybrid models for better oversight.
  • 2020s: Waterfall persists in regulated domains like healthcare, aerospace, and construction. It is increasingly integrated into hybrid methodologies that use Waterfall for high-level planning and Agile for execution. 

Waterfall Methodology in Project Management, a Timeline History

Waterfall template available on this website

BASE24 by ACI Worldwide timeline by era and year

BASE24 is the world’s most widely used payment processing platform, developed by ACI Worldwide. Originally designed for ATM networks, it evolved into a comprehensive system for acquiring, authenticating, and routing card-based and digital transactions across various channels. It is known for its high-performance, fault-tolerant architecture, processing nearly 50% of the world’s electronic transactions at its peak. 

Comprehensive Timeline by Era

Era 1: Foundations & The Rise of BASE24 Classic (1975–1990s)

This era focused on high-availability software for the emerging automated banking industry, specifically for Tandem NonStop servers. 

  • 1975: ACI founded in Omaha, Nebraska, to develop software for the new “NonStop” server computers used by banks and stock exchanges.
  • 1981: Secured its first international client, an Australian bank, marking the start of global expansion.
  • 1982: Launch of BASE24, the first global product designed for 24-hour system operations, originally focused on ATM networks.
  • 1986: Rapid growth led to 131 customers across 14 different countries. 

Era 2: Expansion & Public Transition (1995–2000s) 

The platform expanded into Point of Sale (POS) and branch systems while the company underwent major structural changes. 

  • 1995: The company went public on NASDAQ as Transaction Systems Architects (TSA).
  • 1997: Officially adopted the name ACI Worldwide.
  • Early 2000s: Introduction of BASE24-es (later renamed BASE24-eps), a next-generation platform using C++ and object-based architecture to replace the legacy monolithic design. 

Era 3: Modernisation & The “eps” Shift (2005–2015)

ACI shifted focus toward BASE24-eps, a more flexible, open-architecture version designed for multi-channel transaction processing. 

  • 2005: ACI launches BASE24-eps, featuring a modular engine capable of processing approximately 2,000 transactions per second (TPS) with extremely low latency.
  • 2007: TSA officially rebranded all operations under the ACI Worldwide, Inc. (ACIW) name.
  • 2008: Announced that BASE24 Classic would begin maturing in 2011, urging customers to migrate to the eps platform for better integration with modern systems like IBM System z.
  • 2011–2012: Release of BASE24-eps 11.1, adding support for DB2 on IBM System p, enhanced EMV acquiring, and tools for easier migration from legacy BASE24. 

Era 4: Cloud & Universal Payments (2015–Present)

The platform moved toward cloud-native capabilities and broader ecosystem integration. 

  • 2015: ACI celebrated its 40th anniversary, continuing to power electronic payments for over 6,000 organisations worldwide.
  • 2018: Introduction of UP BASE24-eps on Linux in the Cloud, demonstrating significantly reduced Total Cost of Ownership (TCO) through public and private cloud deployment.
  • Present: BASE24 remains a core pillar of ACI’s portfolio, supporting traditional card, ATM, mobile commerce, and internet banking transactions.

BASE24-eps by ACI Worldwide timeline by era and year

BASE24-eps is a modular, high-availability payment processing engine developed by ACI Worldwide. It evolved from the original “BASE24 Classic” to provide a more flexible, open-system architecture for acquiring, authenticating, routing, and authorizing electronic transactions. 

Base24-eps Overview

  • Architecture: Unlike the TAL-based Classic version, BASE24-eps uses an object-oriented design written primarily in C++ and Java.
  • Key Features:

Detailed Timeline

The Foundation Era (1970s – 1990s)

  • 1975: ACI is founded in Omaha, Nebraska, initially developing software for NonStop server computers.
  • Late 1970s: Development of the original BASE24 (now known as “Classic”), focused on high-uptime ATM processing.
  • 1981: First international customer (an Australian bank) signs on, starting the global expansion of BASE24. 

Transition & Development Era (2000 – 2005)

  • Early 2000s: ACI begins developing the “next generation” platform, initially called BASE24-es (extended systems), which later becomes BASE24-eps (enterprise payment system).
  • 2003 – 2004: The product begins migrating to open architectures, moving away from platform-specific languages. 

Mainstream Adoption Era (2006 – 2013)

  • 2007: ACI highlights BASE24-eps as its strategic future platform in investor overviews.
  • 2008: ACI announces the maturation of BASE24 Classic (ending standard maintenance in 2011), urging customers to migrate to BASE24-eps.
  • 2009: IBM Redbooks releases technical guides for BASE24-eps 08.2 on z/OS, solidifying its place in enterprise banking.
  • 2013: Release of BASE24-eps 2.0, introducing the “customer component” and enhanced service-enabling wrappers. 

Modernization & Cloud Era (2014 – Present)

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

Mark Whitfield IT Project Manager Training Focus

Mark Whitfield, an IT Project Manager specializing in HP NonStop systems, has a career and training history that spans over three decades, from his academic beginnings in the late 1980s to advanced cloud certifications in the 2020s. 

Early Career & Foundations (1988–1995)

During this era, Whitfield focused on core computer science and specialized mainframe systems while working for The Software Partnership (TSP) and Deluxe Data. 

  • 1988–1990: Completed a Higher National Diploma (HND) in Computing at the Bolton Institute of Higher Education (BIHE). Modules included Computer Systems Architecture, Programming Methodology, and Data Processing.
  • May 1993: Tandem Guardian Principles Course.
  • September 1994: VPS 7000/9000 Series and VPS Application Development (VOS 4.3).
  • June 1995: HP NonStop (Tandem) Performance Analysis and Tuning.

Development & Technical Specialisation (1995–2005)

Working primarily with Insider Technologies Limited, this period was marked by software development training in languages like C++ and initial forays into project management. 

  • November 1995: HP NonStop TAL Programming.
  • March 1997: C / C++ Programming at Comtec Computer Training.
  • October 1998: Managing Multiple Projects, Objectives, and Deadlines at SkillPath.
  • February 1999: Successful Project Management at SkillPath.
  • May 2000: Microsoft Project ’98 Certification (Orange Belt) at the IIL UK Education Centre.
  • February 2001: Sales and Marketing training (In-House).
  • March 2004: MultiBatch NSK Job Scheduling Product.
  • February 2005: Web Services and SOA. 

Web Development & Security Focus (2006–2010) 

This era shows a shift toward web-based technologies and specialized security products. 

  • January 2006: PRINCE2 Project Management Foundation.
  • February 2006: NetObjects Fusion.
  • March 2006: Cryptography (In-House at Thales e-Security).
  • December 2006: Thales e-Security SafeSign Product.
  • January 2007: Developing Web Applications Using Microsoft Visual Studio .NET.
  • March 2009: Querying Microsoft SQL 2000 with Transact SQL (M2071) at QA Training.
  • May 2009: Writing for the Web and Website Visibility & Promotion at iTrain Education.
  • November 2009: Thales e-Security HP NonStop Security Resource Manager (SRM). 

Agile & Advanced Management (2011–Present) 

In his current era at companies like Betfred and Capgemini, Whitfield has prioritized professional certifications in management and cloud infrastructure. 

  • May 2011: Agile SCRUM Training (RADTAC) and PRINCE2 Practitioner Certification (ILX Group).
  • June–July 2011: Java and Google Android programming using the Eclipse IDE.
  • January 2012: ITIL Foundation Course.
  • July 2014: Advanced Microsoft Excel 2013.
  • November 2017: Advanced Engagement Management Certification (Level 2) at Capgemini.
  • February 2022: AZ-900 Microsoft Certified Azure Fundamentals.
  • July 2024: Microsoft Excel Refresher 2024 via Udemy. 

Mark Whitfield IT Project Manager Training Focus

Higher National Diploma (HND) in Computer Studies, Bolton Institute of Higher Education (BIHE)—now the University of Greater Manchester

The Higher National Diploma (HND) in Computer Studies at the Bolton Institute of Higher Education (BIHE)—now the University of Greater Manchester—is a two-year, Level 5 vocational qualification designed to provide practical, industry-specific skills. 

LinkedIn Group: https://www.linkedin.com/groups/51224

BIHE / University of Greater Manchester Evolution

The institution has undergone several name changes and status upgrades that affected the delivery of the HND: 

  • 1982: BIHE was formed through the merger of Bolton Institute of Technology and Bolton College of Education (Technical).
  • 1992: The Institute was granted the power to award taught degrees.
  • 2004/2005: BIHE achieved full university status, becoming the University of Bolton.
  • 2024: The university rebranded as the University of Greater Manchester. 

HND Computer Studies: Detailed Timeline

The course traditionally follows a two-year full-time or three-year part-time structure. 

Year 1: Foundations (HE4 Level)

The first year focuses on establishing core technical and business knowledge. In many versions of the Bolton curriculum, Year 1 is common across several computing programmes to allow for flexible progression. 

  • Core Modules:
    • Introduction to Programming: Developing fundamental coding logic.
    • Computer Platforms & Systems Architecture: Understanding the hardware and software environments.
    • Information Systems & Databases: The basics of data management.
    • Website Production & Networking Fundamentals: Introduction to web technologies and connectivity.
    • Quantitative Techniques & Business Studies: Integrating mathematical and commercial contexts. 

Year 2: Specialisation (HE5 Level)

The second year shifts toward advanced application, systems analysis, and professional practice. 

  • Advanced Modules:
    • Systems Analysis & Design: Producing system requirements and user interface specifications.
    • Programming Methodology: Moving into more complex application development.
    • Business Information Systems: Exploring how IT supports organizational requirements.
    • Database Design: Implementing industry-standard database packages.
  • Final Year Project: A major 20-credit core project where students investigate a specific field and apply their cumulative skills to a real-world scenario. 

Progression and Modern Standards

  • Academic Standing: Completion of the HND is equivalent to the first two years of a Bachelor’s degree (Level 5).
  • Degree Top-Up: Successful HND graduates can typically proceed directly into the final year (Level 6) of the BSc (Hons) Computer Science or BSc (Hons) Computing at Bolton.
  • Modern HTQs: Current versions of the course, such as the HND Computing for England (HTQ), now integrate modern fields like Artificial Intelligence, Cloud Computing, and VR technologies.
1988 to 1990 : University of Greater Manchester (previously Bolton Institute of Higher Education – BIHE)
Higher National Diploma (HND) in Computer Studies, Bolton Institute of Higher Education (BIHE)—now the University of Greater Manchester

Henry Ford Mastered Leadership in 8 Ways

Henry Ford Mastered Leadership in 8 Ways

iProPMTemplates on Etsy for Project Management Templates with FREE Upgrades

Mark Whitfield is a Senior Project Manager with over 30 years of experience in delivering PRINCE2 Waterfall and Agile Scrum projects. Operating the Etsy shop ProjectTemplatesSoft (also known as iProPMTemplates), he provides a comprehensive bundle of over 200 professional project management templates. 

Operating the Etsy shop ProjectTemplatesSoft (also known as iProPMTemplates)

Author Overview: Mark Whitfield

  • Professional Background: Graduated in Computing in 1990 and began his career as a programmer in electronic banking software.
  • Expertise: Senior Project Manager and PRINCE2 Practitioner with extensive experience in the Software Development Lifecycle (SDLC).
  • Value Proposition: His templates are designed to be “imitation-proof” professional toolsets used in real-world project delivery.
  • Support Policy: Offers FREE upgrades and additions for life to anyone who purchases his template bundles; users simply contact him via Etsy or his official website. 

Detailed Project Templates Inventory

The expanded inventory typically included in his master ZIP file covers the entire project lifecycle across various formats (Excel, Word, PowerPoint, and MS Project). 

1. Planning & Scheduling Templates

  • MS Project (MPP) Plans: Detailed SDLC Microsoft Project plans adaptable for Waterfall and Agile Scrum, including PRINCE2 7th Edition specific plans.
  • Excel Project Planners: Robust Waterfall and PRINCE2 planners with automated Gantt views, designed for users without MS Project licenses.
  • Plan on a Page (POaP): High-level PowerPoint and Excel templates for stakeholder presentations, showing project timelines and key milestones.
  • Agile Frameworks: Templates for Sprint planning, Daily Stand-ups, Sprint Reviews, and Retrospectives. 

2. Tracking & Control (RAID & RACI)

  • Comprehensive RAID Log: An Excel-based master tracker for Risks, Assumptions, Issues, Dependencies, and Decisions.
  • RACI Matrix: For defining roles and responsibilities (Responsible, Accountable, Consulted, Informed).
  • Agile Trackers: Includes Burn Down and Burn Up charts for teams not using Jira or similar tools. 

3. Financial & Resource Management

  • Project Financial Tracker: Detailed spreadsheets for tracking forecasts, actuals, margins, and variance.
  • Resource Costing Grid: Tools for estimating resource costs across project phases, useful for bidding and Statements of Work (SoW).
  • Capacity Planning: Templates for managing team availability and on-boarding mobilization kits. 

4. Documentation & Reporting

  • Status Reports: Weekly and monthly templates in Word and PowerPoint.
  • Standard PRINCE2 Artifacts: Complete set including Business Cases, Project Briefs, Highlight Reports, and End Stage Reports.
  • Governance Tools: Meeting minutes, stakeholder analysis plans, and Benefits Realisation Plans. 

iProPMTemplates on Etsy for Project Management Templates with FREE Upgrades

AI Projects and Methodologies for Managing AI Projects

Artificial intelligence (AI) is transforming project management through two distinct but related paths: the use of AI-powered tools to manage general projects and the specialized methodologies required to manage AI development itself. 

1. Methodologies for Managing AI Projects

Traditional software development methods (like Waterfall) often fail for AI because these projects are experimental and non-linear. Specialized frameworks have emerged to handle the “data-first” nature of AI: 

  • CPMAI (Cognitive Project Management for AI): A leading methodology that combines Agile principles with data-centric phases: Business Understanding, Data Understanding, Data Preparation, Model Development, Model Evaluation, and Model Operationalization.
  • Agile-AI Hybrid: Adapts standard Agile by using “short-boxed” iterations for model training and allowing for a “flexible scope” because model performance is unpredictable until tested.
  • Data Driven Scrum: A variation of Scrum that prioritizes work based on data availability and experimental results rather than just feature backlogs.
  • MLOps (Machine Learning Operations): An operational framework focused on the continuous integration, deployment, and monitoring of models to prevent “model drift” after a project officially “ends”. 

2. AI-Augmented Project Management (The “AI Copilot”)

For non-AI projects, AI acts as an intelligent assistant to automate administrative tasks and provide predictive insights. 

3. Implementation Strategy

Experts recommend a phased approach to integrating AI into management workflows: 

  1. Assess Inefficiencies: Identify repetitive tasks (e.g., status reporting) that can be automated first.
  2. Data Governance: Ensure project data is clean and centralized; AI is only as good as the data it consumes (“Garbage In, Garbage Out”).
  3. Human-in-the-Loop: Use AI for data-heavy lifting, but retain human judgment for high-stakes leadership, ethics, and stakeholder empathy.

AI Projects and Methodologies for Managing AI Projects

AI history of artificial intelligence by era

The history of artificial intelligence is defined by cycles of extreme optimism followed by “winters” of reduced funding and interest. It has evolved from a theoretical branch of mathematics into a pervasive modern technology. 

The Foundations (Pre-1950)

Before AI was a formal field, it existed in science fiction and early mechanical concepts. 

  • 1921: The term “robot” is coined by Karel Čapek in the play Rossum’s Universal Robots.
  • 1943: Warren McCulloch and Walter Pitts publish the first mathematical model of a neural network.
  • 1949: Edmund Berkeley’s book Giant Brains proposes that machines can think. 

The Birth of AI (1950–1956)

This era shifted AI from mythology to a serious academic discipline. 

  • 1950: Alan Turing publishes “Computing Machinery and Intelligence,” introducing the Turing Test to measure machine intelligence.
  • 1952: Arthur Samuel creates the first self-learning checkers program.
  • 1955-1956: John McCarthy coins the term “Artificial Intelligence” during the proposal for the Dartmouth Workshop, which officially launched the field. 

The Golden Years & First AI Winter (1957–1979) 

Initial successes led to over-promising and a subsequent crash. 

  • 1958: Frank Rosenblatt develops the Perceptron, the foundation for modern neural networks.
  • 1966: Joseph Weizenbaum creates ELIZA, the first “chatterbot”.
  • 1973-1974: The Lighthill Report in the UK and subsequent funding cuts by DARPA lead to the First AI Winter due to limited computing power and unmet expectations.

The Expert Systems Boom & Second Winter (1980–1993)

AI found commercial success through specialized knowledge bases before another decline. 

  • 1980: XCON (expert configurer) becomes the first commercially successful expert system, saving Digital Equipment Corporation millions.
  • 1981: Japan launches the Fifth Generation Computer project with $850 million to create human-level reasoning.
  • 1987-1993: The Second AI Winter occurs as specialized AI hardware (Lisp machines) becomes obsolete compared to cheaper personal computers from Apple and IBM. 

The Age of Agents & Narrow AI (1993–2011) 

AI began achieving superhuman performance in specific, “narrow” tasks. 

  • 1997: IBM’s Deep Blue defeats world chess champion Garry Kasparov.
  • 2002: iRobot releases the Roomba, bringing autonomous AI into the home.
  • 2011: IBM’s Watson wins Jeopardy! against human champions, and Apple releases Siri. 

The Deep Learning Revolution (2012–2021)

A massive surge in data and GPU power transformed the field. 

  • 2012: AlexNet wins the ImageNet competition, proving the power of deep convolutional neural networks.
  • 2016: Google DeepMind’s AlphaGo defeats world Go champion Lee Sedol.
  • 2017: Researchers at Google propose the Transformer architecture, which becomes the backbone of modern large language models. 

The Generative AI Boom (2022–Present)

AI has entered the mainstream, moving toward Agentic AI that can plan and act autonomously. 

  • 2022: OpenAI releases ChatGPT, sparking global interest in generative AI.
  • 2023-2024: Focus shifts toward Multimodal AI (images, video, and text) and Agentic AI capable of completing complex workflows across multiple tools. 

AI history of artificial intelligence by era

An amble around Manchester, 17th March 2026

Ghandi, Manchester City Centre
Abraham Lincoln 1, Manchester City centre
Abraham Lincoln 2, Manchester City centre
Midland Hotel, Manchester

An amble around Manchester, 17th March 2026

Middlebrook Retail Park, Horwich, Bolton Detailed Timeline by Era

Middlebrook Retail Park, located in Horwich, Bolton, is one of the largest integrated retail and leisure destinations in the UK. Covering approximately 200 acres at Junction 6 of the M61, it serves as a mixed-use complex combining over 60 high-street stores with major leisure facilities, two hotels, and the home of Bolton Wanderers F.C.. 

Middlebrook Retail Park, Horwich, Bolton Detailed Timeline by Era

Historical Timeline of Middlebrook

Pre-Development Era (16th Century – 1994) 

  • 16th Century: The site was originally home to Sefton Fold Farm, a three-bay timber-framed farmhouse.
  • Late Medieval: Archaeological digs later revealed a moated site and pottery from this era.
  • Pre-1994: Much of the land consisted of open fields and the former Red Moss tip. 

Inception & Construction Era (1994 – 1997)

  • 1994: Plans for the ambitious scheme were first announced, including a 25,000-seater stadium and 6,000-seater indoor arena.
  • 1995: Outline planning applications for the football stadium were approved in July.
  • 1996: Orbit Developments (part of The Emerson Group) began physical construction. By Christmas, many key buildings were already constructed.
  • 1997: The Reebok Stadium (now Toughsheet Community Stadium) was inaugurated on 1 September with a match between Bolton and Everton.
  • 1997 (Summer): Initial food outlets like McDonald’s, Pizza Hut, and KFC opened for business. 

Establishment & Expansion Era (1998 – 2005)

  • 1998: The first retail businesses officially began operating.
  • 2001: Bolton Arena (USN Bolton Arena) opened in the spring after winning a development grant.
  • 2001: Annual visitor numbers reached 12.5 million for the first time.
  • 2002: The site hosted events for the Manchester Commonwealth Games at the sports arena.
  • 2005: Marks & Spencer (M&S) secured planning permission to occupy a vacant store, marking a significant shift toward major non-food retail. 

Modern Maturity Era (2006 – Present)

  • 2006: A time capsule was buried by schoolchildren to celebrate a decade of development.
  • 2006 (October): Several high-profile stores opened, including HMV and Clarks.
  • 2020s: The park continues to house over 62 high-street brands including ASDA Supercentre, Vue Cinema, and Hollywood Bowl.
  • Present: It remains a top-ranked UK retail park, attracting over 910,000 shoppers per month. 

Middlebrook Retail Park, Horwich, Bolton Detailed Timeline by Era

Middlebrook Retail Park, Horwich, Bolton Detailed Timeline by Era

Benefits Realization Process is a structured framework

Benefits Realization Process

The benefits realization process is a structured framework used to ensure that projects and programmes deliver the tangible value and strategic outcomes intended by an organisation. Unlike traditional project management, which focuses on outputs (deliverables like a new software), benefits realization focuses on outcomes (the actual value derived, such as a 10% increase in efficiency). 

Core Stages of the Process

While various frameworks exist, most follow three or four primary stages:

  • 1. Identification: Defining the expected benefits at the start of a project. This involves aligning benefits with the organisation’s strategic goals and identifying “benefit owners” who will be accountable for their delivery.
  • 2. Planning: Developing a Benefits Realization Plan that establishes metrics, Key Performance Indicators (KPIs), and timelines for when benefits will be achieved.
  • 3. Execution & Delivery: Monitoring and managing the project to ensure it stays on track to deliver the planned benefits. This includes managing risks that could negatively impact benefit delivery.
  • 4. Sustainment & Review: Occurring post-project completion, this stage focuses on ensuring benefits are fully realized and sustained over the long term. A final review is conducted to compare actual results against the original business case. 

Key Components and Tools

  • Benefits Register: A central document used to track and manage all identified benefits, their owners, and their current status.
  • Benefit Profiles: Detailed records for individual benefits, describing what they are, how they will be measured, and who is responsible for them.
  • Benefit Dependency Map (BDM): A visual tool showing the links between project outputs, organizational changes, and final strategic objectives.
  • Benefit Owners: Individuals (usually from the business side) who are accountable for ensuring a specific benefit is achieved and sustained after the project team disbands. 

Why It Matters

Organizations that mature in benefits realization management are significantly more likely to meet their original goals and business intent. It bridges the gap between high-level strategy and tactical project execution, ensuring that investments translate into actual business value. 

Benefits Realization Process is a structured framework

Project Quality Plan PQP in QA/QC Overview

Project Quality Plan PQP in QA/QC Overview

The primary purpose of a Project Quality Plan (PQP) is to define the standards, tools, and processes required to ensure a project’s deliverables are “fit for purpose” and meet all stakeholder expectations. It serves as a strategic roadmap for the project team to maintain consistent quality throughout the project lifecycle rather than treating it as an afterthought. 

Core Objectives

A PQP is designed to achieve several critical goals: 

  • Define “Quality”: Translates vague stakeholder needs into measurable criteria and specific benchmarks.
  • Prevent Defects: Establishes Quality Assurance (QA) processes to proactively “build in” quality from the start, reducing the risk of errors.
  • Detect and Correct Issues: Outlines Quality Control (QC) activities, such as testing and inspections, to identify and fix defects before they reach the customer.
  • Clarify Accountability: Assigns specific roles and responsibilities so every team member knows who is responsible for performing, checking, and approving work.
  • Ensure Compliance: Guarantees the project adheres to relevant internal policies, legal regulations, and industry standards like ISO 9001. 

Strategic Benefits

Implementing a structured quality plan provides tangible advantages for project management: 

  • Reduced Costs and Rework: By catching errors early, the team avoids expensive last-minute fixes and wasted resources.
  • Improved Efficiency: Standardised workflows and clear metrics allow the team to focus on production rather than constant troubleshooting.
  • Increased Stakeholder Trust: Providing objective evidence through audits and reports gives sponsors and clients confidence in the final outcome.
  • Continuous Improvement: The plan often includes feedback loops and lessons-learned processes to refine and enhance quality for future project phases.

Project Quality Plan PQP in QA/QC Overview

PRINCE2 Management Stages Overview

In PRINCE2, a project is managed through a series of management stages, which are discrete sections of a project that the Project Board authorises at specific decision points. Every PRINCE2 project must have at least two stages: an initiation stage and at least one further delivery stage. 

PRINCE2 Management Stages Overview

A detailed breakdown of these stages, aligned with the seven core PRINCE2 processes, is provided below. 

1. Starting Up a Project (SU)

This is a pre-project process designed to determine if the project is viable and worthwhile before committing significant resources. 

  • Key Activities:
    • Appointing the Executive and Project Manager.
    • Developing an Outline Business Case.
    • Creating a Project Brief which defines objectives and scope.
    • Planning the initiation stage itself. 

2. Initiating a Project (IP)

This represents the first management stage of the project. It establishes the firm foundation for the project’s execution. 

  • Key Activities:
    • Creating the Project Initiation Documentation (PID), which includes the full Business Case, Project Plan, and management strategies for risk, quality, and communication.
    • Setting up project controls and refining the project approach.
    • Securing formal approval from the Project Board to proceed. 

3. Directing a Project (DP)

This is an ongoing process that spans the entire project lifecycle, focusing on high-level decision-making by the Project Board. 

  • Key Activities:
    • Authorising the project to start and approving each subsequent stage.
    • Giving ad hoc direction and advice to the Project Manager.
    • Making the final “stop/proceed” decisions at stage boundaries.

4. Controlling a Stage (CS)

This covers the day-to-day management of each delivery stage by the Project Manager. 

  • Key Activities:
    • Assigning work to teams via Work Packages.
    • Monitoring progress and managing risks and issues.
    • Reporting status to the Project Board through Highlight Reports. 

5. Managing Product Delivery (MP)

This process manages the link between the Project Manager and the Team Managers who are actually building the products. 

  • Key Activities:
    • Teams accepting and executing Work Packages.
    • Ensuring work meets the specified quality standards.
    • Delivering completed and tested products back to the Project Manager. 

6. Managing a Stage Boundary (SB)

This occurs at the end of each stage (except the final one) to help the Project Board decide whether to continue. 

  • Key Activities:
    • Reporting on the performance of the current stage.
    • Creating a detailed Stage Plan for the next stage.
    • Updating the overall Project Plan and Business Case with the latest information. 

7. Closing a Project (CP)

This is the final part of the last management stage, ensuring the project is shut down in a controlled manner. 

  • Key Activities:
    • Confirming all products have been accepted by the customer.
    • Capturing Lessons Learned for future projects.
    • Preparing an End Project Report to evaluate performance against the original plan.

PRINCE2 Management Stages Overview

Jackson Structured Programming (JSP) Timeline  by year

Jackson Structured Programming (JSP) was developed by British software consultant Michael A. Jackson to provide a rigorous, data-driven alternative to the intuitive “top-down” methods prevalent in the 1970s. Its evolution is characterized by a transition from micro-level program design to macro-level system architecture. 

The Early 1970s: Foundation and Invention

  • 1970: Michael Jackson founded his firm, Michael Jackson Systems Limited, to fully develop a new program design methodology.
  • 1974: The name Jackson Structured Programming (JSP) was coined by the company’s Swedish licensee.
  • 1975: Jackson published the seminal book Principles of Program Design, which formally documented the JSP method and is now considered a classic. 

The Late 1970s: Standardisation and Expansion

  • 1977: JSP reached global recognition, being taught in universities and used across Europe, the US, and Asia.
  • Government Adoption: The UK government adopted JSP as its standard program design method under the name SDM (System Development Methodology).
  • Industry Use: Large organisations like the World Health Organization (WHO) began using JSP as a standard for specifying programs. 

The 1980s: Evolution into System Development (JSD)

  • 1980: Jackson published JSP, A Practical Method of Program Design, further refining the technique for practical industry use.
  • 1982–1983: Jackson, along with John Cameron, introduced Jackson System Development (JSD). While JSP focused on individual programs, JSD expanded these principles to entire systems.
  • Integration: JSD was widely incorporated into the UK’s SSADM (Structured Systems Analysis and Design Method), specifically for entity and event modelling. 

The 1990s to Present: Legacy and Modern Relevance

  • 1990s: Jackson introduced his third major method, Problem Analysis (or the Problem Frames Approach), focusing on requirements and software specifications.
  • Legacy: While JSP has faded from mainstream daily practice due to the rise of Object-Oriented Programming, its core concepts—like deriving program structure from data structures—influenced modern practices like Event Storming in Domain-Driven Design (DDD). 

Jackson Structured Programming (JSP) Timeline  by year