Author: Mark Whitfield

Welcome to my site! After graduating in Computing in 1990, I accepted a position as a programmer at a Runcorn based software house specialising in electronic banking software, namely sp/ARCHITECT-BANK on Tandem Computers (now HPE NonStop). This was before the internet became more prevalent and so the notion of enabling desktop access to company accounts for inter-account transfers and book keeping was still quite a cutting edge idea (and smartphones only ever hinted at in Space 1999). The company was called The Software Partnership (which was taken over by Deluxe Data in 1994). I spent 5 years in Runcorn developing code for SP/ARCHITECT for various banks like TSB, Bank of Scotland, Rabobank and Girofon (Denmark) to name but a few. I then moved onto a software house in Salford Quays for further bank facing projects. After a further 23 years in the IT industry and now a Senior IT Project Manager (both Agile and Waterfall delivery), I thought I would echo out my Career Profile in this corner of the internet for quick and easy access.

Agile Development Overview and Detailed Timeline by Era

Agile development is an iterative and incremental approach to project management and software delivery that prioritises flexible planning, frequent delivery of working software, and rapid response to change. At its core, Agile seeks to shorten work cycles to deliver value to customers quickly while using frequent feedback to improve quality. 

Core Overview

The foundation of modern Agile is defined by the Agile Manifesto (2001), which establishes four central values: 

  • Individuals and interactions over processes and tools.
  • Working software over comprehensive documentation.
  • Customer collaboration over contract negotiation.
  • Responding to change over following a plan. 

The Agile life cycle typically moves through six phases: Concept, Inception, Iteration, Release, Maintenance, and Retirement. 

Comprehensive Timeline of Agile Development

Agile did not emerge in a vacuum; it evolved from early 20th-century industrial concepts and decades of experimentation in software engineering. 

Era 1: The Industrial & Theoretical Roots (1910s – 1960s)

This era established the foundational concepts of efficiency, waste reduction, and iterative cycles that would later inform Agile frameworks. 

  • 1911: Frederick Taylor publishes The Principles of Scientific Management, advocating for managers to analyse and adopt worker-led process improvements.
  • 1930s: Walter Shewhart at Bell Labs develops the Plan-Do-Check-Act (PDCA) cycle, a groundbreaking iterative methodology for quality control.
  • 1948: Toyota formalises the Toyota Production System (Lean), introducing concepts like Kaizen (continuous improvement) and Just-in-Time manufacturing.
  • 1957: Gerald Weinberg and others at IBM begin using incremental development on projects.
  • 1958: NASA’s Project Mercury uses half-day iterations and test-first development, marking one of the earliest high-stakes uses of iterative cycles.

Era 2: Evolutionary Alternatives to Waterfall (1970s – 1980s) 

As the rigid Waterfall model became dominant, practitioners began developing “lightweight” alternatives to handle complex, shifting requirements. 

  • 1970s: Barry Boehm proposes Wideband Delphi, an early forerunner to Planning Poker.
  • 1976: Tom Gilb publishes the Evolutionary Delivery Model (Evo), perhaps the first explicitly named incremental alternative to Waterfall.
  • 1980: Toyota introduces Visual Control, the predecessor to Agile “information radiators” like Kanban boards.
  • 1986: Hirotaka Takeuchi and Ikujiro Nonaka publish “The New New Product Development Game” in Harvard Business Review, introducing the “rugby” approach that inspired the Scrum framework.
  • 1988: Barry Boehm formalises the Spiral Model, an iterative model focused on identifying and reducing risks. 

Era 3: The Proliferation of Frameworks (1990 – 2000) 

This decade saw a “crisis” in software development where traditional methods failed to keep up with the personal computing boom, leading to the birth of modern frameworks. 

  • 1991: James Martin publishes Rapid Application Development (RAD), formalising the use of timeboxing and iterations.
  • 1993: Jeff Sutherland and team at Easel Corporation first implement Scrum as a formal process.
  • 1994: The Dynamic Systems Development Method (DSDM) is created as a non-profit consortium to provide a framework for RAD.
  • 1995: Ken Schwaber and Jeff Sutherland co-present the Scrum methodology at the OOPSLA conference.
  • 1996: Kent Beck creates Extreme Programming (XP) while working on the Chrysler Comprehensive Compensation (C3) project.
  • 1997: Jeff De Luca introduces Feature-Driven Development (FDD).
  • 1999: Kent Beck publishes Extreme Programming Explained, popularising many engineering practices like pair programming.

