BASIC programming insight and detailed historical timeline by era and year

BASIC (Beginner’s All-purpose Symbolic Instruction Code) was designed to make computers accessible to non-technical users, revolutionising personal computing and software development. 

BASIC Historical Timeline

The Dartmouth Era (1964–1970s)

  • 1964: BASIC was created at Dartmouth College by John G. Kemeny and Thomas E. Kurtz. It first ran on 1 May 1964 on a GE-225 mainframe.
  • 1964: The Dartmouth Time-Sharing System (DTSS) was launched alongside BASIC, allowing multiple users to program simultaneously.
  • 1965: Added character string functionality and simplified mathematical support.
  • 1967: Approximately 2,000 Dartmouth students had learned to code in BASIC by this year.
  • Late 1960s: Hewlett-Packard launched the HP 2000 series, which ran a version of BASIC and brought the language to minicomputers. 

The Microcomputer Revolution (1975–1980s) 

  • 1975: Bill Gates and Paul Allen developed a BASIC interpreter for the MITS Altair 8800, leading to the founding of Microsoft.
  • 1976: Steve Wozniak wrote Integer BASIC for the Apple I, which later became a staple of the Apple II.
  • 1977: BASIC became the de facto standard for the “1977 Trinity” of home computers: the Apple II, Commodore PET, and TRS-80.
  • 1979: Atari BASIC was released for Atari 8-bit computers.
  • 1981: IBM PC launched with a BASIC interpreter in its firmware (ROM BASIC) and GW-BASIC for disk-based systems.
  • 1982: The BBC Micro launched with BBC BASIC, which introduced structured programming features like procedures and local variables to home users.
  • 1982: The Commodore 64 (and Sinclair ZX Spectrum) was released, eventually becoming the best-selling computer model, with BASIC as its primary user interface. 

Modern and Visual Era (1990s–Present)

  • 1991: Microsoft released Visual Basic, which introduced a graphical “drag-and-drop” interface for building Windows applications, revitalising the language for professional use.
  • 2001: Visual Basic .NET was released, fully integrating BASIC into the modern object-oriented .NET framework.
  • Modern Day: Various modern dialects exist, such as Xojo, FreeBASIC, and QB64, while legacy-style BASIC remains popular in the hobbyist “retro-computing” community. 

Key Insights into BASIC

  • Democratisation of Coding: Before BASIC, programming required knowledge of complex assembly or scientific languages like FORTRAN. BASIC used simple English commands like PRINT, GOTO, and IF...THEN to make coding accessible to everyone.
  • Immediate Feedback: Unlike “batch processing” where users waited hours for results, BASIC was designed for interactive use, providing immediate error messages and results.
  • Hardware Efficiency: Early BASIC versions were highly optimised to fit into the tiny memories (often as little as 4 KB) of 1970s microcomputers.
  • Cultural Impact: An entire generation of software engineers began by typing BASIC code into their home computers from hobbyist magazines.

BASIC (Beginners’ All-purpose Symbolic Instruction Code), first released in 1964, was designed to make computing accessible to non-scientists. While modern programming has evolved, the core technical insights and approaches remain the foundation for all software development. 

Technical Insights: The Building Blocks

Programs are constructed using universal building blocks that dictate how a machine processes data: 

  • Variables & Data Types: Containers that store values (e.g., integers, strings).
  • Control Flow (The Logic):
    • Sequence: The specific order in which instructions are executed.
    • Selection: Conditional “if-else” statements that determine the program’s path based on criteria.
    • Iteration (Loops): Repeating a section of code (e.g., FOR or WHILE loops) until a condition is met.
  • Functions & Subroutines: Blocks of reusable code designed to perform specific tasks, improving organization and readability.
  • Syntax: The “grammar” of a language (keywords, operators, punctuation) that must be followed for the machine to understand instructions. 

General Programming Approach

