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.

Essential Business Analyst Skills & the Tools that Power Them

Essential Business Analyst Skills & the Tools that Power Them
Essential Business Analyst Skills
& the Tools that Power Them

Project Requirements Gathering Essentials

Project Requirements Gathering Essentials
Project Requirements
Gathering Essentials

Requirements gathering is the foundational process of identifying, documenting, and managing what a project must achieve to deliver maximum business value. According to the Project Management Institute (PMI), nearly 70% of project failures are directly attributed to poor requirements collection, highlighting its role as the ultimate “scope anchor” for project managers.

Below is an overview of the core steps, techniques, classification categories, and tracking methods needed to establish an airtight requirement framework.

The 6-Step Requirements Gathering Process

Executing a structured lifecycle ensures that raw client requests are transformed into precise, measurable technical blueprints.

  1. Identify and Analyze Stakeholders
    • Map out every individual invested in the project baseline.
    • Separate them into internal (executives, developers) and external entities (vendors, customers).
    • Utilize a stakeholder register to analyze their influence and prioritize conflicting needs early.
  2. Establish Goals and Alignment
    • Define overarching high-level business milestones before hunting for product features.
    • Separate broad targets (goals) from specific deliverables or tasks (objectives).
    • Filter out scope proposals that fail to directly support these core goals.
  3. Elicit Stakeholder Requirements
    • Conduct interactive discovery sessions tailored to user availability and project context.
    • Use direct one-on-one sessions for specific detail validation.
    • Use data gathering structures for broader user bases.
  4. Document and Categorize
    • Translate conversational feedback into clear, unambiguous definitions.
    • Store information inside a centralized, accessible collaborative hub.
    • Record relevant project assumptions and hard technical boundaries.
  5. Prioritize and Validate
    • Organize requests into strict low, mid, or high urgency classifications.
    • Apply prioritization frameworks like MoSCoW (Must-have, Should-have, Could-have, Won’t-have).
    • Conduct structured internal reviews to confirm value connection back to the business.
  6. Baseline Sign-off and Change Control
    • Request formal verification from the main project sponsors.
    • Set a fixed baseline to prevent unauthorized project feature updates.
    • funnels all future adaptations through a strict change control system.

Core Categories of Requirements

To prevent scope gaps, information must be analyzed from a 360-degree technical and strategic perspective.

  • Business Requirements: Define the ultimate overarching problem or strategic objective the business needs to resolve.
  • Stakeholder Requirements: Capture the specific desires, expectations, and operational pain points of the end users.
  • Functional Requirements: Spell out exactly what the target solution must execute or how a user interacts with it.
  • Non-Functional Requirements: Specify system traits such as performance, data security parameters, and growth scalability.
  • Technical Requirements: Detail the internal IT setups, environments, and languages the project must operate inside.

Essential Gathering Techniques

Choosing the right collection methodology depends on the size of your audience and the technical complexity of the work.

Project Requirements Gathering Essentials
Project Requirements Gathering Essentials

Scope Governance: The Traceability Matrix

Once requirements are baselined, they are tracked using a Requirements Traceability Matrix (RTM). This tool links every approved feature back to its source stakeholder and forward into production and testing.

  • Bi-Directional Tracking: Traces forward from need to test case, and backward from code to initial business authorization.
  • Eliminates Scope Creep: Ensures that development engineering teams only spend resources on validated features.
  • Prevents Orphaned Elements: Flags code built without initial business justification, or targets missing a test plan.

Role of a Business Analyst BA in API Integration

Role of a Business Analyst BA in API Integration
Role of a Business Analyst BA
in API Integration

A Business Analyst (BA) acts as the critical bridge between business stakeholders and technical teams. In API integration, the BA translates strategic business goals into clear technical requirements. They ensure systems communicate seamlessly, align with business rules, and support the overall customer journey.

Core responsibilities for a BA in API integration include:

  • Requirement Gathering: Translating business needs into precise functional and non-functional requirements, such as payload data requirements, expected response times, and security protocols.
  • Data Mapping: Defining exactly how data fields correspond across different systems (e.g., matching a CRM’s “Client Name” to a billing system’s “Customer”) and determining data transformation rules.
  • Defining Scenarios: Detailing the API’s behavior for both standard workflows and edge cases, such as handling invalid login attempts, rate limiting, and system timeouts.
  • Documentation & Modeling: Using sequence diagrams and flowcharts to visually map out how systems interact, and producing clear Interface Control Documents (ICD).
  • User Stories & Acceptance Criteria: Writing integration-focused user stories for Agile backlogs, including specific HTTP methods, request/response formats, and error codes.
  • Facilitating Collaboration: Bridging the communication gap by translating technical constraints to non-technical stakeholders and business objectives to developers.
  • Testing & UAT Support: Assisting the QA team in validating API endpoints using tools like Postman, and ensuring requirements are met during User Acceptance Testing (UAT).

