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.

The Reality of a Project Manager, Execution and Accountability

The Reality of a Project Manager, Execution and Accountability

Agile Story Points and the Fibonacci Series, Estimation Strategy

Agile Story Points and the Fibonacci Series, Estimation Strategy
Agile Story Points and the Fibonacci Series, Estimation Strategy

Scrum and Agile in Projects

Scrum and Agile

Mark Whitfield, SC Cleared Senior Project Manager, Manchester

Mark Whitfield is a highly experienced, SC-cleared Senior Project Manager and Engagement Manager specializing in complex IT software development lifecycle (SDLC) projects, digital transformation, and cloud migrations.

Currently based in Greater Manchester, UK, he has over 31 years of experience in the IT industry, working with major blue-chip companies across various sectors, including UK Government, retail banking, aerospace, and utilities.

He is a certified PRINCE2 Practitioner, skilled in both Agile SCRUM and Waterfall methodologies.

Website Links:

Professional Biography:

Mark specializes in bridging technical teams and business stakeholders, delivering complex IT systems under challenging conditions.

His career spans from early roles as a developer on Tandem Mainframe Computers (HPE NonStop) to senior management positions focusing on cloud resources, API integrations, and CRM platform implementations.

  • Key Skills: Project Planning, Stakeholder Management, Financial Forecasting, Risk Management (RAID), Agile Scrum, PRINCE2, ITIL.
  • Key Strengths: Cloud Migration (Azure/Dynamics 365), Payment Systems (ATM/POS), and API-led connectivity.

Detailed Career Timeline:

  • Nov 2023 – Feb 2024 (UK Government – Capgemini): Acted as Client-Side Technical Delivery Manager for a £1m+ Fish Export Service (FES) to CHIP project, facilitating Azure-based API updates for UK-Northern Ireland trade.
  • Nov 2022 (UK Government – Capgemini): Managed two Microsoft Dynamics 365 Azure Cloud projects, including a £0.4m Dynamics 2016 migration and a £0.54m CRM platform discovery/build.
  • Feb 2022 (UK Utility Industry – Capgemini): Managed a £0.5M project migrating legacy document management systems to an Azure-based Enablon product.
  • 2020 (UK Gov – Capgemini): Senior PM for a £375k Agile proof-of-concept (POC) project migrating legacy applications (MS Access/Oracle) to Microsoft Azure and Dynamics 365.
  • Oct 2018 – June 2019 (MuleSoft): Served as Delivery Manager overseeing 5+ UK accounts for MuleSoft Anypoint Platform (API-led connectivity) implementations.
  • Oct 2017 (Automotive Industry – Capgemini): Managed a £430k Digital Readiness project and a £670k Customer Portal/Online Sales project (Agile).
  • May 2017 (Local Govt – Capgemini): Led a £400k telecommunications project (CCaaS) for the Support for Mortgage Interest (SMI) program.
  • Jan 2017 (Aerospace/Def – Capgemini): Senior Project Lead for two £1.3M projects with high-governance and gated deliverables.
  • Jan 2016 – Present (Capgemini UK): Joined as an Engagement Manager (A8), working on projects including Apple iOS app development for UK Air Traffic (NATS) and a £4.3M data center migration for Postal Services.
  • Dec 2014 – Jan 2016 (Betfred Limited): IT Senior Digital Project Manager for online/mobile payment gateways and sports book platforms.
  • Sep 2013 – Dec 2014 (Wincor Nixdorf): Senior Project Manager for a £5+ million ATM/POS software swap-out at a UK retail bank.
  • 2013 (Retail Banking – Riyadh): Delivered an RTLX transaction tracking project (BASE24 Classic) at a Saudi Arabian bank.
  • 1995 – 2013 (Insider Technologies): Worked on Strategic Technical Initiatives and bank-facing projects on the HPE NonStop platform (Tandem) for products Reflex 80:20, Reflex ONE24, RTLX and XPERT24.
  • 1990 – 1995 (The Software Partnership/Deluxe Data): Commenced career as a programmer specializing in electronic banking software on Tandem Computers (HPE NonStop), sp/ARCHITECT-BANK