Mastering programming requires a systematic method for solving problems rather than just memorizing code. 

  1. Understand the Problem: Identify the necessary inputs, desired outputs, and any constraints before writing a single line of code.
  2. Design the Algorithm: Break the problem into smaller, manageable steps. Using flowcharts or pseudocode helps map out the logic without getting bogged down in syntax.
  3. Implementation: Translate your plan into the chosen language (e.g., Python, C++, or JavaScript).
  4. Test & Debug: Execute the code with sample data to ensure accuracy. Debugging is the process of identifying and fixing errors when the output doesn’t match expectations.
  5. Refine & Optimize: Improve the performance and maintainability of your code by reducing steps or using more efficient data structures.

COBOL Programming Overview & Detailed Timeline History by Era and Year

COBOL, (COmmon Business-Oriented Language) is a high-level, compiled programming language designed specifically for business, finance, and administrative systems. Developed as a portable “stopgap” for the US Department of Defense, it has endured for over 65 years and remains the backbone of global financial infrastructure. 

Programming Overview

  • Design Philosophy: It features a “prose” syntax designed to be self-documenting and readable by non-technical business professionals.
  • Structure: Programs are strictly divided into four Divisions:
    1. Identification: Defines the program name and metadata.
    2. Environment: Specifies the physical computer and files used.
    3. Data: Defines variables, structures, and record layouts.
    4. Procedure: Contains the logic and executable statements.
  • Core Paradigms: Originally strictly procedural and imperative, COBOL was updated in 2002 to include object-oriented features.
  • Key Characteristics: It is known for its verbosity (using over 300 reserved words), weak/static typing, and exceptional reliability in large-scale batch and transaction processing. 

Detailed Historical Timeline

Era 1: The Foundation (1950s)

This era focused on consolidating disparate manufacturer-specific languages into a single, hardware-independent standard for business. 

  • 1955: Grace Hopper develops FLOW-MATIC, which introduced English-like commands and influenced COBOL’s design.
  • 1958: IBM releases COMTRAN, another major precursor focused on commercial translation.
  • 1959 (April): Mary Hawes organizes a meeting at the University of Pennsylvania to propose a common business language.
  • 1959 (May): The Pentagon hosts a meeting creating CODASYL (Committee on Data Systems Languages) to oversee the project.
  • 1959 (December): The first specifications, “COBOL – Specifications for a COmmon Business Oriented Language,” are released. 

Era 2: Early Versions & Rapid Adoption (1960–1967)

The language quickly transitioned from a theoretical specification to a functioning industry standard. 

  • 1960: COBOL-60 is officially published.
  • 1960 (August): The first COBOL program runs on an RCA 501.
  • 1961: COBOL-61 is released, providing a major cleanup of original logical flaws.
  • 1962: IBM announces COBOL as its primary development language, ending work on COMTRAN.
  • 1963: COBOL-61 Extended is released, introducing “Sort” and “Report Writer” facilities.
  • 1965: COBOL Edition 1965 adds mass storage file handling and table processing.

Era 3: Standardization & Dominance (1968–1984)

COBOL became the most widely used language in the world as ANSI and ISO codified its rules. 

  • 1968: COBOL-68 (ANSI X3.23-1968) is published as the first official US standard.
  • 1970: COBOL becomes the world’s most widely used programming language.
  • 1974: COBOL-74 is standardized, introducing the DELETE statement and file organization improvements.
  • 1978: ISO formally adopts the COBOL-74 standard. 

Era 4: Structured Programming & Modernization (1985–2001) 

The language evolved to support better logic flow while managing the massive global codebase. 

  • 1985: COBOL-85 introduces structured programming features like END-IF, EVALUATE, and nested subprograms.
  • 1989: First amendment to COBOL-85 adds Intrinsic Function Modules.
  • 1997: Gartner Group estimates 200 billion lines of COBOL code are in existence.
  • 1999: Massive effort peaks to patch legacy COBOL code for the Y2K (Year 2000) problem. 

Era 5: The Object-Oriented & Modern Era (2002–Present)