To deepen your understanding of this role, comprehensive guidelines and methodologies can be explored via LinkedIn’s API for Analysts or Business Analyst Community Integration Guides.

Role of a Business Analyst BA in API Integration

Agile Scrum Five Events

1. Agile Scrum Five Events
2. Agile Scrum Five Events
Agile Scrum Five Events

Why an Organisation Needs a PMO, Project Management Office

Why an Organisation Needs a PMO, Project Management Office
Why an Organisation Needs a PMO,
Project Management Office

An organisation needs a Project Management Office (PMO) to act as the strategic backbone that standardises processes, minimises operational risks, and directly aligns day-to-day project execution with long-term business goals.

Research by the Project Management Institute (PMI) highlights that 80% of high-performing organisations have established PMOs. Furthermore, companies utilizing a PMO deliver initiatives up to 2.5 times faster and waste 38% less budget compared to those operating without one.

1. Strategic Alignment & Portfolio Prioritisation

  • Goal connection: PMOs act as a filter, continuously checking that all active projects serve the corporate strategy.
  • Value redirection: The office can proactively recommend pausing or canceling redundant projects, redirecting resources to high-value initiatives.
  • Intake governance: They design a structured framework for project intake to stop random, impulsive investments.

2. Standardisation & Quality Assurance

  • Unified framework: PMOs replace chaotic “every-team-for-itself” habits with shared templates, common metrics, and standard delivery methodologies.
  • Repetitive economy: Creating consistent guidelines allows multi-project execution to become a predictable machine, reducing human error.
  • Performance baselines: Standardised metrics give leadership an objective rubric to compare project health across entirely different business units.

3. Resource Optimisation

  • Bottleneck reduction: Centralised control prevents staff from being unsustainably double-booked across competing silo projects.
  • Capacity visibility: Real-time capacity mapping lets the executive suite understand exactly who is available before approving future workloads.
  • Skills leverage: PMOs actively track internal talents, allowing organisations to pivot specialized professionals to high-priority issues quickly.

4. Data-Driven Governance & Risk Management

  • Executive transparency: PMOs deliver aggregated status dashboards (like “Stop Light” reporting) to keep stakeholders clearly informed without digging through minor details.
  • Early risk mitigation: Using institutional tools like RAID logs, they catch budget variances and deadline slips before they cascade out of control.
  • Compliance protection: They ensure strict adherence to industry regulations, corporate ethics, and legal benchmarks to safeguard the firm from penalties.

5. Knowledge Management & Continuity

  • Lessons learned: The PMO retains historical metrics, helping project teams build realistic, accurate cost and timeframe estimates on subsequent iterations.
  • Mentorship hubs: They provide ongoing skills coaching and workshops to organically raise the project management maturity level across the company.

Definition of Done DoD vs Definition of Ready DoR in Agile Scrum

1. Definition of Done DoD vs Definition of Ready DoR in Agile Scrum
2. Definition of Done DoD vs Definition of Ready DoR in Agile Scrum
Definition of Done DoD vs Definition
of Ready DoR in Agile Scrum

Insider Technologies Limited, Timeline of HPE NonStop Activity

Mark Whitfield spent 18 years (August 1995 – September 2013) at Insider Technologies Limited (ITL), a Manchester-based software house specialising in high-availability tracking, service management, and transaction monitoring. Entering as a Senior Programmer, he climbed through the ranks to become an Operations Products Manager and, ultimately, the Project Manager for Strategic Technical Initiatives.

Insider Technologies Limited, Spinnaker Court, Chandlers Point, Salford Quays, Broadway. M50 2YR
Insider Technologies Limited,
Spinnaker Court, Chandlers Point,
Salford Quays, Broadway. M50 2YR

His core technical contribution revolved around developing and managing platform-health diagnostic modules, automated event filtering, and multi-currency transaction log trackers.

He focused heavily on the HPE NonStop (Tandem) kernel, integrating these mainframes with Windows, Unix, and Linux open systems. His work protected critical banking infrastructure, such as transaction loops feeding into ACI BASE24 ATM/POS switches and major national payment clearings.

Detailed Timeline Breakdown

🔹 The Foundational Tandem Era (1995–1999)