Education:

  • 1988 – 1990: Higher National Diploma (HND) in Computing, Distinction/Overall First, Bolton Institute of Higher Education (now University of Greater Manchester from 2024).

Mark Whitfield, SC Cleared Senior Project Manager, Manchester

Connect NonStop Registration Sept. 2026, NonStop Technology & Business Conference

Connect NonStop Registration 2026, NonStop Technology & Business Conference
Event Date

September 15-17, 2026 (HPE Education Sept. 14)

Event Location

Orlando, Florida

Venue

The Rosen Plaza 9700 International Drive

Contact Us

info@connect-community.org

TBC’26

Why Do Project Managers Exist?

Why Do Project Managers Exist
Why Do Project Managers Exist?

Project Management Deliverables relating to Project Lifecycle

Project management deliverables are the tangible or intangible outputs—products, services, or documents—produced as a result of project activities. They are specific, measurable, and agreed upon by stakeholders to demonstrate progress toward project goals.

Overview of Project Deliverables

Deliverables are essential for breaking down project goals into manageable components, tracking progress, and ensuring stakeholder alignment.

Types of Deliverables:

  • Internal Deliverables: Created for internal use, such as team charters, project plans, and risk logs.
  • External Deliverables: Client-facing, such as a finished software product, marketing campaign, or project report.
  • Process Deliverables: Interim outputs that mark progress, such as prototypes, wireframes, or testing reports.
  • Product Deliverables: The final, completed goods or services delivered.
  • Tangible vs. Intangible: Physical/digital items (e.g., machinery) vs. conceptual outcomes (e.g., a new training program).

Textual/Documentation Deliverables Project Lifecycle

The project lifecycle defines the stages a project goes through from start to finish. Textual and documentation deliverables are key to managing and controlling these stages.

1. Initiation Phase (Initiating)

  • Goal: Define the project at a high level and obtain authorization.
  • Key Deliverables:
    • Business Case: Why the project is needed.
    • Feasibility Study: Whether the project is achievable.
    • Project Charter: A formal document outlining objectives, scope, and key stakeholders.

2. Planning Phase (Planning)

  • Goal: Develop a roadmap for project execution and define constraints.
  • Key Deliverables:
    • Project Management Plan: A comprehensive document (roadmap) detailing tasks, timelines, and resources.
    • Scope Statement/WBS: Defines boundaries and breaks down work.
    • Communication Plan: Strategy for stakeholder communication.
    • Risk Register: Identifies potential threats and mitigation strategies.

3. Execution Phase (Executing)

  • Goal: Carry out the work defined in the plan to produce deliverables.
  • Key Deliverables:
    • Interim Products/Prototypes: Tangible outputs produced.
    • Meeting Minutes/Notes: Documentation of decisions and action items.
    • Change Requests: Documents updating scope or plan.

4. Monitoring and Controlling Phase

  • Goal: Measure performance against the plan and adjust as needed.
  • Key Deliverables:
    • Status Reports: Progress updates on key performance indicators (KPIs).
    • Quality Control Reports: Results of testing and validation.
    • Updated Project Schedule: Reflects current progress.

5. Closing Phase (Closure)

  • Goal: Formally accept deliverables and close out the project.
  • Key Deliverables:
    • Final Product/Report: The completed output.
    • Project Closure Report: Confirms final deliverables and contract closure.
    • Lessons Learned Document: Records successes and areas for improvement.

Best Practices for Managing Deliverables

  • Define Early: Ensure all stakeholders agree on what “done” means at the start.
  • Use Tools: Employ PM software (e.g., Asana, Jira, Monday.com) to track deliverables.
  • Assign Owners: Each deliverable should have a single, clear owner to ensure accountability.
  • Link to KPIs: Connect deliverables to key performance indicators to measure value.

Project Management Deliverables relating to Project Lifecycle

Agile Dependency Matrix Management in Project Management

Agile Dependency Matrix Management in Project Management
Agile Dependency Matrix Management in Project Management