Recent updates focus on interoperability with modern web and cloud environments. 

  • 2002: COBOL-2002 introduces Object-Oriented Programming (OOP), Unicode support, and recursion.
  • 2014: COBOL-2014 standardizes IEEE 754 data types and method overloading.
  • 2020: The COVID-19 pandemic highlights a critical shortage of COBOL programmers to maintain aging state unemployment systems.
  • 2023: COBOL-2023 adds asynchronous messaging (SEND/RECEIVE) and transaction processing (COMMIT/ROLLBACK).
  • 2024: COBOL celebrates its 65th anniversary of active service.

COBOL Programming Overview & Detailed Timeline History by Era and Year

TAL & PTAL Programming Language on Tandem HPE NonStop

Tandem TAL (Transaction Application Language) is a block-structured, procedural language designed in the mid-1970s for Tandem’s NonStop fault-tolerant operating systems, optimized for systems programming, high-reliability OLTP, and direct hardware interaction. It is heavily influenced by ALGOL and HP 3000 systems, allowing high-performance, message-based applications, and remains supported on modern HP Enterprise NonStop x86-64 platforms. 

Tandem TAL Programming certificate back in 1995, Mark Whitfield

Overview of TAL Programming

  • Purpose: Developed to run on Tandem’s GUARDIAN operating system to build highly available, fault-tolerant transactional systems.
  • Characteristics: Procedural, block-structured, efficient (closer to assembly than C), and designed for speed and direct memory access, according to a NonStop Insider article.
  • Features: Strong support for data manipulation, process management, and message-based IPC (Inter-Process Communication) necessary for node-to-node replication, as described on the Wikipedia page on Tandem Computers.
  • Relation to TACL: While TAL is for creating compiled applications, TACL (Tandem Advanced Command Language) is the interpreter/macro language used for command procedures and system interaction, as explained in a Scribd document. 

Historical Timeline of TAL

  • 1975–1976 (Founding Era): TAL is created for the first Tandem/16 system shipped in 1976, heavily utilizing expertise from HP 3000 systems programming, according to a personal blog post.
  • Early 1980s (Expansion): TAL becomes the standard for ATM networks and banking systems, requiring high-reliability code, as seen in this blogger.com article.
  • 1985 (Evolution): TAL is used to build complex OLTP environments, distinguishing it from nascent PC markets as noted in archived Tandem press clippings.
  • 1990s (Native TAL): Introduction of “Native” TAL (T/TAL) to handle new architecture requirements and move from 16-bit to 32-bit environments, according to a TAL Programmer’s Guide document.
  • 1997 (Compaq Merger): Tandem is acquired by Compaq; TAL continues as the core systems language.
  • 2001 (HP Merger): Tandem (via Compaq) is acquired by HP, bringing TAL to the HP Integrity (Itanium) platform.
  • 2010s–Present (Modernization): TAL applications are ported to HP Enterprise NonStop x86-64, with support for running TAL programs on Intel processors and in virtualized instances, according to a NonStop Insider article. 

Present Day

  • TAL remains essential for maintaining legacy systems, but new applications often utilize C/C++ or Java on the modern NonStop platform, as noted in the Wikipedia page on Transaction Application Language.
  • TAL applications are still relevant due to the “single system image” and fault-tolerance features that define the current NonStop environment, according to the NonStop Insider article. 

PTAL Overview and Timeline

Tandem PTAL (Portable Transaction Application Language) is a block-structured, procedural systems programming language used on HPE NonStop (formerly Tandem) servers. It is the portable successor to the original TAL (Transaction Application Language), designed to allow high-level systems programming without an assembler while maintaining near-machine efficiency. 

Overview: TAL, PTAL, and epTAL

The language evolved to support different processor architectures over Tandem’s 50-year history: 

  • TAL (Original): Designed for the 16-bit CISC stack machine architecture (TNS). It has the syntax of ALGOL/Pascal but the low-level semantics of C.
  • PTAL (Portable): Introduced during the migration to MIPS RISC processors (TNS/R). It removed machine-specific constructs to allow code to be compiled into native RISC instructions.
  • epTAL (Extended): Developed for the migration to Intel Itanium processors (TNS/E). 

Historical Timeline by Year

Year Milestone