This period focused on building out bespoke low-level mainframe diagnostic scripts, real-time logging, and bracing critical infrastructure for the millennium bug.

  • 1995: Joined Insider Technologies Limited at Salford Quays after departing Deluxe Data. He began programming SCOBOL green screens and engineering PATHWAY servers to query raw Guardian operating system procedures.
  • 1996: Core developer for the flagship Reflex monitoring suite (Reflex 80:20). He co-authored the Console module for HPE NonStop Event Management Service (EMS) viewing, alongside tracking blocks for system components like CPU, Disk, and Processes.
  • 1997: Transitioned into an infrastructure consulting capacity, designing code routines to test physical hardware throughput.
  • 1998: Formally appointed as the ITL Operations Products Manager. He orchestrated high-performance benchmarking tests on newly deployed Tandem S7000 processing hardware nodes for Euroclear (formerly CRESTCo), validating infrastructure that handled 88% of UK equities.
  • 1999: Directed critical, deep-level automated Y2K code auditing. This guaranteed that real-time tracking loops and MultiBatch scheduling automation would accurately handle the date rollover for clearing partners like the Bank of England and Deutsche Bank.

🔸 The Operations & Middleware Integration Era (2000–2005)

This era bridged the gap between rigid standalone mainframes and modern open-system dashboards, creating cross-platform monitoring frameworks.

  • 2000: Spearheaded deep-layer integration projects connecting legacy frameworks to distributed enterprise collectors like TIVOLI, COMMAND/POST, and third-party file monitors.
  • 2001: Supervised 24×7 enterprise support teams handling cryptographic security frameworks for Thales e-SECURITY products, overseeing the SafeSign Authentication and Management Server lines on Windows/Unix.
  • 2002: Led technical rollouts for ITL’s interactive Systems Training Platform, deploying patented system-cloning configurations to let institutional clients practice outage responses safely.
  • 2003: Drove cross-platform middleware compatibility protocols, building hooks between the NonStop kernel and WebSphere MQ (MQSeries) message streams to trap transactional anomalies in real-time.
  • 2004: Advanced to Project Manager – Strategic Technical Initiatives, implementing PRINCE2 governance for new product R&D pipelines.
  • 2005: Began standardising the technical architecture of Reflex ONE24, transitioning the vintage monitoring code toward centralized electronic web consoles.

🔹 The Strategic Initiatives & Product Management Era (2006–2013)

Whitfield shifted into pure-play product management, expanding corporate web assets and publishing technical documentation before navigating the company through an MBO.

  • 2006: Pioneered custom transaction parsing frameworks for payment switches, resulting in the foundational engine layout of Sentra and the Real-Time Log Extraction (RTLX) engine.
  • 2007: Acted as the primary corporate website architect and author, modernising Insider’s public presence by building out and managing content deployments on DotNetNuke (DNN).
  • 2008: Managed implementation pipelines for XPERT24, a highly specialized utility engineered specifically for performance tracking across complex BASE24 XPNET banking environments.
  • 2009: Directed extensive migration initiatives, shifting clients from obsolete platform tracking matrices onto unified monitoring frameworks.
  • 2010: Guided software engineers through logic modifications to intercept multi-currency retail POS and ATM interchange drops down to the millisecond.
  • 2011: Coordinated agile deployment sprints for financial institutions to meet strict compliance laws surrounding automated data storage and long-term file retention.
  • 2012: Provided the project governance behind the scenes during Insider Technologies’ internal structural transitions, supporting a £3m Management Buyout (MBO).
  • 2013: Authored a major technical summary published globally in the recognized HP NonStop industry journal, The Connection, defining payment software lifecycles. Concluded his 18-year run at ITL in September to join Wincor Nixdorf.

(Note: The product lines Whitfield built and governed were later acquired by ETI-NET in 2015, where his original RTLX utility was rebranded as C-Deep for Transaction Monitoring.)

Capgemini Projects Managed from 2016 thru 2025, Summary

Mark Whitfield is an SC-cleared Senior IT Project Manager and Engagement Manager at Capgemini UK (Custom Bespoke Solutions).

Mark Whitfield’s IT project management and software engineering career spans over three decades
Mark Whitfield – Senior IT
Project Manager – SC cleared

Joining in January 2016, he has orchestrated enterprise-scale cloud migrations, middleware application refactoring, and API-led integration architectures across public sector and tier-one corporate clients.

Capgemini UK, Floor 7, Venus Building, Trafford Quays, Manchester. M41 7HA
Capgemini UK, Floor 7, Venus Building,
Trafford Quays