Era 4: The Manifesto & Mainstream Adoption (2001 – 2010)

Agile shifted from a niche experimental approach to a global industry standard. 

  • 2001 (Feb): 17 developers meet at Snowbird, Utah, and author the Manifesto for Agile Software Development.
  • 2001 (Post): The Agile Alliance is formed to promote the manifesto’s values.
  • 2003: Mary and Tom Poppendieck publish Lean Software Development, formally linking Lean manufacturing principles to Agile.
  • 2005: Mike Cohn introduces Planning Poker in Agile Estimating and Planning.
  • 2007: The Scaled Agile Framework (SAFe) is introduced by Dean Leffingwell to apply Agile to large enterprises.
  • 2009: The concept of DevOps emerges, seeking to bridge the gap between Agile development and IT operations. 

Era 5: Scale, Transformation, and Modern Evolution (2011 – Present)

Agile has expanded beyond software into marketing, HR, and education, becoming a “culture” rather than just a tool. 

  • 2011: The Project Management Institute (PMI) introduces the Agile Certified Practitioner (PMI-ACP).
  • 2012–2015: Agile adoption surpasses 50% in the development world as success metrics become undeniably clear.
  • 2017: AXELOS updates PRINCE2 to make agility a core focus of the project management standard.
  • 2020s: Continued evolution toward “Business Agility,” where entire organisations adopt Agile mindsets to survive rapidly changing market conditions. 

Agile Development Overview and Detailed Timeline by Era

HP NonStop Tandem Overview and Timeline History by year

HP NonStop is a series of fault-tolerant server computers designed for online transaction processing (OLTP) and mission-critical applications that require 100% uptime. Originally introduced by Tandem Computers Inc. in 1976, the platform uses a proprietary, integrated hardware and software stack known as NonStop OS (formerly Guardian) to eliminate single points of failure through massive redundancy and “fail-fast” logic. 

Historical Timeline by Era

1. The Tandem Founding Era (1974–1981) 

  • 1974: Tandem Computers Inc. is founded by James (Jimmy) Treybig and a team from Hewlett-Packard’s HP 3000 division.
  • 1976: The first system, the Tandem/16 (later NonStop I), is shipped to Citibank.
  • 1977: Tandem systems gain early traction as intelligent front-end processors for bank ATM networks. 

2. The Stack Machine Expansion (1981–1990) 

  • 1981: NonStop II is introduced, adding 32-bit addressing capabilities and replacing magnetic core memory with battery-backed DRAM.
  • 1983: NonStop TXP (Transaction Processing) launches as the first new implementation of the architecture, featuring cache memory and 2.0 MIPS performance.
  • 1986: Introduction of NonStop VLX (Very Large eXpansion) and NonStop SQL, the first fault-tolerant relational database designed for linear scalability.
  • 1987: NonStop CLX launches as a lower-cost, compact minicomputer for remote office environments.
  • 1989: NonStop Cyclone is released for high-end mainframe markets, featuring superscalar CPUs and fiber optic interconnects. 

3. The MIPS RISC Transition & Acquisitions (1991–2003)

  • 1991: Cyclone/R (or CLX/R) marks the move to MIPS R3000 RISC processors, using object code translation to maintain backward compatibility.
  • 1993: Himalaya K-series is released using MIPS R4400 processors.
  • 1995: Open System Services (OSS) is added to the NonStop Kernel to provide a POSIX/Unix-like environment.
  • 1997: Compaq acquires Tandem Computers. The Himalaya S-Series introduces ServerNet, which later becomes the InfiniBand industry standard.
  • 2002/2003: HP merges with Compaq, bringing the NonStop line under Hewlett-Packard. 

4. The HP Integrity & x86 Era (2005–Present)

  • 2005: HP Integrity NonStop (TNS/E) is introduced, migrating the platform to Intel Itanium microprocessors.
  • 2014: NonStop X (TNS/X) launches, shifting the architecture to Intel x86-64 processors for greater industry-standard alignment.
  • 2015: Following the HP corporate split, NonStop becomes part of Hewlett Packard Enterprise (HPE).
  • 2020: Sales of Itanium-based systems officially end in July 2020.
  • 2024–2025: HPE expands the platform with Virtualized NonStop Software for private clouds and consumption-based models via HPE GreenLake.