1974, Tandem Computers founded by James Treybig; initial design of the Tandem/16 hardware begins.

1976, TAL released. The Tandem/16 (NonStop I) ships with TAL as its only programming language.

1981, NonStop II introduced, adding 32-bit addressing support to TAL via an “extended data segment”.

1983, NonStop TXP launched; first major reimplementation of the instruction set architecture supported by TAL.

1986, NonStop VLX introduced with 32-bit data paths; NonStop SQL released, often managed via TAL-based systems.

1989, NonStop Cyclone released, the high-end mainframe competitor for the TAL environment.

1991, PTAL Development starts with the release of Cyclone/R, the first MIPS-based machine. TAL code is initially translated via an “Accelerator” tool before native PTAL compilers take over.

1993, Himalaya K-series released; native mode operating system (NSK) and native compilers (PTAL) become standard.

1997, Compaq acquires Tandem. Migration begins from MIPS to Alpha (later abandoned).

2002, HP merges with Compaq. Development focuses on the Itanium (TNS/E) architecture.

2005, epTAL introduced for the new Integrity NonStop i servers based on Intel Itanium microprocessors.

2014, x86 Migration. NonStop X (TNS/X) systems are released, transitioning the TAL/PTAL environment to Intel x86-64 processors.

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

RTLX by Insider Technologies, Overview and Timeline by Year

Insider Technologies RTLX is a real-time monitoring and tracking solution designed to provide end-to-end visibility for high-volume electronic payments and transactional processes. It specifically ensures that every stage of a payment—from the initial card “tap” at a point-of-sale (POS) terminal to the final movement of funds from an account—is monitored to maintain operational continuity. 

RTLX Overview

  • Function: Real-time transaction and payment monitoring.
  • Platforms: Runs on HP NonStop, Windows, Linux, and Unix.
  • Core Value: Simplifies “Big Data” for IT operations by alerting teams to potential failures before they impact consumers (e.g., preventing ATM or online banking outages).
  • Key Use Case: Used by major financial institutions like the Bank of England and Royal Bank of Scotland for settlement and transaction security. 

RTLX Historical Timeline

The development of RTLX is closely tied to Insider Technologies’ growth as a specialist in mission-critical HP NonStop environments. 

EBUG Conference, Mark Whitfield – Product Manager

The Foundational Era (1989–2000)

  • 1989: Insider Technologies Limited is founded in Manchester, UK, by IT industry veterans.
  • 1990s: The company establishes its “DNA” in the HP NonStop (Tandem) platform, developing core products like MultiBatch and Reflex.
  • 1995: Insider begins a period of rapid growth, providing technical support for critical UK financial infrastructure, including Euroclear (formerly CRESTCo), which settles 88% of UK equities. 

The Expansion Era (2001–2014)

  • 2002: Launch of the state-of-the-art Systems Training Platform, featuring 4x patented cloning technology for hyper-realistic simulations.
  • 2004–2013: Development of the Reflex suite (Reflex 80:20 and Reflex ONE24) and the introduction of Sentra and RTLX Reactor monitoring products.
  • 2014: Insider expands its product initiatives to include diagnostic and trending solutions for real-time electronic payments, solidifying the role of RTLX in global banking. 

The Acquisition & Integration Era (2015–Present)

  • 2015: ETI-NET acquires Insider Technologies on 1 July, integrating its monitoring expertise with ETI-NET’s mainframe storage and backup solutions.
  • 2019: Insider celebrates its 30th year of operations, highlighting RTLX’s role in monitoring modern POS and “tap” payment systems.
  • 2023–Present: Insider becomes part of the PartnerOne group, a global family of mission-critical software companies, further scaling its threat detection and real-time monitoring capabilities. 

RTLX by Insider Technologies, Overview and Timeline by Year

IT Project Testing Techniques

IT Project Testing Techniques

Successful Project Plan

Successful Project Plan

Agile Scrum compared to Kanban

Agile Scrum compared to Kanban

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

Agile Scrum Sprint 0 Zero Setup for Success

Agile Scrum Sprint Zero 0 Setup for Success