Below is the complete portfolio overview and highly detailed chronological breakdown by year of his project delivery history at Capgemini.

Project Portfolio Overview

  • Role Title: Certified Engagement Manager / Delivery Manager (A8 Core Level)
  • Methodologies: Agile Scrum ceremonies, Waterfall frameworks, and hybrid delivery patterns
  • Core Competencies: Hybrid cloud migrations, API lifecycle architectures, cross-data centre integration, multi-supplier governance, and financial forecasting
  • Key Clients Served: UK Government, MuleSoft / Salesforce, Jaguar Land Rover, Royal Mail Group, NATS, and Welsh Water

Detailed Capgemini Projects Timeline Breakdown by Year:

2016 – 2017: Aerospace & Defence Integration & Postal Infrastructure

  • Aerospace & Defence Mobile Apps: Managed an Agile Scrum delivery stream for a UK-wide Air Traffic organisation (NATS). He supervised the development of dual-layered Apple iOS applications rendering real-time airspace positioning data, separating sensitive internal military maps from public views.
  • Salesforce Portal Deployment: Led the enterprise integration and deployment of a Salesforce-driven Single Customer View (SCV) portal platform for defence stakeholders.
  • Postal Services Migration (May 2016 – Oct 2016): Appointed as PM for an award-winning £4.3 million Data Centre Migration project for a major postal client (Royal Mail Group). He directed 90 Capgemini engineers to shift 1,100+ critical interfaces—migrating file transmissions written in UNIX shell scripts and upgrading 150 interfaces processing through IBM ESB to safe software versions right before peak seasonal trading lockouts.

2017 – 2018: Automotive Supply Chain Middleware

  • Jaguar Land Rover iFAB Project: Directed the complex 12-month iFAB Middleware Project architecture development scheme. This cross-functional framework connected globally dispersed manufacturing supply components.
  • Supplier Governance: Coordinated on-site daily standups alongside integration engineering leads to accurately synchronize multiple software suppliers handling distinct tiers of middleware, messaging queues, and front-end architectures.

2018 – 2019: Enterprise API Platform Delivery (MuleSoft)

  • MuleSoft HQ Augmentation (October 2018 – June 2019): Embedded directly into MuleSoft’s London headquarters (Salesforce Tower) as a Senior Delivery Manager.
MuleSoft's London office is located within the Salesforce Tower (formerly known as Heron Tower) at 110 Bishopsgate.
MuleSoft’s London office is located within the Salesforce Tower at 110 Bishopsgate.
  • Anypoint Platform Deployments: Guided multinational corporate clients through API-led connectivity lifecycles. This encompassed configuring Anypoint Code Builder structures, validating hyper-automation runtime layers, and ensuring architectural compliance against regulatory framework rules.
Anypoint Platform Deployments: Guided multinational corporate clients through API-led connectivity lifecycles.
Anypoint Platform is the leading enterprise platform for building APIs, integrations & application networks

2019 – 2021: Large-Scale Public Sector Cloud Migration

  • UK Government Hybrid Cloud Transformation: Commanded a massive modernization program migrating a highly complex estate of legacy code.
  • 130 Applications Transformed: Acted as the primary client escalation point to refactor, re-host, and re-platform 130 public-sector software applications into hybrid cloud environments. His responsibilities included aligning the massive multi-stack migration with strict GDPR protection directives and managing offshore project delivery targets.

2022: Utility Infrastructure & Cloud Upgrades

  • Water Utility EQS Cloud Shift: Dual-managed a £0.5 million technical contract moving an legacy document management environment (EQS) onto Microsoft Azure cloud structures via Enablon for Welsh Water and Scottish Water.
  • MS Dynamics 365 Evolution: Supervised a £0.4 million discovery and blueprint phase to move 12 legacy Microsoft Dynamics 2016 instances operating on outdated shared 8.2 infrastructure onto the unified Microsoft Dynamics 365 Online ecosystem. This involved authoring precise Statements of Work (SoW), custom exit strategies, and foundational Microsoft Project (MPP) tracking models.
  • Accolades: Won the prestigious Capgemini C&CA UK Communications & Engagement Award in December 2022 for outstanding delivery inside the Cloud & Custom Applications business unit.
C&CA UK's Communications & Engagement Award Winner 2022 - Cloud & Custom Applications - Capgemini UK
C&CA UK’s Communications & Engagement Award Winner 2022 – Cloud & Custom Applications – Capgemini UK

Verified Sourcing & Portfolio Links

Capgemini Projects Managed from 2016 thru 2025, Summary