HP NonStop Tandem Overview and Timeline History by year

HPE NonStop (formerly Tandem and Compaq NonStop) is a family of fault-tolerant, integrated hardware and software systems designed for mission-critical enterprise workloads. Since its introduction in 1976, it has served as the backbone for high-volume transaction environments like banks, stock exchanges, and payment systems, offering 100% continuous uptime. 

Core Architecture and Features

The platform is defined by its “shared-nothing” architecture, where every component is redundant to eliminate single points of failure. 

  • Continuous Availability: If a hardware or software component fails, a backup takes over immediately without disrupting the application, a process often managed through process pairs (primary and hot backup processes).
  • Linear Scalability: You can add capacity (CPUs, memory) seamlessly without downtime. Systems can scale from a few processors to clusters of over 4,000 CPUs while maintaining a single-system image for management.
  • Integrated Stack: Unlike standard servers, NonStop includes a fully integrated stack of hardware, the NonStop OS (a proprietary kernel), a relational database (NonStop SQL), and middleware.
  • Fail-Fast Design: Modules are self-checking; they stop immediately upon detecting an error to prevent data corruption, allowing the redundant backup to resume processing from the last known good state. 

Current Hardware and Deployment

While historically based on proprietary or Itanium processors, modern NonStop systems (NonStop X) utilize industry-standard Intel Xeon processors and high-speed InfiniBand interconnects. 

  • High-End Systems: Models like the NS9 X5 are built for the most demanding high-volume transaction processing (OLTP).
  • Mid-Range/Entry Systems: Models like the NS5 X5 offer fault tolerance for smaller enterprises or development environments.
  • Virtualization & Cloud: HPE Virtualized NonStop Software allows the platform to run on standard private cloud infrastructure (e.g., VMware, OpenStack), and it is also available via HPE GreenLake as a consumption-based, pay-as-you-go service. 

Software and Security

  • Database: Supports NonStop SQL/MX and SQL/MP for multi-tenant, fault-tolerant data management.
  • Development: Supports modern languages like Java, C++, Python, COBOL, and the TACL scripting language. Developers can use the Eclipse-based IDE for building and debugging applications.
  • Security: Built with Zero Trust principles, including hardware-level vulnerability mitigations (e.g., against Spectre/Meltdown) and real-time threat detection. 

Detailed Architecture

HPE NonStop architecture is a fault-tolerant, shared-nothing, massively parallel computing platform designed for 100% operational continuity. Originally developed by Tandem Computers, it is engineered so that no single hardware or software failure can bring down the system. 

Core Architectural Pillars

  • Shared-Nothing Architecture: Each processor has its own dedicated memory, I/O bus, and copy of the HPE NonStop Operating System (NSK). This eliminates resource contention and single points of failure found in shared-memory systems.
  • Massive Scalability: Systems scale linearly by adding more processors. A single node can support up to 16 CPUs, and multiple nodes can be clustered to support over 4,000 CPUs.
  • Fault Tolerance (Process Pairs): Software availability is maintained through “process pairs”—a primary process and a passive backup process. If the primary fails, the backup immediately takes over without losing data or state.
  • Fail-Fast Design: Hardware and software modules are designed to stop immediately upon detecting an error (“fail-stop”) to prevent data corruption from propagating. 

Hardware Components

  • Compute Nodes: Modern HPE NonStop X systems use standard Intel Xeon x86-64 processors but implement fault tolerance through specialized system interconnects.
  • System Interconnect (Fabric):
    • InfiniBand: Used in NonStop X systems for high-speed, low-latency communication between CPUs and I/O devices (up to 56 Gbps).
    • ServerNet: The legacy high-speed, point-to-point switched fabric used in older S-series and Integrity i-series systems.
  • CLIMs (Cluster I/O Modules): Specialized offload engines for networking (IP CLIM), storage (Storage CLIM), and telco protocols. They handle I/O processing to free up the main host CPUs. 

Integrated Software Stack