Project Phases, Scrum Master & Project Manager Checklist

Project Phases, Scrum Master & Project Manager Checklist

Roger Federer Overview and Historical Timeline by Era and Year

Roger Federer is a Swiss former professional tennis player who is widely regarded as one of the greatest athletes in history. His 24-year career (1998–2022) is defined by a “deadly combination of power and grace,” characterized by an effortless one-handed backhand and fluid movement. He won 20 Grand Slam singles titles, including a record eight at Wimbledon, and held the world No. 1 ranking for 310 weeks, including a record 237 consecutive weeks. 

Historical Career Timeline

Era 1: Junior Years and Professional Transition (1992–2002) 

Before his global dominance, Federer was a temperamental junior who transformed into a top-ten professional. 

  • 1992–1993: Served as a ballboy at the Swiss Indoors in his hometown of Basel.
  • 1995: Accepted into the Swiss Tennis national development programme at age 14.
  • 1998: Won the Wimbledon junior singles and doubles titles; finished the year as the world’s No. 1 junior. Made his ATP debut at the Swiss Open Gstaad.
  • 1999: Became the youngest player (18 years, 4 months) to end the year in the top 100.
  • 2000: Reached the bronze-medal match at the Sydney Olympics (finished 4th) and met his future wife, Mirka Vavrinec.
  • 2001: Gained international fame by defeating defending champion Pete Sampras at Wimbledon to reach his first major quarter-final. Won his first ATP title in Milan.
  • 2002: Ended the year ranked No. 6 globally; qualified for his first year-end Masters Cup (ATP Finals). 

Era 2: Unrivalled Dominance (2003–2007) 

Federer established a “Golden Era,” reaching all four Grand Slam finals in a single year three times during this period (2006, 2007, 2009). 

  • 2003: Won his first Grand Slam title at Wimbledon, defeating Mark Philippoussis.
  • 2004: Won three Grand Slams (Australian Open, Wimbledon, US Open) and became world No. 1 for the first time on 2 February, a position he would not relinquish for 237 weeks.
  • 2005: Defended his Wimbledon and US Open titles.
  • 2006: Arguably his greatest season, winning three majors and reaching the final of the fourth (French Open); finished with a 92–5 match record.
  • 2007: Reached all four Grand Slam finals again, winning three. Defeated Novak Djokovic in the US Open final to claim his 12th major.

Era 3: Rivalries and Record-Breaking (2008–2012) 

As rivals Rafael Nadal and Novak Djokovic emerged, Federer achieved his most significant career milestones. 

  • 2008: Battled mononucleosis but won a fifth consecutive US Open. Won Olympic Gold in doubles with Stan Wawrinka.
  • 2009: Completed the Career Grand Slam by winning the French Open and broke Pete Sampras’s record of 14 majors by winning his 15th at Wimbledon.
  • 2010: Won his fourth Australian Open.
  • 2011: The first year since 2002 he did not win a major title, despite ending Djokovic’s 43-match win streak at the French Open.
  • 2012: Won a record-equalling 7th Wimbledon title, returned to world No. 1, and won Olympic Silver in singles at the London Games. 

Era 4: Injury Struggles and Late Renaissance (2013–2019) 

After several years of injury and titles eluding him, Federer staged a historic comeback. 

  • 2013–2016: Plagued by back and knee injuries. Underwent knee surgery in 2016 and missed the second half of that season, dropping out of the top 10 for the first time in 14 years.
  • 2017: Returned from a 6-month layoff to win the Australian Open (defeating Nadal) and a record 8th Wimbledon title without dropping a set.
  • 2018: Won his 20th and final Grand Slam title at the Australian Open and became the oldest world No. 1 in history at age 36.
  • 2019: Won his 100th career title (Dubai) and reached his 12th Wimbledon final, losing an epic 5-set match to Djokovic despite holding championship points. 

Era 5: Retirement (2020–2022) 

  • 2020–2021: Limited by multiple knee surgeries. Played his final Grand Slam match at Wimbledon 2021, reaching the quarter-finals.
  • 2022: Announced his retirement in September. Played his final match—a doubles pairing with Rafael Nadal—at the Laver Cup in London.

