Mark Whitfield’s IT project management and software engineering career spans over three decades, progressing from early electronic banking programming on Tandem Mainframes (now known as HPE NonStop) to senior delivery of enterprise-scale middleware, cloud, and digital transformation initiatives.
The high-level chronological timeline (with links) of his professional eras and key project history is broken down below.
💻 1990–1995: Early Programming & Lead Analysis Era
During this foundational era, Whitfield operated as a Programmer and Lead Analyst specializing in core electronic banking software frameworks.
The Software Partnership / Deluxe Data (1990–1995): Developed and enhanced the sp/ARCHITECT-BANK platform. His technical responsibilities focused heavily on coding within Tandem Mainframe environments (now HPE NonStop) using C, C++, TAL, COBOL, and PATHWAY architectures.
Deluxe Data International Operations, Wingate House, Northway, Runcorn
Barclays On-Site Delivery (Early 1990s): Deployed on-site at the Barclays facility in Knutsford, Cheshire. He was responsible for core code development and system architecture design on the Barclays Business Master II (BBM II) electronic banking initiative and subsequent billing modules developed in Poole, Dorset.
Barclays, Wimborne Road, Poole, Dorset
🛠️ 1995–2013: Senior Development & Strategic Project Management Era
Transitioning to Insider Technologies Limited at Salford Quays, Manchester, Whitfield progressed into high-level technical project delivery and strategic product management.
Insider Technologies Limited (ITL) in 2001, Salford Quays, Chandlers Point
Reflex Monitoring Suite R&D (1995–1996): Appointed as a core developer to design platform health and diagnostic plug-in modules for the flagship Reflex 80:20 tracking console.
CRESTCo Infrastructure Integration (1997–1998): Acted as a technical infrastructure consultant for CRESTCo (now Euroclear). Managed hardware benchmark coding and testing for newly deployed Tandem S7000 processing nodes.
CRESTCo in 1997 on St. Katherine’s Dock near Tower Hill tube station
Real-Time Tracking Protocols (1999–2001): Oversaw multi-organizational telemetry deployments for the Bank of England and Deutsche Bank, leveraging specialized MultiBatch scheduling utilities and automated file monitors.
Hewlett-Packard (HP) Certification Initiative (2002–2003): Successfully drove the rigid compliance and verification process to secure official certification for the first HP OpenView Operations (OVO) Smart Plug-In built for NonStop mainframe environments.
First HP OpenView Operations Smart Plug-In for HPE NonStop environments
ATM Log Extraction Deployments (2004–2007): Led technical delivery teams implementing automated transaction log extraction layers (RTLX and Sentra) to audit ATM networks for major retail financial brands like Alliance & Leicester (now Santander) and HSBC.
Cross-Border Retail Banking Rollout (2008–2010): Served as Project Manager overseeing a high-volume, cross-border ATM and Point-of-Sale (POS) environment monitoring expansion for a prominent Saudi Arabian Retail Bank.
Cross-border ATM and Point-of-Sale (POS) environment monitoring expansion
Enterprise Transaction Monitoring (2011–2013): Functioned as Project Lead to bridge retail banking transaction networks with corporate governance architectures. Integrated critical pathways for Standard Chartered and Global Payments into TIVOLI and XPERT24 using ACI’s XPNET infrastructure.
Wincor Nixdorf Banking Division (2013–2014): Retained as Project Manager for Professional Services. He directed a massive hardware and software transition stream for Lloyds Banking Group’s Self-Service Software Replacement (SSSR) programme whilst also providing a qualified management link with Wincor Nixdorf, Paderborn (Germany) for subject matter expertise, as part of the transition.
🎮 2014–2016: Digital Infrastructure & Enterprise Betting Era
Whitfield shifted his delivery domain focus from banking mainframes into real-time high-transaction digital platforms.
Betfred Project Delivery (2014–2016): Managed IT infrastructure and digital systems alignment projects, supporting high-throughput retail and digital consumer gaming workflows.
☁️ 2016–Present: Cloud Integration, Middleware, & Public Sector Era
In this current era, Whitfield acts as a senior, SC-cleared Senior IT Project Manager specializing in hybrid cloud migrations and API-led integration.
Capgemini UK Consultancy (2016–Present): Leading massive corporate and public sector agile/waterfall delivery initiatives. His technical program management footprint expands across a vast roster of tier-one enterprise environments:
MuleSoft Ecosystem Deployments: Directing system integration projects utilising the Salesforce MuleSoft suite, spanning API lifecycle design, Anypoint Code Builder configurations, and hyper-automation flows.
Multi-Sector Enterprise Clients: Orchestrating cloud migrations, middleware application refactoring, and data pipelines for Jaguar Land Rover (JLR), Heathrow Airport, Royal Mail Group (RMG), NATS (National Air Traffic Services), Welsh Water, Rabobank, Barclays, and UK Export Finance (UKEF).
C&CA UK’s Communications & Engagement Award Winner 2022 – Cloud & Custom Applications – Capgemini UK
HP OpenView Operations (OVO) is a foundational enterprise systems management (ESM) platform designed to centrally monitor and manage infrastructure, multi-vendor operating systems, and enterprise applications across distributed IT environments.
The system operates on an Agent-Server Architecture. Core components include:
Management Server: Central hub that aggregates system logs, processes alerts, correlates events, and triggers automated remediation scripts.
Smart Plug-ins (SPIs): Specialized modular add-ons that inject domain-specific monitoring logic for applications like Oracle databases, Microsoft Active Directory, or SAP.
Intelligent Agents: Lightweight background processes deployed on managed nodes to collect log events, metrics, and state data, formatting them into structured OVO messages.
1. HP OVO screenshot in 2002
2. HP OVO screenshot in 2002
See bottom of this post for HPE NonStop (previously Tandem) monitoring in OpenText Operations Bridge Manager. I overlooked an integration with HP OpenView Operations for a HPE NonStop product in 2002, called Reflex 80:20.
Detailed Timeline Breakdown by Era and Year
🌅 Era 1: Origins and The Foundation (Late 1980s – 1994)
This era established HP’s footprints in IT infrastructure management, pivoting from pure SNMP network map discovery toward server telemetry.
Late 1980s: HP releases Operations Center (OpC) as an add-on application for its core Network Node Manager (NNM) platform. It replaces slow SNMP polling with Remote Procedure Calls (RPC) to gather host logs.
1990–1993: HP scales OpC into a robust engine capable of executing basic automation scripts on remote UNIX boxes when specific thresholds break.
🚀 Era 2: The “ITO” and OpenView Operations Boom (1995 – 2000)
The framework shifted from isolated utilities into an integrated, market-dominating enterprise suite.
1995: HP tightly merges NNM and Operations Center into a single product called IT Operations (ITO) Version 3.x.
1996:HP OpenView Service Navigator is embedded into the product line. It provides a graphical hierarchy of business services instead of just a raw list of broken servers.
1999: The suite formally adapts to include broad SNMP traps alongside its core agents and is renamed HP OpenView Operations ITO.
🔄 Era 3: Platform Split and VantagePoint Transition (2001 – 2006)
HP decoupled its codebases to natively handle Windows NT/2000 scaling alongside legacy Unix environments while heavily investing in product renaming.
2001: HP briefy rebrands the suite to HP VantagePoint Operations (VPO). However, customer brand loyalty forces them to quickly pivot back to the popular HP OpenView Operations (OVO) naming convention.
2002: Codebases officially bifurcate into OVOU (OpenView Operations for Unix) and OVOW (OpenView Operations for Windows, built natively on Microsoft WMI frameworks).
2005:OVO Version 8.0 drops. It features heavy integration capabilities for external service desks, advanced HTTP/HTTPS agent communication protocols, and a refreshed Java GUI console.
🏢 Era 4: The Business Technology Optimization (BTO) Era (2007 – 2016)
Massive corporate acquisitions changed the software landscape. OVO ceased to be a standalone system monitoring tool and transformed into an automated operations center.
2007: HP drops the legendary “OpenView” moniker. Following the acquisitions of Mercury Interactive, Peregrine, and Opsware, the suite is rebranded as HP Operations Manager (HPOM) under the HP Business Technology Optimization (BTO) banner.
2009: HP rolls out Operations Manager i (OMi), integrating topology-based event correlation (TBEC) to suppress duplicate alert storms across the data center.
2015: Hewlett-Packard splits into two companies; the portfolio lands under Hewlett Packard Enterprise (HPE). The engine is bundled into the HPE Operations Bridge (OpsBridge) suite.
☁️ Era 5: Divestiture and Modern Legacy (2017 – Present)
2017: HPE spins off its enterprise software division. The entire legacy OpenView/Operations Manager portfolio is sold to Micro Focus.
2023:OpenText completes its acquisition of Micro Focus. The underlying technical heritage of the old OVO agents survives today, evolved into cloud-ready containerized architectures inside the modern OpenText Operations Bridge cloud monitoring portfolio.
OpenText Operations Bridge Manager Screenshot example
HPE NonStop (previously Tandem) Monitoring
Micro Focus Operations Bridge (now part of OpenText AI Operations Management) provides end-to-end IT monitoring by consolidating data from over 200 sources. For HPE NonStop, it utilizes specialized Management Packs to ingest metrics, system events, and health data for comprehensive, real-time hybrid IT analysis.
To monitor HPE NonStop servers using the modern OpenText Operations Bridge/AIOps platform, the setup revolves around the Operations Bridge Manager (OBM) and targeted management packs:
Management Packs for HPE NonStop: OpenText provides specific management packs and solutions designed for NonStop systems. These capture system health, CPU/disk metrics, pathway status, and system messages.
Operations Agent: A lightweight agent is deployed directly on the NonStop nodes, which securely streams local performance data and events back to the central OBM console.
Centralized Event Consolidation: OBM acts as a “manager of managers”. It ingests the NonStop events and correlates them alongside data from your cloud (AWS/Azure), containers, and network endpoints.
AIOps and Remediation: The platform utilizes built-in machine learning to reduce alert noise and accelerate root cause analysis. You can also use automated Runbooks to automatically remediate known issues on the NonStop platform.
Because the platform has been fully integrated into the OpenText portfolio, these integrations are supported across containerized deployments, on-premise, or SaaS models.
You can find downloadable PRINCE2 project templates in Excel (.xls/.xlsm) and Microsoft Project (.mpp) formats across several specialized platforms. Because PRINCE2 is a highly structured methodology, standard templates usually map its specific processes (like Starting Up, Initiating, and Controlling a Stage) directly onto Gantt charts and tracking sheets.
PRINCE2 MS Excel .xls plan in a spreadsheet
PRINCE2 MS Project .mpp plan in a project file
The primary download options, ranging from premium practitioner bundles to free resource packages, are categorized below:
Comprehensive Premium Bundles (MPP & XLS)
If you require a fully integrated toolkit built specifically for the official PRINCE2 framework, individual project management practitioners offer comprehensive marketplace downloads:
Mark Whitfield PM Templates: Offers a dedicated seventh edition package including MW MS Project Plan Template PRINCE2 v0.2.mpp alongside its exact equivalent spreadsheet MW Excel PRINCE2 Project Plan Template v0.2.xlsm. You can download this Prince2 toolkit package plus others, on the Mark Whitfield Official Site or through the Mark Whitfield Etsy UK Shop.
Flevy Marketplace: Provides highly structured, professional enterprise files. You can purchase and download the PRINCE2 Templates + Microsoft Project MPP & MS Excel Document directly from their platform, which packs the MPP tracking timelines and XLSM / XLS sheets together.
PRINCE2 project templates, Excel (.xls/.xlsm) & MS Project (.mpp) formats
Microsoft Excel XLS PRINCE2 spreadsheet screenshots
Microsoft Excel XLS PRINCE Project Plan with Task Descriptions
Microsoft Excel XLS PRINCE Project Plan with Gantt View 1
Microsoft Excel XLS PRINCE Project Plan with Gantt View 2
Microsoft Excel XLS PRINCE Project Plan with Gantt View 3
Microsoft Excel XLS PRINCE Project Plan with Delivery Costings
Microsoft Excel XLS PRINCE Project Plan with Charts
Microsoft Excel XLS PRINCE Project Plan with PRINCE2 Stage Charts
Standard Artifacts Included in Download Packages
When downloading a comprehensive .zip toolkit, the package typically contains the core structural elements of the framework divided across your scheduling software:
MS Project (.mpp): A pre-constructed Prince2 waterfall delivery layout mapped with the 7 key PRINCE2 stages, built-in dependency workflows, milestone gates, and methodological prompts embedded in the task notes.
MS Excel (.xls/.xlsm): Mirrored project planning sheets (with costing) utilizing native formulas to auto-populate Gantt charts, alongside targeted operational spreadsheets like RAID logs (Risks, Assumptions, Issues, Dependencies), RACI matrix charts, resource trackers, and project budget tools.
Legacy enterprise managers (often spanning IT Service Management, Network Node Management, and Event Correlation) defined enterprise IT in the 1980s, 1990s, and 2000s. The following are major, pioneering platforms, their primary functions, and their eventual modern replacements:
Legacy IT Operations Management (ITOM)
HP OpenView: A flagship suite that included Network Node Manager (NNM) for topology mapping and Operations Manager (formerly OVO) for centralized event and alert monitoring across Unix, Windows, and mainframes. I overlooked the integration of the HP NonStop product Reflex 80:20 with HP OpenView.
Modern equivalent: Evolved into Micro Focus Operations Bridge, later absorbed by OpenText.
IBM Tivoli: A massive suite born from the acquisition of Candle and Tivoli Systems. The core components included Tivoli Enterprise Console (TEC) for event correlation and Tivoli Netcool/OMNIbus for real-time network and service monitoring. I overlooked the integration of the HP NonStop product Reflex 80:20 with IBM Tivoli.
Modern equivalent: Evolved into IBM Cloud Pak for Watson AIOps.
BMC Patrol: One of the premier tools for deep system, application, and database monitoring (often known for its KM – Knowledge Module – architecture).
Modern equivalent:BMC TrueSight Operations Management and BMC Helix.
CA Unicenter: A comprehensive, all-in-one mainframe and distributed systems management tool for job scheduling, asset management, and event monitoring.
Modern equivalent: Rebranded under Broadcom, largely integrated into their enterprise software division.
Sun Microsystems SunNet Manager / Solstice Enterprise Manager: Early pioneers in Unix-based network management and remote system administration.
Modern equivalent: Discontinued; mostly absorbed by Oracle Enterprise Manager.
Enterprise Event Correlation & Command Centers
Command/Post (Boole & Babbage): One of the earliest automated event correlation engines designed for mainframes, which later expanded into distributed environments. Acquired by BMC.
Micromuse Netcool: Famous for its ultra-fast, rules-based Omnibus, capable of ingesting vast amounts of SNMP traps and Syslog messages across telecommunications and large enterprise networks. Acquired by IBM.
Network and Performance Managers
HP OpenView Performance/SysView: Tools specifically built for historical performance charting, OS native monitoring, and deep metric extraction.
Novell NMS (NetWare Management System): The standard for managing legacy Novell NetWare servers and IPX/SPX network topologies.
Most of these tools were displaced by modern APM (Application Performance Monitoring) and AIOps (Artificial Intelligence for IT Operations) platforms that feature cloud-native architectures, distributed tracing, and out-of-the-box integrations. Common replacements include:
Datadog
Dynatrace
Splunk / Splunk IT Service Intelligence
LogicMonitor
ScienceLogic
HP OpenView Operations
HP OpenView Operations Enterprise Managerintegrationwith Reflex 80:20
First HP NonStop 2-way Smart Plug-In (SPI) for HP OVO
Requested to research and produce a design for integrating the ITL NSK based Reflex 80:20 product with the hp OpenView Operations (hp OVO) enterprise manager. This initially involved a trip to Lisbon to attend the hp OpenView Universe event that represents the technical showcase for this enterprise level product. I then put together a number of design documents and managed a development team tasked with engineering an hp OpenView Smart Plug-in (SPI) to interact with Reflex 80:20 on the hp NonStop platform. This hp SPI approach represents the latest technology for integrating third-party products and provides an unparalleled approach for enabling remote platform control and management under hp OVO.
Once the Reflex SPI development was complete, I overlooked acceptance testing at the hp labs at Fort Collins, Colorado and was instrumental in attaining HP certification for the Reflex 80:20 product. As part of the certification process, I produced a comprehensive Reflex SPI user guide along with supporting marketing literature. More information.
BASE24 is an enterprise-grade electronic funds transfer (EFT) software suite developed by Applied Communications Inc. (now ACI Worldwide). It handles real-time transaction acquiring, authenticating, routing, switching, and authorization across ATMs, Point-of-Sale (POS) networks, and digital payment channels.
XPNET (Exchange Protocol Network) is the fundamental communications middleware layer designed explicitly for BASE24 on fault-tolerant systems. It acts as an abstraction layer managing interprocess communications (IPC), network protocols (e.g., Bisync, X.25, TCP/IP), line management, device messaging, and high-volume transaction routing. Together, they form the transactional backbone for a majority of the world’s top financial institutions.
RTLX Reactor (in 2012) for tracking BASE24-eps & BASE24 XPNET transactions
Deep-Dive Architecture and Technology Stack
1. BASE24 Core Design
Process Pair Architecture: Designed natively around Tandem’s process pairs. A Primary Process performs the active transaction switching while a Backup Process remains synchronized in a standby state. If the hardware or primary process fails, the backup takes over instantly with zero data loss or session drops.
Functional Modules: Divided into specific transactional entities:
ATM (Automated Teller Machine Device Handler): Direct control and state management of physical terminals using custom message streams (e.g., Diebold, NCR).
POS (Point of Sale): Merchant terminal management and merchant accounting integration.
Auth (Authorization Processor): Internal validation scripts against account records or stand-in limits.
2. XPNET Middleware Engine
Line and Station Infrastructure: XPNET maps communication through abstract configurations. A Line represents a physical or logical network pipe, and a Station represents an endpoint (e.g., an interchange gateway or terminal node).
Dynamic Load Buffering: Employs internal memory queue structures to absorb traffic spikes from international card networks (such as Visa and Mastercard) without spilling into disk storage.
Protocol Multi-threading: It decouples low-level link dynamics (e.g., CRC checking, dropouts) from core business logic, converting legacy and modern network formats into standardized internal transaction tokens.
Application Development Timeline & Political Breakdown
The timeline below details how geopolitical, regulatory, and corporate ownership developments directly shaped versioning and core code changes in BASE24 and XPNET.
Era 1: The Tandem & Expansionist Era (1975–1992)
Geopolitical & Industry Context: The rise of consumer credit card networks, personal checking accounts, and the physical expansion of banking via ATMs. Regional networks were fragmented, necessitating specialized software to cross-connect them.
Corporate Dynamics: Applied Communications Inc. (ACI) operated as an independent software house in Omaha, Nebraska, forming a deep partnership with Tandem Computers before being acquired by US West (1988) and later Tandem directly (1991).
Year-by-Year Code & Technical Milestones:
1975–1981: Initial exploration of high-availability banking systems on Tandem NonStop computers. Developers laid the groundwork using Tandem Screen COBOL and low-level communication drivers.
1982:BASE24 v1.0 officially launches. The original codebase was written in TAL (Tandem Application Language), a high-performance, structured system programming language designed specifically for NonStop systems.
1985: A primitive version of XPNET is spun out from early shared-memory messaging code to support multi-protocol lines (Bisync, Async) without forcing restarts of the core application.
1987: Introduction of early ISO 8583 message formatting engines within the core routing code. This allowed the software to natively interpret standard financial messaging frames across distinct interbank networks.
1991: Tandem acquires ACI. Code refactoring focused heavily on optimizing interactions with Tandem’s native file system (Enscribe) and expanding the XPNET process memory layout to take advantage of new Tandem CLX architecture performance.
Era 2: The TSA Corporate & Public Market Era (1993–2000)
Geopolitical & Industry Context: Globalization of financial services, the consolidation of national card switches, and the commercial explosion of internet banking and POS devices.
Corporate Dynamics: Tandem divested ACI to a private holding company, leading to the creation of Transaction Systems Architects (TSA) in late 1993. TSA went public on NASDAQ in 1995, pushing development velocity to meet Wall Street expectations.
Year-by-Year Code & Technical Milestones:
1993–1994: Standardized compilation routines moved to Tandem’s pTAL (portable TAL) to bridge code execution compatibility between older CISC-based architectures and the newly emerging MIPS RISC processors.
1995–1996: BASE24 version 4.x introduces advanced multi-institution handling inside a single logical codebase, allowing multi-tenant processing for third-party credit card consolidators.
1997: Release of BASE24 v5.x, featuring significant expansions in XPNET (v2.x) to accommodate native TCP/IP sockets alongside aging X.25 line infrastructures.
1998–1999: Heavy investment into Y2K compliance remediation. Code changes involved updating binary-coded decimal (BCD) date configurations, expanding date-storage windows across Enscribe files, and deploying the BASE24 Year 2000 System Assessment frameworks globally.
Era 3: Enterprise Platform Shift & Consolidation (2001–2014)
Geopolitical & Industry Context: Post-9/11 regulatory changes (e.g., USA PATRIOT Act), the implementation of modern security standards like Triple DES (TDES), and the birth of the PCI-DSS (Payment Card Industry Data Security Standard). Mainframes and alternative hardware processors (IBM, HP-UX) became fierce competitors to Tandem.
Corporate Dynamics: TSA officially rebranded to ACI Worldwide, Inc. (ACIW) in 2007. A strategic decision was made to rewrite the platform to break vendor lock-in and provide cross-platform flexibility.
Year-by-Year Code & Technical Milestones:
2001–2002: Standard cryptographic layers within BASE24 are systematically modified to enforce Triple DES compliance across automated teller machines.
2003: ACI introduces BASE24-eps (Enterprise Payments System). This marked a foundational architecture shift, moving away from TAL/pTAL entirely to an object-oriented paradigm written in C++ and designed to execute cross-platform (HPE NonStop, IBM z/OS, AIX, Linux).
2005–2006: BASE24-es/eps code integrates with enterprise middleware layers such as IBM WebSphere MQ, using CICS containers on z/OS to deliver modern service-oriented architecture (SOA) web services wrappers.
2008–2010:ACI shocks the banking industry by announcing the sunsetting of standard maintenance for classic Tandem NonStop BASE24 by late 2011. Millions of lines of legacy TAL code are effectively frozen, forcing major migrations toward BASE24-eps.
2011–2013: Code enhancements center around PA-DSS validation and securing encryption pathways to ensure tokenized processing. XPNET 3.x is deployed onto newer HP Integrity Itanium-based J-Series and H-Series blades.
Era 4: Modernization, Cloud-Native, and Open Systems (2015–Present)
Geopolitical & Industry Context: The dominance of Real-Time Payments (RTP, FedNow, ISO 20022 formats), cloud computing mandates, and aggressive cost-reduction pushes away from high-maintenance legacy hardware configurations.
Corporate Dynamics: ACI pivots sharply to open-ecosystem SaaS delivery, cloud partnerships (AWS, Microsoft Azure, Google Cloud), and co-development with IBM to optimize cross-platform throughput.
Year-by-Year Code & Technical Milestones:
2015–2016: BASE24-eps code is successfully ported to Red Hat Enterprise Linux (RHEL) on standard x86 processors. This architectural pivot offered a reduction in total cost of ownership (TCO) compared to legacy hardware by providing massive processing scaling.
2018–2020: The introduction of standard ISO 20022 messaging libraries into the switching matrix to support instant transaction settlement schemes globally.
2021–2024: Legacy middleware systems are phased down. Modern releases feature direct REST API hooks, cloud-adaptor hooks, containerised microservices integration, and extended configuration capabilities via the ACI Desktop GUI.
2025–2026: ACI partners with IBM to launch native 64-bit deployment optimizations for BASE24-eps running on IBM Z mainframes (including z16/z17 configurations), incorporating hardware-driven AI fraud analysis models and full PCI-SSF (PCI 4.0) certification.
Overview of BASE24 and XPNET plus application timeline by era
Mark Whitfield’s premium project management toolkit consists of over 200 editable templates tailored for Agile Scrum, Waterfall, and PRINCE2 frameworks. Built across 30+ years of digital and IT delivery, these frameworks prioritize corporate governance, seamless stakeholder reporting, and visual lifecycle control.
Many POAP, Plan on a Page example templates
Below is the comprehensive, scannable breakdown of the core artifacts categorized by lifecycle focus, purpose, and application format. Purchase project templates here.
📅 1. Master Planning & Visual Roadmapping
These tools serve as the operational foundation for tracking dependencies, defining Work Breakdown Structures (WBS), and establishing executive visibility.
Detailed Software Development Life-Cycle (SDLC) Plan
Focus: End-to-end task tracking from inception and elaboration to construction, testing, and transition.
Format: Microsoft Project (.mpp) & Microsoft Excel (.xlsx).
The choice between PRINCE2 and PRINCE2 Agile depends entirely on your project environment: PRINCE2 is best for highly structured, predictable projects with fixed requirements, while PRINCE2 Agile is designed for dynamic environments that require iterative delivery and flexibility.
Both methodologies are owned by PeopleCert and build upon the same core governance framework.
Core Differences
The table below breaks down how these two frameworks compare across key project dimensions:
PRINCE2 and PRINCE2 Agile features
PRINCE2 Breakdown
Traditional PRINCE2 (Projects IN Controlled Environments) is a structured, process-based approach for project management. It provides a clear blueprint for roles, responsibilities, and management stages.
Fixed Targets: It fixes the project scope, time, and cost upfront to minimize risk.
The 7 Principles: It relies on universal principles, such as continued business justification and defined roles.
Management Stages: Projects are broken into distinct sections to review progress before moving forward.
Predictability: Ideal for large infrastructure, construction, or compliance-heavy projects where changes are costly.
PRINCE2 Agile Breakdown
PRINCE2 Agile does not replace traditional PRINCE2; instead, it wraps agile delivery methods around the existing PRINCE2 governance framework. It allows corporate management to maintain control while development teams use frameworks like Scrum or Kanban.
The Hexagon: It fixes time, cost, quality, and benefits, but makes scope and risk flexible.
Agile Integration: It introduces agile concepts like daily standups, burn charts, and retrospectives.
Maturity Tool: It uses the “Agilometer” to assess if a project is suitable for agile execution.
Speed to Market: Ideal for software development, creative industries, or any project requiring quick consumer feedback.
Which Certification Should You Choose?
Choose PRINCE2 if you work in a traditional industry, need to establish clear corporate governance, or manage projects with strictly defined outcomes.
Choose PRINCE2 Agile if you already work in an agile environment and need to add corporate structure, or if your organization is transitioning from waterfall to agile.
Mark Whitfield, May 2011 – Registered PRINCE2 Practitioner with ILX
The core electronic banking software product sp/ARCHITECT-BANK was originally developed by The Software Partnership (TSP), a highly specialized British software house co-founded by Nigel Walsh in Runcorn, Cheshire.
Engineered to deliver high-availability, fault-tolerant electronic and desktop home-banking services, it ran natively on Tandem NonStop mainframe computers (now HPE NonStop).
The Software Partnership, Norton House, Crowngate, Runcorn, Cheshire
Over the decades, the product evolved through major corporate acquisitions, eventually being integrated into enterprise-level banking suites like CONNEX Advantage under eFunds and FIS.
🌅 Era 1: The Inception and Independent Software House Era (Mid-1980s–1993)
During this foundational era, The Software Partnership engineered the core product from scratch to meet the emerging demand for “Direct Electronic Banking” before the commercial internet became prevalent.
1985: The Software Partnership (TSP) is co-founded by Nigel Walsh in Runcorn, Cheshire. Development begins on a standard product architecture designed specifically for the transaction processing monitor (PATHWAY) and operating system (Guardian) of Tandem Computers.
1988–1989: The company establishes sp/ARCHITECT (and its core module, sp/ARCHITECT-BANK) as a premier client-server base package for corporate and home-office electronic banking.
1990: The engineering team scales up to build standard product releases written in COBOL85 and utilizing NonStop SQL databases. They develop proprietary testing utilities like sp/TESTBED to simulate PC-to-mainframe interfaces. Mark Whitfield joins the company after graduating in Computing in late 1990.
1991: Major deployment begins for the high-profile Barclays Business Master II (BBM II) desktop corporate banking application, with TSP placing teams (including Mark Whitfield) on-site at Barclays in Knutsford, Cheshire.
Barclays, Radbroke Hall, Knutsford, Cheshire
1992: A batch billing and invoicing suite of modules is engineered over 3-months and appended to the Barclays installation at Poole, Dorset. Mark Whitfield is assigned to this HPE NonStop (Tandem) billing/ invoicing development on the UK south coast. Simultaneously, TSP expands internationally into continental Europe.
Barclays, Wimborne Road, Poole, Dorset
1993: TSP develops an automated, touch-tone voice menu system for Girofon (Denmark). The code interfaces phone lines through Periphonics Interactive Voice Response (IVR) hardware directly into the back-end Tandem banking system. Concurrently, the core application handles desktop money transfers and early logic checking for clearing giants TSB and Bank of Scotland. Mark Whitfield is also involved with supporting this IVR technology.
🤝 Era 2: The Deluxe Data International Era (1994–1999)
Recognizing the massive European banking client footprints of sp/ARCHITECT, US-based electronic funds transfer (EFT) specialist Deluxe Data acquired TSP to merge their direct banking and card processing capabilities.
1994: Deluxe Data Corporation acquires The Software Partnership. The Runcorn offices are reorganised as Deluxe Data International Operations.
Deluxe Data International Operations, Wingate House, Northway
1995: The product undergoes heavy code optimization to satisfy customer acceptance loops for international clearers, notably deploying direct electronic banking solutions for major Dutch institutions like Rabobank. Mark Whitfield moves on from Deluxe Data (after 5 years) to Insider Technologies Limited in Salford Quays in late 1995. This to continue HPE NonStop programming work for both monitoring and diagnostic products like Reflex 80:20.
1996: Development transitions toward hybrid enterprise networking. The sp/ARCHITECT system is updated with custom TCP/IP software interfaces to allow newer mid-range UNIX servers (such as IBM RS/6000) to safely communicate with the core Tandem server environment.
1997: Deluxe Data expands the core platform’s messaging logic using Tandem’s Remote Server Call (RSC) facility. This enables early Windows NT operating systems to request live financial data from the sp/ARCHITECT host.
1998: An automated, multi-process file transfer protocol is integrated natively into the bank database, leveraging Connect:Direct transport layers to securely transfer corporate SWIFT financial data files.
🚀 Era 3: The eFunds & Corporate Consolidation Era (2000–2006)
Deluxe Data’s technologies spun off into a new corporate entity called eFunds Corporation, altering the delivery model of the legacy software.
2000: Deluxe Electronic Payment Systems officially merges with other divisions to form eFunds Corporation (EFD). The sp/ARCHITECT package becomes a core pillar of eFunds’ international banking portfolio.
2002–2004: To modernise the transaction handling backbone, components of the sp/ARCHITECT platform are refactored. The system’s underlying communication routing is systematically aligned with CONNEX, a dominant market-leading Electronic Funds Transfer (EFT) processing engine.
2005–2006: eFunds transitions the direct client-server software layers into highly secure corporate portals, providing the foundational logic for what would eventually be rebranded as the CONNEX Advantage banking solution.
🏢 Era 4: The FIS Integration and Legacy Modernisation Era (2007–Present)
The final stage of the product timeline represents its absorption into global banking infrastructure software, where its high-availability DNA remains active in institutional transaction environments.
2007: Financial technology behemoth Fidelity National Information Services (FIS) acquires eFunds Corporation for approximately $1.8 billion. Following industry consolidation, the corporate remnants of the original TSP Runcorn operations are absorbed into Fidelity National Information Services (FIS) and relocated to Aegon House in Daresbury, Warrington.
Fidelity National Information Services (FIS) Aegon House, Warrington (in 2007)
2010: FIS fully absorbs the remaining codebase, utilizing its core Tandem architecture algorithms to fortify transaction processing stability.
2015–2020: The architectural concepts pioneered by sp/ARCHITECT-BANK continue to govern high-volume legacy systems. The logic stays preserved in COBOL85 code bases running on modern HPE Integrity NonStop (Intel Xeon-based) fault-tolerant environments.
2020s–Present: Modern banking infrastructures gradually migrate from the classic database frameworks toward microservice configurations and open-banking APIs. However, the core system layout remains a primary point of historical reference for designing high-throughput, 24/7/365 fault-tolerant banking systems.
sp/ARCHITECT-BANK originally developed by The Software Partnership (TSP), Runcorn, Cheshire
sp/ARCHITECT-BANKCode Evolution Timeline
The timeline below details how the code’s core design, language implementations, and application deployment strategies transformed by era and year.
1. The Monolithic & TAL Foundation Era (1980s – Early 1990s)
During this era, the application focus was strictly high-throughput, fault-tolerant electronic funds transfer (EFT) and point-of-sale (POS) switching systems natively built for Tandem Guardian environments.
Late 1980s: The core design of sp/ARCHITECT is established using TAL (Tandem Application Language). Applications are deployed as single-system monoliths. Code optimization focuses heavily on low-level bit manipulation and message structuring to survive CPU or inter-process failures without losing in-flight transactions.
1991–1993: Structuring of modular execution libraries. Early iterations of the codebase segment transaction processing routes from core database logging routines. The introduction of Tandem’s newer NonStop SQL forces early integration layers to transition from standard unstructured unstructured file systems (Enscribe) to early relational tracking.
2. Distributed Client/Server & pTAL Migration Era (Mid 1990s – Early 2000s)
The architectural demands shifted from single-frame monoliths toward distributed banking systems, giving rise to “Distributed Monoliths” and client/server network structures.
1995–1996: Hardware evolutions transition from the older CISC-based Tandem systems to RISC architectures (MIPS processors). sp/ARCHITECT undergoes a massive compilation shift to pTAL (portable TAL) to preserve legacy code performance across new instruction sets.
1998–1999: Tandem’s acquisition by Compaq pushes the software suite to handle open standard protocols. The application code begins abstracting system calls to prepare for broader networking interfaces.
2001–2003: Deluxe Data / eFunds eras. The code sees the introduction of C/C++ wrappers around the legacy pTAL components. Systems are decoupled into a clear 3-Tier architecture: front-end terminal networks, back-end pTAL transactional engines, and standardized clearing houses.
3. Open Systems, Modern Middleware, & Java Integration Era (Mid 2000s – 2010s)
Following HP’s acquisition of Compaq and subsequent software realignments, the sp/ARCHITECT codebase was re-engineered to prevent vendor lock-in and adopt modern enterprise standards.
2005–2007: Java is introduced into the sp/ARCHITECT ecosystem. New application modules, specifically merchant portal interfaces and settlement reporting tools, are written entirely in Java and run via OSS (Open System Services) environments.
2010–2012: FIS acquisition era integration. Legacy pTAL code blocks are systematically refactored or heavily wrapped in C++ using object-oriented principles to ensure long-term maintenance. The transaction routing engine is altered to support early SOA (Service-Oriented Architecture) paradigms via web-services hooks.
2015–2018: Mainstream deployment of COB (Core Banking) standard formats within the application layer. The system moves away from old proprietary network messaging layouts to ISO 20022 compliance frameworks, utilizing dedicated conversion engines native to the sp/ARCHITECT stack.
4. Modern Cloud-Adjacent & Hybrid Infrastructure Era (2020s)
The current evolutionary footprint centers on maintaining the absolute sub-millisecond reliability of the core architecture while exposing capabilities to dynamic cloud endpoints.
2021–2023: Modernization of the application payload. High-performance micro-frontends handle real-time fraud monitoring and data streaming using asynchronous event-driven pipelines (e.g., Kafka event consumers interfacing directly with the NonStop core runtime environments).
2024–2026: Transition to containerized orchestration and cloud-adjacent infrastructure. The sp/ARCHITECT footprint utilizes x86-based virtualized NonStop systems (NSX), enabling legacy core modules (derived from the original TAL logic) to execute seamlessly on modern virtual environments alongside Linux-based multi-tenant applications.
Insider Technologies Limited is a specialized UK-based software house and service provider that engineers high-availability monitoring, tracking, and cybersecurity solutions for business-critical, 24/7 mission-critical architectures. I worked at ITL in Salford Quays from 1995 through to 2013.
Attending an EBUG conference (European BASE24 User Group)
Foreground, attending a British Isles TANDEM User Group (BITUG)
Insider Technologies Limited (website author in 2009)
CompanyOverview
🏢 Corporate Identity & Status
Legal Name: Insider Technologies Limited
Founded:27 February 1989
Headquarters: Manchester, UK (Albert Street, Eccles)
Ownership: Operating as a private independent software company, recently integrated as part of PartnerOne.
Strategic Partnerships: Certified Microsoft Gold Partner for Application Development and long-standing Hewlett Packard Enterprise (HPE) partner.
Insider Technologies Limited (ITL) in 2001, Salford Quays, Chandlers Point
🌐 Core Domain & Industries Served
The company delivers real-time, event-driven diagnostic, tracking, and compliance middleware solutions across three main highly-regulated global verticals:
Government & Defence: Secure enterprise military messaging tracking and digital evidence handling.
Telecommunications: Tracking data traffic and critical infrastructure middleware.
🛠️ Core Technology Stack & Competencies
Insider Technologies specializes in niche high-availability operating environments—specifically HPE NonStop (historically Tandem Computers and HP NonStop) running Guardian and Open System Services (OSS) environments—alongside enterprise Windows, Linux, and Unix systems. Their expertise spans database transaction management, BASE24 XPNET monitoring, IBM WebSphere MQ tracking, and low-level development (SQL, TAL, TACL, COBOL85, C++, Pathway).
Insider Technologies – Core products in 2003
In-Depth Product & Political-Technical Timeline
This timeline breaks down how Insider Technologies evolved its software suite. It demonstrates how their technical development directly responded to shifting geopolitical landscapes—ranging from late-Cold War military messaging security to post-9/11 financial regulations and modern European cloud autonomy initiatives.
🔹 The Foundation & Legacy Tandem Era (1989–1999)
Political Context: The final years of the Cold War and the 1990s globalization boom demanded high-security, fault-tolerant mainframes for NATO-aligned military communications and early global banking clearing networks.
Technical Context: Tandem Computers dominated the un-interruptible 24/7 market. Software was required to monitor these platforms without causing processing overhead.
1989
Company Incorporation: Insider Technologies is incorporated in the UK to engineer bespoke software for highly robust technical ecosystems.
1990–1995
Reflex (Core Release): Release of Reflex, a foundational service management and real-time transaction diagnostic tool built specifically for the Tandem Guardian operating system.
1996–1999
MultiBatch Software: Further Develop and Extend MultiBatch to orchestrate and safely automate complex batch processing on Tandem machines alongside the evolution into HP NonStop computing frameworks.
Y2K Compliance Focus: Technical adjustments were deployed across Reflex and MultiBatch to assure financial institutions that automated transaction logging would not fail during the millennium rollover.
🔸 The Multi-Platform & Financial Compliance Era (2000–2015)
Political Context: Following the September 11 attacks, global anti-money laundering (AML) and counter-terrorism financing (CTF) frameworks heavily expanded. Financial regulators demanded exact, audible end-to-end payment tracking.
Technical Context: Enterprises began migrating away from single-architecture mainframes toward heterogeneous IT environments, requiring tools that could jump across Windows, Unix, and Linux simultaneously.
2002–2004
Sentra Development: Launch of Sentra, expanding the firm’s portfolio beyond HPE NonStop into cross-platform environment monitoring for Windows, Linux, and Unix systems.
Reflex 80:20 & Reflex ONE24: Advanced variations of the Reflex tracking system were built to cater to specialized real-time electronic payment flows like BASE24 with XPNET.
2005–2010
RTLX Reactor (page 12) and Middleware Monitoring: The release of RTLX Reactor provided message tracking capabilities tailored for IBM WebSphere MQ, allowing institutions to trace various payment and other data through complex middleware chains.
Corporate Structuring: The creation of Insider Technologies (Holdings) Limited reinforced corporate expansion as the company deepened its footprint in secure military messaging for government defense bodies.
🔹 The Cyber Autonomy & Sovereignty Era (2016–Present)
Political Context: Escalating nation-state cyber warfare, strict GDPR regulations, and the UK/EU push for technological sovereignty and domestic digital ecosystem resilience heightened the reliance on trusted, onshore technology suppliers.
Technical Context: High-threat environments demand zero-trust visualization, time-accurate logging across digital evidence files, and advanced protection against internal exfiltration vectors.
2019
30-Year Milestone & Modernization: The company celebrates its 30th year, accelerating development on modern mobile application extensions to permit real-time, remote secure alerts for operations teams.
2022–2025
PartnerOne Integration: Insider Technologies aligns its operations under the PartnerOne portfolio, preserving its UK identity while supercharging its enterprise-scale data infrastructure solutions.
Corporate Integration combines Insider’s expertise with PartnerOne’s portfolio to deliver advanced analytics and secure messaging systems to banking, defence, and telecommunications markets.
Defense and Public Safety Porting: Technical deployment of specialized capabilities covering digital evidence security, timekeeping tracking, and legacy virtualization modules aimed explicitly at helping the UK Government maintain its historical tech stacks safely.
RTLX Reactor (in 2012) for tracking BASE24-eps & BASE24 XPNET transactions
Insider Technologies Limited (ITL), Company Overview and Timeline by Year
The Insider RTLX product at ETI-NET is now called C-Deep for Transaction Monitoring;
Mark Whitfield is a Greater Manchester-based Senior IT Project and Engagement Manager.
With over 30 years in the IT and software development industry, he has continuously upskilled in project delivery, Agile methodologies, cloud platforms, and cyber security.
Phase 1: Foundational Education
1985 – 1988: Leigh College, UK
Focus: Computer Science and Biology (‘A’ Levels)
1988 – 1990: University of Greater Manchester (formerly Bolton Institute of Higher Education, BIHE)
Focus: Higher National Diploma (HND) in Computer Studies (Graduated with Distinction; First overall in the year)
Key Modules: System Analysis, Programming Methodology, Database Architecture, and Business Information Systems
Phase 2: Project Management & Professional Training
2000 – 2006: Industry Integration & Early Methodologies
Focus: Service-Oriented Architecture (SOA), Agile, Sales, and early project management
Courses/Certifications: Sales and Marketing (In-house Outsource, 2001), Web Services and SOA (Insider Technologies, 2005), PRINCE2 Foundation (2006), Designing Good Marketing Literature (SkillPath Seminars, 2006)
2009: Digital & Communications
Focus: Digital marketing and content
Courses: Writing for the Web, and Website Promotion and Visibility by Design (iTrain Education)
2011: Structured Frameworks
Focus: Formal project frameworks and delivery methodologies
Courses/Certifications: PRINCE2 Foundation & Practitioner (ILX Group), Agile Scrum (RADTAC)
2012: Operational Management
Focus: Service management best practices
Courses/Certifications: ITIL Foundation
Phase 3: Advanced Engagement & Enterprise Training
2017 – 2019: Capgemini Engagement & Compliance
Focus: High-level engagement management and corporate governance
Courses/Certifications: Advanced Engagement Management Certification (Level 2), Group Anti-Corruption, and Intellectual Property Rights (IPR) Training
2022: Cloud Modernization
Focus: Enterprise cloud computing fundamentals
Courses/Certifications: AZ-900 Microsoft Certified Azure Fundamentals
The blog posts by Mark Whitfield, a Senior IT Project and Engagement Manager, primarily focus on practical project management (PM) frameworks, methodology implementation, and digital delivery execution.
Hosted on his platform, PROject Templates, the blog acts as an extension of his 30+ year career transitioning from mainframe engineering to leading large-scale Agile and Waterfall digital transformations.
Blog Overview and Key Topics
The core purpose of the blog is to guide project professionals through real-world deployment challenges while showcasing an ecosystem of over 200 editable Microsoft Office templates.
The main content focus areas include:
Framework Implementation: In-depth overviews on aligning project lifecycles with PRINCE2 (7th Edition), Agile Scrum, and Kanban methodologies.
Detailed Project Planning: Actionable steps for setting up Software Development Life Cycles (SDLC), defining dependencies, establishing milestones, and handling project baselines.
Risk and Governance Control: Best practices on organizing and managing RAIDs logs (Risks, Actions, Issues, Dependencies), change requests, and corporate project governance.
High-Level Reporting: Frameworks for structural communication with stakeholders, utilizing Plan on a Page (POaP) examples, dashboard designs, and financial budget tracking templates.
Digital & Cloud Delivery Lessons: Real-world insights drawn from his corporate and public sector experiences, covering topics like middleware architecture deployments and hybrid cloud application refactoring.
In Europe, “free” higher education almost always refers to zero tuition fees at public universities, though you will still need to pay for living expenses (rent, food, books). No European country requires student loans; rather, loans are an optional choice to fund living costs.
Use the regional breakdown below to see which countries offer zero tuition and which generally require you to pay.
Countries with Free (or Almost Free) Tuition
Countries with Free (or Almost Free) Tuition
These countries charge no tuition fees (or very minimal administrative fees) for eligible students:
Germany: Public universities are completely tuition-free for both domestic and international students, including those from outside the EU. You only pay a small semester fee (approx. €150-€350).
Norway: Free of charge for all students, regardless of nationality.
Austria: Free for EU/EEA students. For non-EU students, the fee is generally a very low €727 per semester.
France: Public university tuition is heavily subsidized and extremely low (approx. €170 to €2,700 per year, depending on the degree).
Iceland: Free tuition at public universities, though a registration fee of roughly €400-€600 is required.
Czech Republic: Public universities are free if you study a program taught in the Czech language. English programs require tuition.
Greece: Free tuition for EU/EEA nationals; non-EU students pay very low fees (around €1,500/year).
Poland: Tuition is free for Polish citizens and EU/EEA students.
Countries with Free Tuition for EU/EEA Students Only
These countries offer free degrees if you are a European citizen, but charge international (non-EU/EEA) students:
Denmark: Free for EU/EEA students; international students pay up to €16,000 per year.
Sweden: Free for EU/EEA students; international students pay full tuition.
Finland: Free for EU/EEA students. Non-EU students pay tuition for English-taught programs.
Slovenia: Free for full-time undergraduate students from the EU.
Countries That Generally Require Tuition (and Potential Loans)
In these countries, you will pay tuition fees ranging from a few hundred to several thousand Euros per year, making student loans or personal savings more necessary:
United Kingdom: In England and Wales, tuition fees can cost up to £9,250 a year for domestic students, and higher for international students. Students heavily utilize the government’s Student Loans Company to cover both fees and maintenance.
The Netherlands: Yearly tuition fees for EU students are around €2,500, with higher fees for international students. Dutch citizens and eligible EU students can take out loans through DUO.
Italy & Spain: Both charge moderate tuition fees for public universities based on family income or the specific region, making it much more affordable than the UK but rarely entirely free without scholarships.
Salesforce MuleSoft is an industry-leading Integration Platform as a Service (iPaaS) and automation solution that enables organizations to securely connect data, applications, and devices across hybrid cloud and on-premises environments. Instead of relying on rigid, custom-coded point-to-point connections, MuleSoft uses an API-led connectivity approach. This methodology treats every system connection as a modular, reusable building block (System, Process, and Experience APIs).
October 2018 – June 2019, was assigned as a Delivery Manager at MuleSoft
Core Capabilities
Anypoint Platform: The flagship product covering the entire lifecycle of API design, testing, deployment, governance, and monitoring.
MuleSoft Automation: A suite combining Composer (no-code integration for business teams) and Robotic Process Automation (RPA) to automate workflows across legacy and modern platforms.
Salesforce Ecosystem Synergy: Acts as the data integration engine for Salesforce Customer 360, bringing siloed third-party systems together to establish a single customer view.
Outcome Based Delivery (OBD) Model, C4E, Center for Excellence
Detailed Timeline Breakdown
The evolution of MuleSoft spans four distinct eras, progressing from a niche open-source project to an enterprise integration powerhouse, culminating in its massive acquisition and expansion under Salesforce.
Era 1: The Open-Source Roots (2003 – 2008)
This era focused on addressing the tedious “donkey work” of custom data integration through open-source software.
2003: Developer Ross Mason creates the Mule open-source project. He writes an architecture framework to move away from rigid, proprietary integration infrastructure. The project name stems from the literal “mule work” or drudgery of writing point-to-point connections.
2006: Ross Mason and Dave Rosenberg co-found MuleSource in San Francisco. The company is built to commercialize the open-source Mule Enterprise Service Bus (ESB) project.
2007: Lightspeed Venture Partners leads a Series A funding round to back the growing open-source platform.
2008: The company expands its product landscape by focusing on developer adoption and expanding core enterprise middleware features.
Era 2: Cloud Transition and iPaaS Transformation (2009 – 2016)
During this era, the company pivoted to a subscription-based software-as-a-service model, targeting cloud applications and APIs.
2009: The company officially changes its name from MuleSource to MuleSoft. Greg Schott is hired as CEO to restructure the business, transitioning from a pure open-source model to a hybrid commercial enterprise subscription model.
2010: The development of dedicated cloud tools kicks off, responding to a massive industry shift from on-premises systems toward software-as-a-service (SaaS) applications.
2012: MuleSoft launches CloudHub, the industry’s first true multi-tenant Integration Platform as a Service (iPaaS).
2013: MuleSoft acquires ProgrammableWeb, the leading repository for web application programming interfaces (APIs), positioning itself as the voice of the emerging API economy.
2014: The company officially rolls out the Anypoint Platform, a unified product suite designed to dismantle the barriers between data applications, SaaS platforms, and APIs.
2015: MuleSoft secures a $128 million funding round led by New Enterprise Associates, with Salesforce Ventures participating as a strategic investor. Revenue breaks past the $100 million mark.
2016: The enterprise focus shifts entirely toward championing API-led connectivity over standard enterprise service bus middleware architectures.
Era 3: IPO and the Salesforce Acquisition (2017 – 2018)
The era defined by rapid financial maturation and a landmark enterprise SaaS consolidation.
2017: MuleSoft launches its Initial Public Offering (IPO) on the New York Stock Exchange under the ticker symbol MULE, valuing the business at over $1.5 billion on its first day of trading.
2018 (March): Salesforce announces a definitive agreement to acquire MuleSoft for an enterprise value of approximately $6.5 billion, making it Salesforce’s largest acquisition up to that point.
2018 (May): Salesforce completes the acquisition. MuleSoft is positioned to power the new Salesforce Integration Cloud to unlock legacy and external database silos for CRM clients.
Era 4: Modern Era—Automation and Unified Customer 360 (2019 – Present)
This era represents the deep technological coupling of MuleSoft with cloud architecture, AI, and low-code applications.
2019: Salesforce shifts strategy, abandoning the “Integration Cloud” branding to lean heavily on the trusted MuleSoft brand. The technology is deeply embedded directly into core platforms like Sales and Service Clouds.
2020: MuleSoft updates its core data engine engine with Mule 4, optimizing performance, reducing custom script overhead, and easing API lifecycle management workflows.
2021: The brand releases MuleSoft Composer, a click-based, no-code application integrated directly inside the Salesforce user interface, enabling business users to connect systems without relying on IT engineers.
2022: Salesforce expands MuleSoft’s reach beyond APIs by acquiring Servicetrace and launching MuleSoft RPA, building a comprehensive hyper-automation ecosystem alongside Composer.
2023–2024: MuleSoft adapts to the AI revolution by releasing Anypoint Code Builder and embedding Einstein AI into the workflow. Developers use natural language prompts to automatically generate integration flows and API designs.
2025–2026: MuleSoft is fully integrated as a core architectural foundation for Salesforce Data Cloud and Agentforce. It serves as the primary system of connectivity to securely feed legacy, real-time enterprise data into autonomous AI agents.
Salesforce MuleSoft Overview & Development Timeline
1. Welcome Salesforce, London Office2. Welcome Salesforce, London Office (external)
The development of programming languages on the HPE NonStop platform (originally founded as Tandem Computers) is tightly bound to its architectural hardware transitions: from custom CISC stack machines to MIPS RISC, Intel Itanium, and eventually standard Intel x86-64 infrastructures.
Detailed List of NonStop Programming Languages
1. Core Proprietary & System Languages
TAL (Transaction Application Language): The foundational system programming language for Tandem. It is a block-structured, machine-dependent procedural language designed to compile directly into highly efficient machine instructions. It features ALGOL/Pascal-like syntax but implements C-like semantics, structural pointers, and weak data typing.
pTAL & epTAL: Specialized evolutions of TAL. Rather than rewriting legacy codebases from scratch during architecture shifts, pTAL was introduced to compile existing TAL code natively into MIPS RISC architectures. Later, epTAL was developed to target Intel Itanium microprocessors.
TACL (Tandem Advanced Command Language): A built-in command interpreter and interpreted scripting language. It functions like a Unix Bash shell but features highly complex macro capacities used to orchestrate system configurations, monitor processes, and automate failover procedures.
2. Enterprise & Enterprise Legacy Languages
COBOL85 (and older COBOL74): The undisputed workhorse of NonStop commercial workloads. HPE’s tailored implementation of the COBOL85 standard natively interfaces with the Guardian OS. It allows programmers to embed SQL/MP statements and program fault-tolerant Process Pairs through HPE NonStop Pathway (TS/MP).
SCOBOL (Screen COBOL): A specialized, high-level structural derivative of COBOL utilized exclusively to build blocks for character-cell terminal interfaces (such as the 6530 terminal environments) running within Pathway architectures.
NonStop SQL (SQL/MP and SQL/MX): While technically a database system, its embedded syntax acts as a declarative language integrated into C and COBOL. SQL/MP works with the legacy Guardian file system, while SQL/MX brings ANSI-compliant SQL closely bound with the Open System Services (OSS) environment.
3. Standard Mainstream Languages
C & C++: Heavily introduced during the RISC transition to allow software portability. Mainstream development on modern NonStop systems uses standard C/C++ cross-compilers. They run in either the native fault-tolerant Guardian personality or the standard POSIX-compliant Open System Services (OSS) environment.
Java: A first-class language layer deployed natively on NonStop. HPE optimizes the Java Virtual Machine (JVM) to scale across multi-CPU shared-nothing frameworks, allowing modern enterprise web apps to run with out-of-the-box system availability.
4. Modern Open-Source Options
Python, Go, & JavaScript (Node.js): Modern procedural and script utilities provided by HPE. These environments leverage the OSS POSIX platform layer, running modern DevOps orchestration, microservices, and hybrid-cloud pipelines alongside the native database engines.
Detailed Timeline Breakdown by Era and Year
The evolution of NonStop languages maps directly across distinct engineering ownership eras.
The Proprietary Foundation Era (Tandem Computers: 1974–1989)
1976: Tandem ships the original Tandem/16 (NonStop I). TAL is the only available language on the platform. The entire Guardian Operating System is written completely in TAL.
1981: The NonStop II hardware is introduced. Tandem expands language support to include COBOL74, FORTRAN, and BASIC to attract mainstream banking clients.
1983: Tandem releases the Transaction Monitoring Facility (TMF) and Pathway application management software. SCOBOL is introduced alongside them to program secure terminal entry interfaces.
1985: TACL is deployed, completely modernizing the command line shell ecosystem with scalable macros and structured operational control.
1986: Tandem launches NonStop SQL, the first linearly scalable, fault-tolerant relational database engine. Embedded SQL syntax is integrated directly into TAL and COBOL compilers.
1988: Compilers undergo a major update to natively support the newly established COBOL85 standard, which quickly replaces COBOL74 for all mission-critical banking transactions.
The Open Systems & Hardware Transition Era (Compaq: 1990–2001)
1991: Hardware migrates from CISC stacks to MIPS RISC architectures with systems like the Cyclone/R. To protect client software assets, Tandem delivers the pTAL compiler to translate TAL source code into native RISC binaries.
1995: Tandem introduces Open System Services (OSS), a POSIX-compliant UNIX subsystem running over the Guardian kernel. This brings full-scale, native native compliance for standard ANSI C and C++ programming.
1997: Compaq acquires Tandem Computers. Engineering shifts heavily toward implementing Java on NonStop, targeting cross-platform, enterprise internet-banking codebases.
2000: NonStop SQL/MX is released. It allows developers to use embedded SQL statements within standard C, C++, and emerging Java applications inside the OSS runtime environment.
The Corporate Alignment & Itanium Era (Hewlett-Packard: 2002–2014)
2002: HP merges with Compaq. Java is designated as a first-class citizen on the platform, receiving deeper optimization to tie into native clusters seamlessly.
2005: HP releases the Integrity “NonStop i” servers, moving processors away from MIPS onto Intel Itanium architectures. The epTAL compiler is rolled out alongside standard C/C++ updates to seamlessly compile older environments onto Itanium.
2011: Open-source scripting engines, including early ports of modern Python, are introduced to the OSS environment, easing the system-management burden for engineers unfamiliar with legacy TACL.
The Modern Enterprise Era (Hewlett Packard Enterprise: 2015–2026)
2015: HP splits, and the platform transitions to HPE. Standard Intel x86-64 hardware dominates with the NonStop X architecture. Compilers utilize an standard GCC/LLVM-based back end, allowing normal Linux/Unix C++ programs to build on NonStop with minimal alteration.
2020: Sales of Itanium systems officially terminate. Legacy languages like TAL are deprecated for new software creation but are preserved to support older, foundational logic.
2023–2024: HPE rolls out modern cloud-ready DevOps Starter Kits. Full, native support is added for modern languages such as Go, modern Python 3.x, and Node.js, allowing them to integrate into modern automated CI/CD build environments.
HPE NonStop Tandem Programming Languages and Development Timeline
Typical Agile Scrum Master interview questions evaluate your understanding of the Scrum Framework (the 3-5-3 structure), your ability to facilitate continuous improvement, and your soft skills in conflict resolution and servant leadership.
The questions generally fall into four core categories:
1. Scrum Fundamentals & Frameworks
These questions test your technical knowledge of Scrum and how it compares to other frameworks.
Explain Scrum vs. Agile: Agile is the overarching mindset and set of principles; Scrum is a specific, lightweight framework for implementing Agile.
The 3-5-3 structure: What are the three roles (Product Owner, Scrum Master, Developers), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), and three artifacts (Product Backlog, Sprint Backlog, Increment)?
Scaling Agile: What experience do you have scaling Agile (e.g., SAFe, Scrum of Scrums, Nexus) if the organization is large?
2. Facilitation & Coaching
Interviewers want to see how you run events, coach Product Owners, and improve team delivery.
Daily Scrum: What is your approach to running the Daily Scrum, and how do you prevent it from becoming just a status update?
Retrospectives: What specific techniques or games do you use to keep retrospectives fresh and actionable?
Definition of Done (DoD): How do you help a team create and adhere to a clear Definition of Done?
Metrics: How do you track a team’s effectiveness (e.g., velocity, sprint goal success, cycle time, burndown charts)?
3. Behavioral & Situational Scenarios
These “tell me about a time when…” questions assess your real-world experience.
Team Conflict: Can you describe a time when you had to resolve a conflict between team members or between a developer and the Product Owner?
Resistant Teams: What would you do if a team member or stakeholder doesn’t see the value in Scrum ceremonies and refuses to participate?
Management Intervention: How do you handle managers or executives who try to bypass the Scrum process or assign work directly to the developers?
Scope Creep: How do you handle sudden mid-sprint requirement changes or scope creep?
4. Self-Awareness & Servant Leadership
Hiring managers ask these to test your humility and growth mindset.
Your Greatest Failure: Can you share a time you failed as a Scrum Master, and what you learned from the experience?
Protecting the Team: How do you say “no” to leadership or protect the team from external noise while still serving the broader organization?
__________
More Agile Scrum Questions with Example Answers:
Mastering a Scrum Master interview involves demonstrating a deep understanding of servant leadership, the Agile mindset, and hands-on experience navigating team dynamics. Below are the most common interview questions, summarized with strategic, industry-recommended answers to help you stand out.
Core Scrum Framework & Mechanics
Question 1: Explain the 3-5-3 structure of Scrum.
What they’re looking for: A solid foundation in Scrum basics.
Recommended Answer: “Scrum is governed by a ‘3-5-3’ rule: 3 roles (Product Owner, Scrum Master, Developers), 5 events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), and 3 artifacts (Product Backlog, Sprint Backlog, Increment).”
Question 2: What is the difference between a Product Backlog and a Sprint Backlog?
What they’re looking for: Understanding of backlog management and scope.
Recommended Answer: “The Product Backlog is a continuously evolving, prioritized list of everything needed for the product, owned by the Product Owner. The Sprint Backlog is a subset of the Product Backlog—it’s the specific forecast of items the team commits to delivering during the current sprint.”
Behavioral & Situational Questions
Question 3: How do you handle conflict within the Scrum team?
What they’re looking for: Your facilitation and conflict-resolution skills, avoiding direct intervention where the team can self-manage.
Recommended Answer: “I avoid playing the role of a micromanager. Instead, I facilitate open dialogue and encourage the team to address the conflict directly using the Scrum values of openness and respect. My goal is to guide them to find a mutually agreeable solution while fostering an environment of psychological safety.”
Question 4: What do you do if a team member refuses to adopt Scrum practices?
What they’re looking for: Change management skills and patience.
Recommended Answer: “I first try to understand the root cause of their resistance, as it usually stems from a lack of understanding or fear of change. I would have a private one-on-one conversation to address their concerns. I might pair them with an experienced Agile advocate or use team-building exercises to demonstrate the value of Scrum in a low-pressure way.”
Leadership & Stakeholder Management
Question 5: Tell me about a time you had to challenge leadership or management.
What they’re looking for: The courage to protect the team’s focus and uphold Scrum principles.
Recommended Answer: “I once had a stakeholder attempt to bypass the Product Owner and directly assign high-priority tasks to Developers mid-sprint. I respectfully but firmly challenged this by explaining how breaking the Sprint Goal jeopardizes the team’s focus and the project’s overall velocity. I then helped the stakeholder work with the Product Owner to place the new task in the Product Backlog for the next sprint planning.”
Question 6: How do you measure if your team is truly Agile?
What they’re looking for: Focus on delivering value over measuring arbitrary metrics like velocity.
Recommended Answer: “Velocity is for planning, not for measuring success. I look at outcome-based metrics, such as Sprint Goal success rates, customer satisfaction scores, time-to-market, and the quality of increments. The ultimate measure is whether we are continuously delivering iterative business value to our end users.”
In the 1980s, GCE O-Level grades ranged from A to E (where A, B, and C were considered passing). Due to grade inflation and changes in the curriculum over the decades, an O-Level grade C is roughly equivalent to a Grade 4 in the current numerical GCSE system, while an O-Level grade A equates to a Grade 7 or 8.
A direct, point-by-point comparison between the O-Level system of the 1980s and today’s numerical GCSE grades reveals the following equivalence:
O-Level grade C is equivalent to Grade 4, while O-Level grade A equates to Grade 7/8
Important Differences in System Design
Grading Method: O-Levels were norm-referenced, meaning a fixed percentage of students received each grade every year, regardless of the overall score. Today’s GCSEs are criterion-referenced, meaning grades are awarded based strictly on the skills and knowledge the student demonstrates, with grade boundaries adjusted accordingly.
Cohort Reach: In the 1980s, O-Levels were designed for the top 20–25% of the academic cohort, while the next 40% took CSE (Certificate of Secondary Education) exams. The modern GCSE is designed to cater to the vast majority of all abilities.
Assessment & Breadth: O-Levels were almost entirely dependent on final, high-stakes written exams, whereas modern GCSEs require more breadth across a wider range of subjects and rely heavily on 9-1 scoring.
Direct comparison between O-Level system of 1980s and today’s numerical GCSE grades
A Plan on a Page (POAP) is a concise, visual summary of a project’s core elements. It distills complex, granular project details into a highly accessible, single-page format.
It acts as an executive summary rather than a replacement for comprehensive, detailed project plans. Example, tailorable Agile and Waterfall MS PowerPoint POaP project templates can be purchased at this link.
Plan On a Page also known as a POAP
🎯 Primary Purpose
Executive Communication: Provides busy stakeholders and C-level management with rapid visibility into a project’s status without overwhelming them with data.
Alignment: Ensures teams, sponsors, and stakeholders share a unified understanding of project goals and direction.
Focus & Risk Management: Keeps the strategic vision front-and-center, prevents teams from getting “lost in the weeds,” and allows leaders to spot high-level risks early.
Decision Support: Serves as a quick reference guide during steering committee and status meetings.
A Plan on a Page (POAP) is a concise, visual summary of a project’s core elements
📝 Content Summary
To fit on a single page, a POAP strips away tactical daily tasks and focuses only on the most critical strategic and timeline components:
Project Vision & Scope: A concise statement of what the project aims to deliver.
Objectives & KPIs: Specific, measurable targets and Key Performance Indicators to measure success.
Visual Timeline: A high-level roadmap, Gantt chart, or phase-based breakdown (e.g., Discovery, Execution, Launch) displaying major milestones.
Project Health/Status: Current RAG (Red/Amber/Green) status or progress tracking.
Resource & Budget Allocation: High-level overview of assigned budget and key personnel.
Risk & Dependencies: Notable blockers, constraints, or critical assumptions.
Governance & Contacts: The project sponsors, managers, and the best way to get support.
All POAP templates can be purchased by clicking on the link on the website banner
Hindley Park High School (originally founded as Hindley and Abram Grammar School) was a historic secondary school located on Park Road in Hindley, Wigan, Greater Manchester. I attended the school from 1980 thru 1985.
Operating under its final name until its closure in August 1991, the institution served the local community for over three centuries. The iconic Victorian school building still stands today and serves the region as the Three Towers Academy.
Park High Secondary School, Hindley, Wigan – Overview and Timeline
Full Institutional Description
Location and Campus: Located on Park Road, Hindley, the school campus features a prominent mid-Victorian main building constructed of traditional red brick and stone dressings. The site evolved from a single large schoolroom to include a master’s house, separate classrooms, and the landmark Carlton Villas (acquired in 1937 as headmaster quarters).
Academic Identity: For most of its existence, it operated as a selective Grammar School focusing on classical education, mathematics, and sciences. In its later eras, it transitioned into a non-selective voluntary controlled secondary school managed by the Wigan Metropolitan Borough Council.
Heritage Values: The school holds deep historical significance for the Wigan borough. Its grounds feature two prominent war memorials dedicated to the alumni who perished during World War I and World War II.
Park High Secondary School, Hindley, Wigan – side view of main building
Chronological Timeline Breakdown
Era 1: The Foundations & Lowe Hall (1632 – 1855)
1632:The Hindley and Abram Grammar School is officially established through a charitable foundation. It opens inside “Lowe Hall” off Stony Lane (modern-day Liverpool Road) and is locally dubbed The Lowe School.
1829: The school updates its charter; while originally free, the Headmaster is granted the liberty to charge tuition fees for advanced instruction in Latin, arithmetic, and writing.
1848: The campus layout at Lowe Hall is formally documented for the first time on the inaugural Ordnance Survey map.
Era 2: The Park Road Relocation & Growth (1856 – 1979)
1856: The school outgrows its original home and relocates to a brand-new building on Park Road, anchoring its identity to the “Park” area of Hindley.
1882: The infrastructure expands significantly to accommodate a growing pupil registry. The site now comprises a large central schoolroom, a secondary classroom, and a dedicated headmaster’s residence.
1900s–1930s: The school undergoes rapid student growth. In 1937, the neighbouring Carlton Villas are formally purchased to serve as upgraded residential quarters for the headmaster.
1944–1970s: Following the Education Act of 1944, the school solidifies its role as a key selective grammar school for the Hindley and Abram districts, operating alongside local secondary modern alternatives.
Era 3: The 1980s Transformation (1980 – 1989)
1980–1985: Amidst a nationwide shift away from selective education, the school operates as Hindley Park High School, a voluntary controlled secondary school. It adapts its classical grammar curriculum to broader secondary education requirements.
1986–1888: Financial strain and shifting local demographics within the Wigan Council area prompt institutional reviews regarding school surplus spaces across the borough.
1989: Local education authorities begin formal consultations regarding the consolidation of secondary education in Hindley, outlining plans to phase out the historic Park Road site in favour of expanding Outwood Academy Hindley (then known as Mornington High School).
Era 4: Closure & Modern Reuse (1990 – Present)
1991: On 31 August 1991, Hindley Park High School officially closes its doors to pupils, ending 359 years of direct educational lineage.
1992–2010s: The building is preserved by the local authority and repurposed as a Teachers’ Development Centre.
2020s: The historical complex finds a permanent modern educational use. The facility is occupied by the Three Towers Alternative Provision Academy, ensuring the 1856 building continues to serve local children needing specialised support.
Mark Whitfield is an SC-cleared Senior IT Project and Engagement Manager with over 30 years of experience. His career spans from early mainframe programming to leading multi-million-pound cloud migrations and digital transformations for major financial, utility, and government clients.
The chronological breakdown of his professional project portfolio, structured by his definitive career eras, is detailed below:
1. The Technical Era (1990–1995)
During this foundational era, Mark worked as a Programmer and Lead Analyst for The Software Partnership (acquired by Deluxe Data in 1994). He focused strictly on the development, optimization, and deployment of the sp/ARCHITECT-BANK electronic banking solution on Tandem Mainframe Computers.
Details: Handled the custom design and backend coding for a high-profile desktop electronic business banking application.
Project: Automated Touch-Tone Phone Banking Suite
Year: 1992–1993
Client: Girofon (Denmark)
Budget: Client-retained vendor contract
Details: Coded automated, menu-driven voice solutions operating on a Periphonics VRAM device to fetch live customer balances directly from mainframes.
Project: Early Digital Inter-Account Transfers
Year: 1993–1994
Client: TSB & Bank of Scotland
Budget: Internal product development
Details: Directed logic design and mainframe coding to support pioneering inter-account electronic funds transfers.
Project: International Banking Optimization
Year: 1994–1995
Client: Rabobank
Budget: Vendor-driven custom development framework
Details: Managed localized software optimization, custom patches, and deployment testing for global banking operations.
2. The Infrastructure & Monitoring Era (1995–2014)
Mark transitioned into a Product and Project Manager role at Insider Technologies Limited (and later a brief stint at Wincor Nixdorf). His focus shifted heavily toward platform diagnostics, high-availability transaction monitoring, and financial hardware software integrations.
Project: Reflex (Reflex 80:20) System Co-Development
Year: 1995–2004
Client: Multiple Tier-1 Investment Banks (including Euroclear/Crestco, Bank of England, and Deutsche Bank)
Budget: Part of a broader £3M Management Buyout (MBO) product portfolio
Details: Acted as Senior Programmer and Technical Lead to co-develop diagnostic monitoring modules for high-availability mainframes.
Details: Managed the integration of transaction tracking across ATM networks using ACI’s XPNET and HP NonStop architecture.
Project: Legacy ATM Software Modernisation
Year: 2013–2014
Client: Major UK Retail Bank (via Wincor Nixdorf Professional Services)
Budget: Corporate financial service transformation
Details: Served as Project Manager executing the swap-out of outdated, legacy ATM client systems for modernized software stacks.
3. The Digital and Cloud Era (2014–Present)
This era highlights Mark’s leadership of large-scale Agile and Waterfall digital delivery frameworks, moving from corporate gambling technology to complex, high-budget UK public sector programs.
Project: Mobile & Online Gaming Sportsbook Platforms
Details: Led Agile Scrum development teams to upgrade payment gateways, implement fraud detection, and roll out football/horse racing mobile interfaces.
Project: National Air Space Real-Time Mobile Applications
Year: 2016
Client: NATS (UK-wide Air Traffic Organisation)
Budget: Corporate custom applications initiative
Details: Managed the secure Agile delivery of Apple iOS applications displaying live military and public airspace information.
Project: Core Systems Interface Data Centre Migration
Year: 2016 (May–October)
Client: Royal Mail Group (RMG) / Postal Services
Budget:£4.3 Million
Details: Led a massive cross-functional team of 90 Capgemini engineers to migrate over 1,100 platform data interfaces ahead of peak annual trading.
Project: Automated Call Centre CCaaS Telephony Implementation
Year: 2017 (May onwards)
Client: Local Regional Government
Budget:£400,000
Details: Deployed a programmatic dialler system linked with Microsoft Azure CRM to facilitate the “Support for Mortgage Interest” campaign.
Project: Automotive Online Car Sales and Digital Readiness
Year: 2017 (October)
Client: Jaguar Land Rover (JLR) / Aston Agile Delivery Centre
Budget:£1.1 Million (Split into a £670k Customer Sales Portal and a £430k Readiness project)
Details: Engagement Manager implementing a new-car ecommerce vehicle pipeline.
Budget:£1 Million+ (Part of a larger £13.5M cloud program moving 130 apps)
Details: Orchestrated the launch and configuration of Azure Cloud frameworks migrating 12 historical Dynamics 2016 platforms to Dynamics 365 Online.
Project: Fish Export Service (FES) to CHIP Inspection Portal
Year: 2023–2024 (Nov–Feb)
Client: UK Government / Northern Ireland Trading Framework
Budget:£1 Million+
Details: Served as Technical Delivery Manager directing Agile Scrum teams to build cloud-hosted APIs supporting catch verification under the Windsor Framework.
Mark Whitfield is an SC-cleared Senior IT Project Manager with over 30 years of experience delivering high-availability financial, cloud, and digital transformation projects. Over his career, he has transitioned from deep technical engineering on HPE NonStop (Tandem) mainframe systems to leading major corporate and public sector Agile and Waterfall software rollouts.
A comprehensive, year-by-year timeline breakdown of his project history and clients since 1990 is outlined below.
💻 The Technical Era (1990–1995)
During this period, Whitfield worked as a Programmer and Lead Analyst for The Software Partnership (acquired by Deluxe Data in 1994). He focused on electronic banking software (sp/ARCHITECT-BANK) on Tandem Mainframe Computers.
1990–1992: Barclays Bank – Placed on-site at Knutsford, Cheshire to design and code software for the high-profile Barclays Business Master II (BBM II) electronic desktop banking project.
1992–1993: Girofon (Denmark) – Developed a touch-tone phone banking suite. This allowed clients to use automated voice/menu-driven systems via a Periphonics VRAM device to fetch live balances from back-end mainframes.
1993–1994: TSB & Bank of Scotland – Conducted early-era digital investigations, logic design, and mainframe coding for inter-account desktop money transfers.
1994–1995: Rabobank – Headed software optimization, custom electronic coding patches, and on-site deployment validation for international operations.
🛡️ Monitoring & Infrastructure Era (1995–2013)
Whitfield joined Insider Technologies Limited (ITL) in Salford Quays, specializing in platform diagnostics, transaction monitoring, and financial logging systems for mission-critical infrastructure.
1995–1996: Internal ITL Product R&D – Core developer on the Reflex monitoring suite (Reflex 80:20), creating platform health and diagnostic plug-in modules.
1997–1998: CRESTCo (now Euroclear) – Brought in as a technical infrastructure consultant to run benchmark tests on newly released Tandem S7000 processing hardware nodes.
1999–2001: Bank of England / Deutsche Bank – Deployed real-time tracking protocols utilizing ITL’s MultiBatch scheduling architectures and file monitors.
2002–2003: Hewlett-Packard (HP) – Successfully managed the rigorous certification process for the first HP OpenView Operations (OVO) Smart Plug-In built for the NonStop mainframe environment.
2008–2010: Saudi Arabian Retail Bank – Acted as Project Manager overseeing the cross-border rollout of a high-volume ATM and Point-of-Sale (POS) monitoring system.
2011–2013: Global Payments / Standard Chartered – Integrated transaction monitoring capabilities with external corporate frameworks such as TIVOLI and XPERT24 using ACI’s XPNET architecture.
This timeframe marked a total transition into senior contract project management, dealing directly with multi-million-pound programs.
2013–2014: Lloyds Banking Group (LBG) – Augmented into Wincor Nixdorf as the IT Project Manager leading a £5+ million workstream. This was part of LBG’s comprehensive Self-Service Software Replacement (SSSR) initiative to modernise legacy ATM software.
2014–2016: Betfred – Senior IT Project Manager inside an Agile Scrum structure. Directed cross-functional software vendors to deliver updates for mobile apps (iOS/Android), fraud detection systems, and payment gateways for their digital sportsbook platforms.
In January 2016, Whitfield joined global consultancy firm Capgemini as a Senior client-facing Engagement/Delivery Manager.
2016–2017: Aerospace & Defence Client – Managed an enterprise-level integration project to deploy a Salesforce-driven Single Customer View (SCV) portal platform.
2017–2018: Jaguar Land Rover (JLR) – Served as Project Manager for the iFAB Middleware Project, a complex 12-month architecture development program linking global manufacturing supply components.
2018–2019: MuleSoft (A Salesforce Company) – Augmented directly into MuleSoft’s London headquarters as a Delivery Manager, spearheading API-led connectivity deployments via the Anypoint Platform.
2019–2021: UK Government Agency (UK Gov) – Commanded a major Hybrid Cloud Migration initiative to refactor, re-host, and re-platform 130 legacy agency software applications directly to cloud servers.
2022: UK Utility Sector (Welsh Water / Scottish Water) – Dual-management lead executing a £0.5 million contract to migrate an aging, on-premise document management program (EQS) onto the Microsoft Azure cloud via Enablon.
2023–2026: Public Sector & Core Tooling (Current) – Managing high-value middleware and API integrations for entities like the Royal Mail Group (RMG), NATS, and regional government bodies. Concurrently authors a widely used portfolio of commercial project management templates (RAID logs, RACI matrixes, and MS Project MPP layouts) published via PROject Templates.
Wincor Nixdorf was a premier global provider of IT solutions, hardware, software, and services tailored for retail banks and the retail industry.
Headquartered in Paderborn, Germany, the company historically commanded roughly 35% of the global automated teller machine (ATM) market and stood as a dominant force in electronic point-of-sale (EPOS) systems.
Its operations focused deeply on business process optimisation, automated cash handling, and retail self-checkout systems. In 2016, Wincor Nixdorf merged with its US rival Diebold, Inc., creating the modern consolidated market leader, Diebold Nixdorf.
Detailed Historical Timeline
The history of Wincor Nixdorf spans several distinct strategic eras, tracing its evolution from a post-war calculator workshop into a modern global fintech titan.
Era 1: The Founding & Decentralised Computing (1952–1989)
This era was defined by entrepreneur Heinz Nixdorf, who pioneered small-to-medium business computing and electronic banking terminals across Europe.
1952: Heinz Nixdorf establishes Labor für Impulstechnik in Paderborn, Germany. The small enterprise builds electronic calculators for businesses rebuilding in post-war Europe.
1964: The company shifts from acting as a third-party component supplier to marketing office calculators and billing systems under its own brand name. []
1968: Following corporate acquisitions, the company officially rebrands as Nixdorf Computer AG and develops some of the world’s earliest decentralized minicomputers.
1969: The firm enters the North American market by purchasing the electronics division of the US office equipment manufacturer Victor Comptometer.
1971: Secures its first landmark international banking contract, supplying 1,000 terminals to the Swedish banking industry.
1978: Global sales cross DEM 1 billion, and the workforce grows to over 10,000 employees globally.
1982: Expands its engineering breadth by forming a dedicated corporate telecommunications division.
1984: Launches its initial public offering (IPO), floating shares publicly on the Frankfurt Stock Exchange.
1986: Founder Heinz Nixdorf suddenly dies of a heart attack at a corporate event. The company struggles to pivot from hardware-locked minicomputers to emerging open personal computer architectures.
1989: Amid intensifying global hardware margins and strategic missed steps, corporate financial losses top DEM 1 billion.
Era 2: The Siemens Integration & Corporate Carve-Out (1990–1998)
During this stage, corporate giant Siemens rescued and absorbed the distressed business, later reorganizing its retail and banking assets into a specialized standalone vehicle.
1990: Siemens AG steps in to purchase the shares of Nixdorf Computer AG, officially merging it with its own Data Information Services division to create Siemens Nixdorf Informationssysteme (SNI) AG.
1992: SNI expands heavily across European IT markets, operating as a distinct, specialized computing arm under the Siemens umbrella.
1996: Becomes the largest IT company in Germany and the second largest across the European continent.
1998: Siemens restructures its computing strategy; it sells its personal computer division to Acer and spins off the highly profitable banking and retail segments into a new unit: Siemens Nixdorf Retail and Banking Systems GmbH.
Era 3: Private Equity Buyout & The Rise of Wincor Nixdorf (1999–2015)
This period marked the official birth of the independent “Wincor Nixdorf” brand, characterized by aggressive global expansion, software-driven solutions, and public market listing.
1999: Private equity firms Kohlberg Kravis Roberts (KKR) and Goldman Sachs Capital Partners complete a buyout of the Siemens unit. The company is formally renamed Wincor Nixdorf GmbH.
2000: Launches major end-to-end IT outsourcing and infrastructure managed services alongside its standard terminal hardware.
2004: On 19 May, Wincor Nixdorf successfully returns to the public markets, listing as Wincor Nixdorf AG on the Frankfurt Stock Exchange via a high-performing IPO.
2006: Longtime Chief Executive Officer Karl-Heinz Stiller resigns from the board, leaving a structurally sound company expanding deep into automated cash recycling and software.
2009–2014: Deploys multi-vendor banking software and automated checkout machines worldwide, expanding operations across roughly 100 countries.
2015: Reports global revenues of €1.8 billion, split roughly 65% in banking services and 35% in retail point-of-sale solutions. On 23 November, US rival Diebold announces a formal business combination agreement to acquire the company.
Era 4: The Diebold Nixdorf Consolidation (2016–Present)
This current era represents the unification of American and European ATM powerhouses to navigate shifting brick-and-mortar financial landscapes.
2016: Diebold Inc. officially completes its $1.8 billion voluntary public takeover of Wincor Nixdorf AG on 15 August. The consolidated global giant begins unified operations as Diebold Nixdorf on 16 August.
2017: The UK Competition and Markets Authority (CMA) formally clears the merger following a comprehensive antitrust review, requiring Diebold to divest its legacy UK customer ATM operation to avoid localized market monopoly.
2021: Capitalizing on self-checkout shifts accelerated by the pandemic, the combined entity launches its next-generation DN Series™ EASY self-service retail product line.
2023: Burdened by legacy debt structures, supply chain disruptions, and pandemic operational challenges, Diebold Nixdorf files for a prepackaged Chapter 11 bankruptcy protection in June. The restructuring swiftly sheds $2.1 billion in debt. By August, it successfully emerges from bankruptcy, resuming trading on the New York Stock Exchange (NYSE).
2024–2026: The restructured firm shifts its focus from low-margin hardware to high-margin managed services and cloud software, stabilizing its global operations with annual revenues reaching $3.75 billion.
The Software Partnership (TSP) was a highly specialized British software house based in Runcorn, Cheshire, that played a key role in early cutting-edge electronic banking software. The firm famously developed sp/ARCHITECT-BANK, an innovative enterprise banking system built explicitly for Tandem Computers (now HPE NonStop) fault-tolerant server systems. I was based there between 1990 and 1995.
The Software Partnership Logo
Below is a detailed overview of the company’s operational history, alongside the corresponding hardware/software architectural eras of the HPE NonStop platform it relied upon.
Detailed Overview
Core Focus: The Software Partnership specialized in online transaction processing (OLTP) and electronic automated banking software. Long before the internet became mainstream, TSP engineered early desktop access environments for corporate bookkeeping and inter-account bank transfers.
Key Product: Its flagship software suite, sp/ARCHITECT, ran on Tandem’s highly unique, redundant architecture. The software handled complex high-volume retail transactions, ATM networking, and ledger balances.
Major Clients: High-profile financial institutions deployed TSP’s systems, including TSB (Trustee Savings Bank), Bank of Scotland, Rabobank, and Denmark’s Girofon.
Legacy: TSP initiated a massive lineage of financial tech operations in the Runcorn/Warrington area. After subsequent buyouts and transitions, its corporate DNA integrated into modern banking giants, eventually operating under Fidelity National Information Services (FIS).
Detailed Timeline by Era and Year
The history of TSP mirrors the evolution of the underlying fault-tolerant architecture originally built by Tandem, later managed by Compaq, HP, and currently Hewlett Packard Enterprise (HPE).
Era 1: The Tandem Founding & TSP Inception (Mid-1970s – 1989)
This era is marked by Tandem’s creation of the fault-tolerant server market, which birthed the niche that TSP filled.
1974–1976: Tandem Computers is founded and ships its first 16-bit NonStop I (T/16) system, utilizing complete component redundancy to guarantee close to zero downtime for the financial industry.
1981: Tandem introduces the NonStop II, transitioning to battery-backed DRAM memory and enabling early 32-bit addressing.
Mid-1980s: The Software Partnership (TSP) is co-founded by Nigel Walsh. It establishes offices first in Timperley (Wingate Drive), then moves to Crowngate (Norton House) in Runcorn. The team begins developing online banking architectures explicitly for Tandem OS (Guardian) and early UNIX nodes.
1989: Tandem launches the NonStop Cyclone, a high-end mainframe system featuring superscalar CPUs and fiber-optic interconnects.
Era 2: The MIPS RISC Transition & Corporate Buyouts (1990 – 1999)
TSP reaches peak software deployment exactly as Tandem shifts its internal processor technology.
1990: TSP establishes itself as a major regional employment hub for software engineers following a massive boom in terminal banking technology. Software programmers deploy sp/ARCHITECT-BANK code for massive retail banks internationally.
1991: Tandem shifts its structural hardware away from proprietary chips, introducing its first MIPS RISC-based NonStop systems.
1992: TSP expands its Runcorn footprint, moving to custom facilities at Wingate House on Northway, Runcorn.
1994: TSP is acquired by American firm Deluxe Electronic Payment Systems (a division of Deluxe Corporation, one of the largest check printers and transaction processors in the US). The corporate name transitions to Deluxe Data.
1997: Due to shifts in the enterprise hardware landscape, Compaq Computer Corporation acquires Tandem Computers for $3 billion, taking over the NonStop lineage.
Era 3: The Itanium Migration & eFunds Realignment (2000 – 2013)
The architecture sheds its proprietary processors for industry standards, and TSP’s corporate legacy transforms.
2000: Deluxe Data’s electronic payment wing splits off and rebrands as EFD eFunds.
2001–2002: HP (Hewlett-Packard) merges with Compaq, absorbing the NonStop portfolio. Simultaneously, HP begins shifting NonStop servers from MIPS architectures to Intel Itanium processors.
2007: Following industry consolidation, the corporate remnants of the original TSP Runcorn operations are absorbed into Fidelity National Information Services (FIS) and relocated to Aegon House in Daresbury, Warrington.
Era 4: The Modern HPE NonStop X & Virtualization Era (2014 – Present)
The legacy of the high-availability software pioneered in Runcorn culminates in cloud and x86 integration.
2014: HP introduces NonStop X, completely migrating the underlying architecture to Intel x86-64 processors and implementing InfiniBand connectivity fabrics.
2015: Hewlett-Packard officially splits into two entities; the core mission-critical banking platform continues its five-decade lineage under Hewlett Packard Enterprise (HPE).
2020s–Present: HPE modernizes the software architecture to support Virtualized NonStop Software (vNS). Modern variants allow banking systems to run mission-critical apps seamlessly inside enterprise private clouds and scalable HPE GreenLake consumption models with 100% fault tolerance.
Deluxe Data International Operations, Wingate House, Northway, Runcorn, Cheshire
The Software Partnership, Norton House, Crowngate, Runcorn, Cheshire
⚙️ sp/ARCHITECT
sp/ARCHITECT (specifically sp/ARCHITECT-BANK) was a foundational electronic banking and transaction framework engineered in the 1990s by The Software Partnership (a UK-based fintech house later acquired by Deluxe Data). It primarily powered corporate banking portals and telephone-driven banking services.
The platform acted as highly reliable middleware, serving as a bridge between the customer and back-end banking mainframes. The breakdown of its architecture, infrastructure, and core functions includes:
⚙️ Architectural Breakdown
Hardware & OS: Built to run natively on fault-tolerant Tandem NonStop computers (now HPE NonStop). This “shared-nothing” architecture was designed for absolute transactional uptime and zero data loss.
Programming Languages: Built using legacy enterprise standards. Code was primarily written in COBOL85 and TAL (Transaction Application Language) native to the Tandem ecosystem.
Middleware Integration: Utilized Tandem-specific middleware like Pathway and Remote Server Call (RSC) to handle client-to-host communications.
💻 Core Capabilities & Modules
Electronic Delivery Framework: Served as a multi-channel framework, accommodating a wide variety of early access devices like desktop clients, UNIX workstations, and smart phones.
Transaction Handlers: Deployed custom scripts/handlers that enabled end-users to securely access real-time account data and perform early inter-account transfers without visiting a physical branch.
Testing Utilities: Included proprietary simulation tools like sp/TESTBED, acting as a PC-to-host test harness so developers could emulate user queries and transaction flows.
🏦 Industry Footprint
European Rollout: Heavily adopted by large European financial institutions, including TSB, Rabobank, Bank of Scotland, and Girofon.
BBM II Integration: Powered landmark corporate desktop banking solutions like Barclays Business Master II (BBM II), long before modern web browser banking existed.
Evolution: Following its acquisition, its design philosophies eventually evolved into Deluxe Data’s broader CONNEX suite of payment solutions.
A Capgemini Engagement Manager is a senior-level, client-facing role responsible for end-to-end delivery of complex business and technology transformation programs. They bridge strategy and execution, acting as a trusted advisor to clients while maintaining operational and financial control over projects.
Engagement Manager, from 2016
Key Responsibilities
End-to-End Delivery: Overseeing projects from start to finish, ensuring milestones, SLAs, and contractual obligations are met on time and within budget.
Stakeholder Management: Acting as the primary client point of contact while aligning cross-functional and globally distributed delivery teams.
Risk & Governance: Identifying potential roadblocks, proactively managing risks, and ensuring strict adherence to project governance standards.
Business Growth: Spotting opportunities for additional business and supporting bid activities for account expansion.
Mark Whitfield, Engagement Management EM Level 2 Exam Passed 2017
Ideal Candidate Profile
Experience: Typically requires a degree in Business, Engineering, or IT, combined with at least 5+ years of experience in project management or service delivery within a B2B environment.
Skills: Strong commercial acumen, proficiency in formal methodologies (e.g., Agile, ITIL), and the ability to lead diverse, multinational teams.
C&CA UK’s Communications & Engagement Award Winner 2022, Cloud & Custom Applications, Mark Whitfield
PROject Templates 
