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
The primary purpose of a Project Quality Plan (PQP) is to define the standards, tools, and processes required to ensure a project’s deliverables are “fit for purpose” and meet all stakeholder expectations. It serves as a strategic roadmap for the project team to maintain consistent quality throughout the project lifecycle rather than treating it as an afterthought.
Core Objectives
A PQP is designed to achieve several critical goals:
Define “Quality”: Translates vague stakeholder needs into measurable criteria and specific benchmarks.
Prevent Defects: Establishes Quality Assurance (QA) processes to proactively “build in” quality from the start, reducing the risk of errors.
Detect and Correct Issues: Outlines Quality Control (QC) activities, such as testing and inspections, to identify and fix defects before they reach the customer.
Clarify Accountability: Assigns specific roles and responsibilities so every team member knows who is responsible for performing, checking, and approving work.
Ensure Compliance: Guarantees the project adheres to relevant internal policies, legal regulations, and industry standards like ISO 9001.
Strategic Benefits
Implementing a structured quality plan provides tangible advantages for project management:
Reduced Costs and Rework: By catching errors early, the team avoids expensive last-minute fixes and wasted resources.
Improved Efficiency: Standardised workflows and clear metrics allow the team to focus on production rather than constant troubleshooting.
Increased Stakeholder Trust: Providing objective evidence through audits and reports gives sponsors and clients confidence in the final outcome.
Continuous Improvement: The plan often includes feedback loops and lessons-learned processes to refine and enhance quality for future project phases.
Critical Chain Project Management (CCPM) represents a paradigm shift in how timelines are managed, moving away from traditional task-based safety to system-wide buffers. Its history is deeply rooted in the Theory of Constraints (TOC) and evolved through four primary eras of modern project management.
The Foundations: Pre-1958
Before the formal creation of CCPM, the industry relied on “craft-based” approaches and the early Gantt Chart (1910s) to visualize task durations. During this era, projects like the Hoover Dam (1931) and the Manhattan Project proved that large-scale coordination was possible, but they lacked a systematic way to handle resource constraints or project-wide uncertainty.
The Traditional Era: 1958 – 1979
This period saw the birth of the “Critical Path,” the ancestor of the “Critical Chain.”
1957: The Critical Path Method (CPM) was invented by the DuPont Corporation to manage chemical plant maintenance.
1958: The Program Evaluation Review Technique (PERT) was developed for the U.S. Navy’s Polaris Project, introducing probabilistic task durations.
The Limitation: While these methods identified the longest sequence of tasks, they often ignored resource availability, leading to frequent delays and “multitasking” inefficiencies.
The Conceptual Era: 1980 – 1994
The theoretical seeds for CCPM were planted during the rise of the personal computer and the introduction of a new management philosophy.
1984:Dr Eliyahu M. Goldratt published his seminal business novel, The Goal, introducing the Theory of Constraints (TOC).
Core Principle: Goldratt argued that every system has at least one constraint that limits its output. Managing this “bottleneck” is the key to overall performance.
Focus Shift: Organizations began looking at “flow” rather than just individual task completion.
The CCPM Era: 1995 – Present
CCPM was formally introduced as a distinct methodology to address the failures of traditional CPM.
1997: Goldratt published the book “Critical Chain”, officially launching the method.
Key Innovations: Unlike CPM, the Critical Chain accounts for both task dependencies and resource constraints. It replaced individual task “safety margins” with:
Project Buffers: A collective time safety net placed at the end of the project.
Feeding Buffers: Placed where non-critical tasks feed into the critical chain to prevent delays.
Fever Charts: A new visual tool for tracking buffer consumption rather than just task deadlines.
Modern Integration: In the 21st century, CCPM has been integrated with Agile and Lean practices to help organizations manage multi-project pipelines and global resource pools.
Critical Chain Project Management (CCPM) timelines differ from traditional methods by shifting safety margins from individual tasks to strategic buffers at the end of the project or at integration points. This approach accounts for both task dependencies and resource constraints to determine the “Critical Chain”—the true longest path in a project.
Core Components of a CCPM Timeline
The Critical Chain: The longest sequence of dependent tasks, adjusted for resource availability.
Aggressive Task Estimates: Tasks are estimated at a 50% confidence level (how long it takes if things go well) rather than the traditional 90% (safe) estimate.
Project Buffer: A single aggregate buffer placed at the very end of the project to protect the final delivery date.
Feeding Buffers: Placed at points where non-critical task sequences (feeding chains) merge into the critical chain, preventing delays in minor tasks from affecting the main timeline.
Resource Buffers: Virtual markers or alerts placed before critical tasks to ensure that key resources (people or equipment) are ready to start exactly when needed.
CCPM versus Traditional Timeline (CPM)
Implementing a CCPM Timeline
Identify the Critical Path: Map the logical sequence of tasks.
Level Resources: Adjust the schedule so no single resource is over-allocated, transforming the path into a Critical Chain.
Strip Task Padding: Reduce task durations by roughly 50% to eliminate “Student Syndrome” (procrastinating until the last minute).
Insert Buffers: Add a Project Buffer (typically 50% of the chain’s length) at the end and Feeding Buffers where non-critical paths merge.
Monitor via Fever Chart: Use a Fever Chart to track if the buffer is being consumed faster than tasks are being completed.
Critical Chain Project Management (CCPM) Overview and Timeline