Roger Federer Overview and Historical Timeline by Era and Year

Roger Federer career statistics

…with hyperlinks

Roger Federer‘s professional career spanned 24 years, from his ATP debut in 1998 to his emotional retirement at the Laver Cup on 23 September 2022. He concluded his career with 103 singles titles and 20 Grand Slam championships, including a record eight Wimbledon titles. 

Career Timeline (1998–2022)

  • 1998: Professional Debut
    • Federer made his ATP debut at the Swiss Open Gstaad.
    • Won the Wimbledon junior singles and doubles titles.
  • 2001: Breakthrough Victory
    • Defeated defending champion Pete Sampras at Wimbledon, ending Sampras’s 31-match win streak and reaching his first major quarter-final.
  • 2003: First Grand Slam Title
  • 2004: Ascending to World No. 1
    • Won the Australian Open, Wimbledon, and US Open.
    • Became World No. 1 for the first time on 2 February, beginning a record-breaking streak of 237 consecutive weeks at the top.
  • 2006: The “Career-Best” Season
    • Reached the final of all four Grand Slams, winning three of them (Australian Open, Wimbledon, US Open) and finishing the year with 12 titles and a 92–5 record.
  • 2008: Olympic Gold
  • 2009: Career Grand Slam
    • Won the French Open to complete his Career Grand Slam and equaled Pete Sampras’s then-record of 14 major titles.
    • Secured his 15th major title at Wimbledon shortly after.
  • 2012: Olympic Silver & No. 1 Return
    • Won an eighth Wimbledon title and reclaimed the World No. 1 ranking.
    • Earned an Olympic silver medal in singles at the London Games.
  • 2014: Davis Cup Triumph
    • Led Switzerland to its first-ever Davis Cup title, defeating France in the final.
  • 2017: The Renaissance
    • After a six-month injury hiatus, won the Australian Open and a record eighth Wimbledon title.
  • 2018: 20th Grand Slam & Oldest No. 1
  • 2022: Retirement
    • Announced his retirement on 15 September.
    • Played his final competitive match in doubles alongside Rafael Nadal at the Laver Cup in London.

HP NonStop MultiBatch Overview and Historical Timeline

HP NonStop MultiBatch is a “mainframe-class” workload automation and batch scheduling manager developed by Insider Technologies (distributed by ETI-NET). It is designed specifically for the HPE NonStop (formerly Tandem) platform to automate, manage, and secure complex batch processing across both Guardian and OSS environments. 

Product Overview

While the native NonStop scheduler is NetBatch, MultiBatch is positioned as a modern, high-performance alternative that provides deeper integration with the NonStop architecture. 

  • Workload Automation: Manages thousands of concurrent jobs with sophisticated calendaring and dependency tracking.
  • Architecture: Built to leverage NonStop’s fault tolerance and linear scalability, allowing batch schedules to execute across multiple networked nodes.
  • Interfaces: Modernized from command-line tools to a suite of role-based Graphical User Interfaces (GUIs) for operations and management.
  • Security: Includes a secure, audited environment with full support for NonStop-specific security attributes like High-PIN and CPU selection. 

Historical Timeline by Era

The evolution of MultiBatch is closely tied to the history of the Tandem/NonStop platform, which spans over 50 years of ownership changes and architectural shifts. 

1. The Tandem Era (1974 – 1997)

  • 1974: Tandem Computers founded by James Treybig to build the first fault-tolerant commercial systems.
  • Late 1980s – Early 1990s: MultiBatch originated during this period (reportedly in the early 1990s) to address the needs of large financial institutions requiring complex batch schedules beyond the capabilities of the original NetBatch.
  • 1991: Release of the Cyclone/R and the start of the migration from proprietary stack machines to MIPS RISC processors. 