The NonStop platform is a “tightly coupled” environment where hardware and software are integrated for availability. 

  • NonStop OS (NSK): A message-based operating system that manages the distributed resources as a single system image.
  • HPE NonStop SQL/MX: A distributed, fault-tolerant relational database that provides ANSI SQL compliance and automatic load balancing across the cluster.
  • HPE Pathway (TS/MP): An application server and middleware framework that manages workload distribution, load balancing, and automatic process restarts.
  • TMF (Transaction Monitoring Facility): Ensures database integrity by managing atomic transactions; if an update fails, TMF automatically rolls back the changes. 

Modern Deployment Options

  • HPE Virtualized NonStop (vNS): The complete software stack decoupled from proprietary hardware, allowing it to run as a set of virtual machines on industry-standard x86 servers within a private cloud (VMware).
  • HPE GreenLake: A consumption-based model providing NonStop capabilities as a cloud-like service. 

Business Analyst typical day example

Business Analyst typical day example

Senior Project Manager vs Project Manager vs Program Manager

Senior Project Manager vs Project Manager vs Program Manager

Back at the Trafford Centre…

Back at the Trafford Centre…

Project Management Plan Components, PMBOK

Project Management Plan Components, PMBOK

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

Artificial Intelligence AI Terms Explained, an Overview

AI Artificial Intelligence Terms Explained, an Overview

Project Management KPIs to track

Project Key Performance Indicators KPIs
Key Performance Indicators KPI overview

Project Management KPIs to track

Roger Federer Overview and Detailed Timeline History by Era

Roger Federer is a Swiss former professional tennis player who is widely regarded as one of the greatest of all time, having won 20 Grand Slam singles titles and held the world No. 1 ranking for 310 weeks. Known for his effortless playing style and versatile shot-making, he revolutionized the sport during a career that spanned over two decades from 1998 to 2022. 

Wimbledon 2007
Won by Roger Federer for the fifth consecutive time, a feat only before achieved in the Open Era by Björn Borg.

Career Overview Statistics

Won by Roger Federer for the 5th time

According to ATP Tour statistics, Federer concluded his career with the following major achievements:

Federer concluded his career with the following major achievements

Detailed Timeline by Era

1. Early Career & Breakthrough (1998–2002)

Federer transitioned from a dominant junior—finishing 1998 as the world No. 1 junior—to a rising star on the ATP Tour. 

  • 1998: Turned professional; won Wimbledon junior singles and doubles titles.
  • 1999: Youngest player to finish the year in the Top 100 (ranked 64th).
  • 2001: Won first ATP title in Milan; defeated 7-time champion Pete Sampras at Wimbledon to reach his first major quarter-final.
  • 2002: Won first Masters title in Hamburg and entered the world Top 10 for the first time. 

2. Peak Dominance Era (2003–2007) 

This period marked Federer’s absolute peak, where he reached all four Grand Slam finals in a single calendar year twice (2006, 2007). 

  • 2003: Won first Grand Slam title at Wimbledon and his first Year-End Championship.
  • 2004: Won three of four majors (Australian Open, Wimbledon, US Open) and became world No. 1 on 2 February.
  • 2006: Career-best season with a 92–5 record, reaching all four major finals and winning three.
  • 2007: Defended three major titles and beat Rafael Nadal to win his fifth consecutive Wimbledon. 

3. The Rivalry Era & Career Slam (2008–2012)

Federer faced intense competition from the emergence of the “Big Four” (Nadal, Djokovic, and Murray). 

  • 2008: Battled mononucleosis; won fifth consecutive US Open; won Olympic Gold in doubles with Stan Wawrinka.
  • 2009: Won first French Open to complete the Career Grand Slam; passed Sampras’ record with a 15th major at Wimbledon.
  • 2010: Won fourth Australian Open.
  • 2012: Won 7th Wimbledon title and Olympic Silver in singles; reclaimed world No. 1 to break the record for total weeks at the top. 

4. Injury Struggles & Renaissance (2013–2019)

After several years plagued by back and knee injuries, Federer staged a remarkable late-career comeback. 

  • 2014: Led Switzerland to its first Davis Cup title.
  • 2016: Underwent first knee surgery; missed the second half of the season for recovery.
  • 2017: Returned after a 6-month hiatus to win the Australian Open (defeating Nadal) and a record 8th Wimbledon title.
  • 2018: Won 20th Grand Slam at the Australian Open; became the oldest No. 1 in history at age 36.
  • 2019: Won 100th career title in Dubai; reached 12th Wimbledon final. 

5. Final Years & Retirement (2020–2022)