2. The Compaq & Early HP Era (1997 – 2014)

  • 1997: Compaq acquires Tandem.
  • 2002: Hewlett-Packard (HP) merges with Compaq. The NonStop platform begins its migration from MIPS to Intel Itanium (branded as Integrity NonStop).
  • Mid-2000s: MultiBatch matures as a mission-critical tool for global banks and stock exchanges. Development focuses on MultiBatch 7 and 8, enhancing GUI capabilities and adding support for Open System Services (OSS). 

3. The Modern HPE Era (2014 – Present)

  • 2014: NonStop X is introduced, moving the architecture from Itanium to Intel x86-64.
  • 2015: Hewlett-Packard splits into HP Inc. and Hewlett Packard Enterprise (HPE).
  • 2018 – 2020: MultiBatch 9.5 is released with an enhanced GUI. It increasingly becomes the primary alternative as HPE shifts focus away from active sales of the legacy NetBatch product.
  • 2023 – 2024: Release of MultiBatch 10, introducing “Define Classes,” support for up to 2,500 jobs, and improved OSS process handling. This era focuses on “modernisation through tradition,” aligning with HPE’s push for virtualized NonStop and hybrid cloud deployments. 

MediaCityUK Photo Journal and Historical Timeline, Salford Quays

Mark Whitfield is a photographer who has documented the development of MediaCityUK in Salford Quays through an extensive “Photographic Build Timeline Journal”. His collection includes over 15,000 images that capture the site’s transformation from a derelict dockland into a global media hub. 

MediaCityUK Photo Timeline

Mark Whitfield: Photography Overview

  • Project Focus: Whitfield began documenting the rise of MediaCityUK in May 2007, specifically focusing on the construction of the BBC’s new northern home.
  • Visual Documentation: His work is described as a unique photo timeline that charts the incredible structural changes at the site over several years.
  • Background: Beyond his photography, Whitfield has a background in IT project management and has worked in Salford Quays for over 15 years.
  • Galleries: Much of his work is hosted on his personal website, mark-whitfield.com, and he has shared specific milestones on platforms like Flickr and Instagram. 
MediaCityUK site in 2007

Historical Timeline of MediaCityUK

The following timeline integrates key development milestones with Whitfield’s photographic journey:

  • 2004–2006: Pre-Construction Phase
    • The BBC signals its intention to move jobs to Manchester (2004).
    • Salford Quays is officially chosen as the site for the new development (June 2006).
  • 2007: Construction Begins
    • May 18, 2007: Mark Whitfield captures his first timeline photo, marking the start of the build.
    • The first “spade in the ground” occurs as Peel Group and Bovis Lend Lease begin work.
    • The Pie Factory, a refurbished bakery, opens as the first working studio complex.
  • 2008–2009: Structural Growth
    • Whitfield continues extensive documentation; photos from April 2008 and February 2009 capture the rising concrete frames of the main buildings.
    • The high-rise 2,116-space multi-storey car park is completed (August 2009).
  • 2010: Infrastructure Milestones
    • The MediaCityUK Metrolink station opens (September 20), connecting the site to the wider Manchester tram network.
    • First trial show is recorded in Studio HQ2 (November), featuring a simulated power failure and evacuation.
    • Initial infrastructure is completed by December.
  • 2011: Operational Launch
    • January 2011: Dock10 studios become operational.
    • February 2011: The first program, Don’t Scare the Hare, is filmed at MediaCityUK.
    • May 2011: BBC staff begin moving into three dedicated buildings: Bridge House, Dock House, and Quay House.
    • October 2011: The University of Salford opens its new media academy at the site.
  • 2012–2014: Full Integration
    • April 2012: The Queen and Duke of Edinburgh officially open MediaCityUK.
    • March 2013: ITV completes its move to the site.
    • January 2014: Coronation Street records its first episode at the new production facility on Trafford Wharf.
  • 2015–2021: Expansion & Sustainability
    • 2016: Completion of “Tomorrow,” the final building in Phase One.
    • 2020: The Pie Factory closes and is demolished to make way for Phase Two.
    • 2021: MediaCityUK buildings become the first in the UK to achieve net-zero carbon status. 
MediaCityUK building beginning to take shape in late 2008

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

History of the x86 IBM PC platform by Era and Year

The history of the x86 IBM PC platform is defined by a shift from a proprietary IBM product to an open industry standard (“Wintel”) and finally to the modern diverse ecosystem of high-performance computing. 

Era 1: The Foundation & The “Big Blue” Monopoly (1978–1981)

Before the first PC, the building blocks of the x86 architecture were established by Intel. 

  • 1978: Intel introduces the 8086 microprocessor, the 16-bit foundation of the x86 instruction set.
  • 1979: Intel releases the 8088, a lower-cost version with an 8-bit external bus, which IBM would later choose for its first PC.
  • 1980: Microsoft signs a contract with IBM to develop an operating system (MS-DOS/PC DOS) for their upcoming machine.
  • 1981 (August 12): IBM announces the IBM Personal Computer (Model 5150).
    • Spec highlights: 4.77 MHz 8088 CPU, 16KB–256KB RAM, and CGA graphics.
    • Impact: Its “open architecture” allowed third-party expansion, though the BIOS remained proprietary. 

Era 2: The Rise of the Clones (1982–1986) 

IBM’s dominance was quickly challenged as other companies “cloned” the hardware and reverse-engineered the BIOS. 

  • 1982: Columbia Data Products introduces the MPC 1600, the first 100% IBM PC compatible.
  • 1982: Intel announces the 80286, supporting protected mode and up to 16MB of RAM.
  • 1983: Compaq releases the Compaq Portable, the first highly successful 100% compatible clone with a clean-room engineered BIOS.
  • 1983: IBM launches the PC/XT (Model 5160), the first PC with a built-in hard drive.
  • 1984: IBM introduces the PC/AT (Model 5170) using the 80286 chip, which sets the standard for PC architecture for the next decade.
  • 1985: Intel introduces the 80386, the first 32-bit x86 processor.
  • 1986: Compaq beats IBM to market with the first 386-based PC, the Deskpro 386, signalling IBM’s loss of control over the platform’s technical lead.

Era 3: The “Wintel” Standard & Multimedia (1987–1999)

As IBM tried and failed to regain control with proprietary standards, Microsoft and Intel became the new “de facto” leaders. 

  • 1987: IBM launches the PS/2 line with the proprietary MicroChannel Architecture (MCA), but the industry rejects it in favour of the open AT-bus (ISA).
  • 1989: Intel releases the 486DX, integrating the math co-processor and L1 cache onto the chip.
  • 1993: Intel debuts the Pentium processor, moving away from numbers to a trademarked brand to prevent competitors from using the name.
  • 1995: Windows 95 is released, cementing the GUI as the standard interface for x86 PCs.
  • 1997: Intel launches MMX technology to improve multimedia performance on PCs. 

Era 4: 64-Bit & Multi-Core (2000–2019)

The platform evolved to handle massive data and professional workloads through architectural shifts. 

  • 2003: AMD introduces x86-64, the 64-bit extension that Intel eventually adopts as the industry standard.
  • 2005: Intel ships its first dual-core processor, starting the “core war” to improve performance without increasing heat.
  • 2005: IBM exits the PC market entirely, selling its division to Lenovo.
  • 2006: Apple transitions its Macintosh line to Intel x86 processors (a move that lasted until 2020).
  • 2011: The 30th anniversary of the IBM PC; by this time, “PC” almost exclusively meant an x86 machine running Windows. 

Era 5: The Modern Era (2020–Present)

Current x86 systems focus on massive core counts, high-speed storage (NVMe), and integrated AI. 

  • 2020–2022: Development of high-performance multi-core architectures like Intel’s 12th Gen (Alder Lake), introducing hybrid performance and efficiency cores.
  • 2025–2026: Transition to “AI PCs” using processors like the Intel Core Ultra series (Series 2), which include NPUs (Neural Processing Units) for local AI workloads.
  • Today: Modern x86 PCs, such as those from Dell or Lenovo, feature 20+ cores, DDR5 memory, and PCIe 5.0 expansion.

History of the x86 IBM PC platform by Era and Year

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)

Solution Architect, must know items

Solution Architect, must know items

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