Persistent knee issues eventually forced the conclusion of his competitive career. 

  • 2020–21: Underwent multiple knee surgeries; reached Wimbledon quarter-finals in 2021 as the oldest man in the Open Era to do so.
  • 2022: Officially retired on 23 September at the Laver Cup in London, playing his final match in doubles alongside long-time rival and friend Rafael Nadal.

Roger Federer Overview and Detailed Timeline History by Era

Mark Whitfield HP NonStop Tandem experience & Project Management Templates

Mark Whitfield is an experienced IT Project Manager and software developer who has spent over 22 years specialising in HP NonStop (formerly Tandem) systems. He is currently an Engagement Project Manager at Capgemini. 

Career & Expertise

Whitfield’s career in HP NonStop began in 1990 and includes significant technical and leadership roles across the financial and technology sectors: 

  • Software Development: Early in his career, he worked as a programmer for The Software Partnership (later Deluxe Data/FIS), focusing on electronic banking software like sp/ARCHITECT on Tandem mainframes.
  • Insider Technologies (1995–2013): He spent 18 years at Insider Technologies as a Senior Development Engineer and Project Manager. His work involved:
    • Developing monitoring and diagnostic software such as Reflex 80:20, Reflex ONE24, and RTLX (Real-Time Log Extraction) for payment systems.
    • Managing the first HP OpenView Operations Smart Plug-In certification for the NonStop platform.
    • Designing XPERT24, a performance tracking product for ACI’s XPNET layer.
  • Capgemini (2016–Present): As an Engagement Project Manager, he has led digital projects for major clients in the automotive, government, and aerospace sectors, including a cloud migration for UK Government applications. 

Technical Contributions

  • Publications: He has authored articles for globally published journals like The Connection (2013), discussing topics such as querying terabytes of legacy transaction log data from NonStop mainframes.
  • Project History: He has managed high-value projects, including a £5 million initiative to migrate legacy HP NonStop software to AIX-based technologies for a large UK retail bank.
  • Training: He is trained in various NonStop-specific technologies, including TAL (Transaction Application Language), COBOL85, PATHWAY, and NonStop SQL. 

Whitfield also maintains a professional website, mark-whitfield.com, where he provides project management templates and resources related to HP NonStop and Tandem systems. 

Mark Whitfield provides a comprehensive bundle of over 200 editable project management templates designed for Agile, Waterfall, and PRINCE2 methodologies. These templates are based on over 30 years of project delivery experience and are available for purchase via his official website or Etsy shop. 

Key Template Categories

The bundle includes a wide variety of tools across different formats (Excel, PowerPoint, Word, and MS Project): 

  • Planning & Scheduling:
    • Plan on a Page (POaP): Over 30 PowerPoint slide examples for executive-level summaries.
    • Detailed Project Plans: MS Project (MPP) and Excel templates for SDLC, PRINCE2 7th Edition, and Agile Scrum projects.
    • Gantt Charts: Built-in tracking views for both MS Project and Excel.
  • Tracking & Control:
    • RAID Logs: Comprehensive logs for tracking Risks, Actions, Issues, and Dependencies, plus additional tabs for Change Requests and Lessons Learned.
    • RACI Matrix: Templates to define project roles and responsibilities (Responsible, Accountable, Consulted, Informed).
    • Finance Trackers: Tools for internal and external forecast vs. actual costs, including margin and variance tracking.
  • Agile Specific Tools:
    • Burn Down & Burn Up Charts: Excel-based alternatives when tools like Jira are unavailable.
    • Agile Story Dependency Tracking: Specifically for managing dependencies between agile stories and external suppliers.
  • Reporting & Governance:
    • Status Reports: Weekly and monthly templates in Word and PowerPoint formats.
    • Stakeholder Analysis: Power/interest mapping and engagement plan templates.
    • Benefits Realisation: Plans to track project outcomes against initial business goals. 

Purchase Benefits

  • Lifetime Upgrades: Once purchased, all future additions and updates to the template package are provided for free.
  • Compatibility: Templates are designed for Microsoft Office 365 but also include Excel versions compatible with earlier software.
  • Support: The package typically includes walkthrough Word documents to guide users on how to use each major template.

Mark Whitfield HP NonStop Tandem experience & Project Management Templates

Key Skills for the Project Manager

Key Skills for the Project Manager

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

Project Management mindset, 8 thought processes

Project Management mindset, 8 thought processes

Llandudno Pier Overview and Historical Timeline by Era

Llandudno Pier, often called the “Queen of Welsh Piers”, is the longest pier in Wales at 2,295 feet (700 metres). It is a Grade II* listed structure renowned for its Victorian and Edwardian elegance, featuring ornate ironwork and classic kiosks. 

Llandudno Pier, often called the “Queen of Welsh Piers”, is the longest pier in Wales

Historical Timeline by Era

Early Origins (The Pre-Pier Era)

  • 1858: A short wooden pier (242 ft) was built by the St George’s Harbour and Railway Company to export limestone.
  • 1859: This original structure was severely damaged by the “Royal Charter Storm”.
  • 1860–1875: Though repaired, the wooden pier was too short for steamships except at high tide. 

Victorian Era: Construction and Growth

  • 1875: The Llandudno Pier Company was formed to build a new, modern structure.
  • 1876: Construction began in June/July. The first pile was driven on 16 September 1876.
  • 1877: The pier officially opened on 1 August, initially measuring 1,234 feet.
  • 1878: Construction was fully completed; the first steamboat (Prince Arthur) landed in May.
  • 1884: A landward extension was added, bringing the pier to its current length of 2,295 feet.
  • 1886: The Pier Pavilion opened on 16 September as a 2,000-seat theatre and concert hall.
  • 1887: Renowned conductor Jules Rivière took charge of the pier’s orchestra, which eventually grew to symphony proportions.
  • 1891: A new landing stage was added to accommodate increased steamship traffic. 

Edwardian and Mid-20th Century

  • 1905: A pier-head pavilion was constructed.
  • 1910: Extensive improvements were made, including widening most of the pier.
  • 1938: Major alterations were carried out on the landing stage.
  • 1968: The pier was purchased by the Trust House Forte Group.
  • 1969: The landing stage was totally rebuilt in concrete and steel to handle large Isle of Man steamers. 

Modern Era: Challenges and Restoration

  • 1983: The pier became part of the First Leisure Corporation.
  • 1984: The Pier Pavilion theatre closed.
  • 1994: A major fire destroyed the Pier Pavilion on 13 February, leaving only the iron supports.
  • 1998: Purchased by Leisure Parks Ltd (Trevor Hemmings) along with several other UK piers.
  • 2005: Voted “Pier of the Year” by the National Piers Society.
  • 2015: Purchased by local entrepreneur Adam Williams (Tir Prince Leisure Group) for £4.5 million.
  • 2021: Adam Williams purchased the derelict Pavilion site to protect the pier’s future.
  • 2025: Voted “Pier of the Year” for the second time following major restoration efforts. 

Llandudno Pier Overview and Historical Timeline by Era

Product and Project Management

Product and Project Management

Cost Estimating vs Cost Planning

Cost Estimating vs Cost Planning

In professional project management and construction, cost estimating and cost planning are complementary processes that occur at different stages to ensure a project remains financially viable. 

1. Cost Estimating: “What will it cost?”

Cost estimating is a technical assessment used to predict the expenditures for a project. 

  • Early Stages: Estimates might be “rough orders of magnitude” based on square footage or historical data (e.g., cost per hotel room).
  • Later Stages: Estimates become precise “tender figures” used by contractors to bid on work, factoring in current market rates for labour and materials.
  • Function: It answers the question: “Is this specific plan affordable?”. 

2. Cost Planning: “How do we stay on budget?”

Cost planning is a strategic framework that manages a project’s financial health from start to finish. 

  • Iterative Process: It is a “living document” that is updated as the project moves from concept to detailed design.
  • Allocation: It breaks down the total budget into “elemental” targets (e.g., spending £X on the foundation and £Y on finishes).
  • Control: If an estimate for one part of the project exceeds its target, the cost plan guides the team to adjust the design or find savings elsewhere to keep the overall project on track. 

Standard Professional Guidance

The Royal Institution of Chartered Surveyors (RICS) provides the New Rules of Measurement (NRM 1), which standardises how these processes work together: 

  1. Order of Cost Estimate: Establishing the initial viability of a project.
  2. Elemental Cost Plan: Breaking the estimate down into functional parts.
  3. Cost Checking: Continually comparing design changes against the cost plan to prevent overspending.
Cost Estimating vs Cost Planning

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