Download Templates for Project Management | FREE Upgrades & Additions
Author: Mark Whitfield
Welcome to my site!
After graduating in Computing in 1990, I accepted a position as a programmer at a Runcorn based software house specialising in electronic banking software, namely sp/ARCHITECT-BANK on Tandem Computers (now HPE NonStop). This was before the internet became more prevalent and so the notion of enabling desktop access to company accounts for inter-account transfers and book keeping was still quite a cutting edge idea (and smartphones only ever hinted at in Space 1999). The company was called The Software Partnership (which was taken over by Deluxe Data in 1994).
I spent 5 years in Runcorn developing code for SP/ARCHITECT for various banks like TSB, Bank of Scotland, Rabobank and Girofon (Denmark) to name but a few. I then moved onto a software house in Salford Quays for further bank facing projects. After a further 23 years in the IT industry and now a Senior IT Project Manager (both Agile and Waterfall delivery), I thought I would echo out my Career Profile in this corner of the internet for quick and easy access.
Agile is a project management philosophy, while Scrum is the structured, real-world framework used to put that philosophy into action. Think of Agile as a commitment to healthy living, and Scrum as the specific daily workout routine you follow to stay fit. Instead of planning a massive project from start to finish upfront, Scrum breaks the work down into small, manageable pieces delivered in short cycles.
The easiest way to understand Scrum is through the 3-5-3 Rule: 3 Roles, 5 Events, and 3 Artifacts.
👥 The 3 Roles
A standard Scrum team is small, cross-functional, and self-managing, meaning they have all the skills needed to complete the work without relying on outsiders.
Product Owner: The visionary. They understand customer needs, decide what needs to be built, and maintain the master to-do list.
Scrum Master: The coach. They do not manage the team; instead, they protect them from distractions, facilitate meetings, and clear roadblocks.
Developers: The builders. This includes the engineers, designers, or writers who do the hands-on work and decide how to build it.
📦 The 3 Artifacts
Artifacts are simply the tangible items or lists used to maintain transparency across the project.
Product Backlog: The ultimate master list of features, fixes, and requirements needed for the product, prioritized by value.
Sprint Backlog: The specific subset of items selected from the master list that the team commits to finishing during the current cycle.
Increment: The final, working piece of the product delivered at the end of a cycle that meets the team’s “Definition of Done”.
📅 The 5 Events (Ceremonies)
Scrum operates in time-boxed blocks called Sprints, which usually last 1 to 4 weeks. Each Sprint includes four distinct meetings:
The Sprint: The time-box itself where the actual building happens.
Sprint Planning: A meeting at the start of a Sprint where the team decides what they can realistically achieve and creates a plan.
Daily Scrum (Stand-up): A quick, 15-minute daily meeting where developers sync on progress, plan the next 24 hours, and flag blockers.
Sprint Review: A showcase held at the end of the Sprint to demo the working increment to stakeholders and gather feedback.
Sprint Retrospective: An internal team meeting to review what went well, what went wrong, and how to improve the process for the next Sprint.
🏗️ Why Does Scrum Work?
Scrum relies entirely on Empiricism, meaning making decisions based on real-world evidence rather than guesswork. It stands firmly on three pillars:
Transparency: Everyone involved sees exactly what is happening.
Inspection: The team frequently stops to check the quality of the product and progress.
Adaptation: If something goes off-course, the team shifts direction immediately rather than blindly following an outdated plan.
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.
Columbo is one of television’s most celebrated crime dramas, spanning 35 years, 69 episodes, and two major television networks. Starring Peter Falk in his four-time Emmy-winning role, the show completely upended standard detective tropes with its signature “inverted detective story” structure.
Peter Falk, Columbo
The following guide breaks down the core characteristics of the series, followed by a comprehensive, year-by-year chronological timeline of its production and broadcasting history.
Detailed Description of the Series
The Inverted “Whodunit” (The Howcatchem)
Unlike standard mystery shows where the audience tries to guess the killer, Columbo is an inverted detective story. Every episode begins by showing the audience exactly who the murderer is, their motive, and the elaborate steps they take to craft an “airtight” alibi. The true tension and entertainment lie in the psychological cat-and-mouse game between the killer and Lieutenant Columbo, watching him slowly pick apart their flawless crime.
The Character of Lieutenant Columbo
The Appearance: Columbo is famously dishevelled. He wears a rumpled, beige raincoat over a wrinkled suit, drives a battered 1959 Peugeot 403 convertible, and frequently chomps on a half-burned cigar.
The Tactics: He acts incredibly humble, forgetful, and easily distracted. This is a deliberate ploy to make the high-society killers underestimate him, causing them to let their guard down and talk too much.
The Catchphrase: Just as a suspect believes Columbo is leaving and they have gotten away with murder, he stops, turns around, scratches his head, and delivers his iconic phrase: “Just one more thing…”
Personal Quirks: He works for the Los Angeles Police Department (LAPD), never carries a gun, loves chili with crackers, owns an incredibly lazy basset hound simply named “Dog”, and constantly references his unseen wife, Mrs. Columbo.
Detailed Production & Broadcast Timeline
The history of Columbo spans across two distinct network eras: the NBC Era (the original 1970s run) and the ABC Era (the late 1980s revival through to the final specials).
Pre-Falk Origins (1960 – 1962)
1960: Writers Richard Levinson and William Link introduce the character of “Lieutenant Columbo” in an episode of the anthology series The Chevy Mystery Show titled “Enough Rope”, played by actor Bert Freed.
1962: The writers adapt the story into a stage play named Prescription: Murder, where Columbo is portrayed by Oscar-winner Thomas Mitchell.
The NBC Series Era (1971 – 1978)
During this run, Columbo does not air weekly. Instead, it serves as a rotating program on The NBC Mystery Movie alongside shows like McCloud and McMillan & Wife.
1971:Season 1 begins. The official premiere episode, “Murder by the Book”, is directed by a young, pre-fame Steven Spielberg.
1972:Season 1 concludes, and Season 2 premieres in September. This season includes classics like “Etude in Black”.
1973:Season 2 ends, and Season 3 launches, introducing “Any Old Port in a Storm”, which features Donald Pleasence and is widely considered one of the best episodes of the series.
1974:Season 3 wraps up, and Season 4 premieres. It features Johnny Cash in “Swan Song” and Dick Van Dyke in “Negative Reaction”.
1975:Season 4 concludes, and Season 5 debuts in the autumn, featuring the episode “Forgotten Lady”.
1976:Season 5 ends. Season 6 premieres in October with a shortened, three-episode order as Peter Falk begins negotiating fiercely over his contract and salary.
1977:Season 6 wraps up. Season 7 launches in November, highlighting the fan-favourite episode “Try and Catch Me” starring Ruth Gordon.
1978: The final NBC episode, “The Conspirators”, airs in May. Burnt out by the rigorous schedule and wanting to pursue feature films, Peter Falk walks away from the character, ending the original run.
The Hiatus & Spin-Off (1979 – 1988)
1979: NBC attempts to keep the brand alive without Falk by launching a spin-off series, Mrs. Columbo, starring Kate Mulgrew. It is heavily rejected by fans and swiftly cancelled.
1980–1988:Columbo remains entirely dark for nearly a decade.
The ABC Revival Era (1989 – 2003)
ABC successfully strikes a deal with Peter Falk to bring the detective back for a series of premium, two-hour television movies.
1989: After an 11-year absence, Columbo returns to television with Season 8. Later that year, Season 9 launches.
1990:Season 9 concludes in May. ABC abandons the rigid, seasonal formatting, shifting the series into occasional, high-budget “TV Specials”. Season 10 officially begins with “Columbo Goes to College” in December.
1991: Three major movie specials are broadcast: “Caution: Murder Can Be Hazardous to Your Health”, “Columbo and the Murder of a Rock Star”, and “Death Hits the Jackpot”.
1992: Two movie specials air: “No Time to Die” (a rare episode where Columbo solves a kidnapping rather than a murder) and “A Bird in the Hand…”.
1993: Only one special is produced and broadcast this year: “It’s All in the Game”, written by Peter Falk himself.
1994: Two movie specials air: “Butterfly in Shades of Grey” (featuring William Shatner’s second appearance as a Columbo villain) and “Undercover”.
1995: A single movie special is broadcast: “Strange Bedfellows”, co-starring George Wendt.
1997: Following a brief hiatus, “A Trace of Murder” airs to celebrate the 30th anniversary of the franchise.
1998: The movie special “Ashes to Ashes” is broadcast, featuring Patrick McGoohan, who also directed several episodes of the series.
2001: “Murder With Too Many Notes” airs after a multi-year delay in production.
2003: The 69th and final episode, “Columbo Likes the Nightlife”, airs on 30 January. This concludes the historic run of the franchise, as Peter Falk formally retires from playing the character before his passing in 2011.
The HPE NonStop Technology & Business Conference (Nonstop TBC 2026)—hosted by Connect Worldwide—will take place from September 14 to September 17, 2026, at The Rosen Plaza in Orlando, Florida.
This signature annual event brings together enterprise IT leaders, software engineers, and solution architects to explore innovations shaping mission-critical environments.
Core Event Schedule
The four-day conference partitions its educational and collaborative tracks as follows:
September 14: Dedicated exclusively to HPE Education Day, featuring expanded deep-dive technical pre-conference courses.
September 15–17: The primary conference technical program and breakout sessions.
Key Focus Areas & Tracks
The 2026 event focuses heavily on bridging mission-critical legacy stability with modern software frameworks:
AI-Driven Transformation: Adapting continuous availability to the demands of modern artificial intelligence and machine learning workloads.
Digital Resilience & Security: Mitigating modern risks, modernising backup systems, and maintaining absolute runtime security.
FinTech & Payments: Real-world operational strategies from global peers managing transaction-heavy workloads.
Expanded Business Track: New for 2026, this track aligns executive business drivers with technical architectures for practical IT roadmap building.
Logistics and Pricing
Venue: The Rosen Plaza Hotel, situated at 9700 International Drive, Orlando, Florida.
Pricing: A newly reduced Early Bird Registration ticket is available for $895.
Accommodations: Registered attendees gain access to a dedicated Connect block rate of $181 per night (including tax).
Sponsorships: Major industry partners, such as comforte, sponsor the event, granting enterprise buyers direct visibility into third-party NonStop infrastructure add-ons.
Centiun is a UK-based Microsoft AI Cloud Partner and IT consultancy specializing in digital transformation, cloud migration, and AI integration for public and private sector organizations.
Centiun is a UK-based Microsoft AI Cloud Partner and IT consultancy
They help businesses modernize operations, leverage low/no-code platforms, and transition legacy infrastructure to secure cloud environments.
Core Services
Cloud & App Modernization: Migrating on-premise, legacy applications to secure cloud environments to reduce costs and enhance agility.
Microsoft AI & Business Applications: Implementing solutions across the Microsoft stack, including Copilot, Power Platform, and Dynamics 365, to improve process efficiency and data-driven decision-making.
Managed Services & Governance: Providing SLA-compliant technical governance, threat monitoring, and support to ensure business continuity.
Training & Enablement: Upskilling staff to confidently use Microsoft tools and low-code solutions.
Target Industries
Centiun tailors their technology solutions to several specialized sectors, offering domain expertise in:
Healthcare and Non-profits
Public Bodies and Central Government
Financial Services and Manufacturing
Energy and Utilities
Why They Stand Out
Microsoft Expertise: Their seasoned experts hold numerous Microsoft certifications and boast a combined 20+ years of experience in Microsoft Business Applications.
Tailored Approach: They focus on personal service rather than one-size-fits-all solutions, aiming to help clients scale and modernize while minimizing operational disruption.
Security & Trust: The firm operates with strict data security measures, holding accreditations like Cyber Essentials and registration with the Information Commissioner’s Office (ICO).
Explore their complete list of solutions and case studies directly on the Centiun Official Website.
Agile project management is an iterative, adaptive approach that breaks projects down into small, manageable cycles called sprints or iterations. Instead of planning the entire project upfront, teams continuously deliver functional increments, gather immediate feedback, and adapt to changing requirements. It prioritizes team collaboration, customer involvement, and rapid value delivery over rigid documentation and sequential phases.
Comprehensive Timeline Breakdown by Era and Year
Era 1: The Foundational Seeds (1950s – 1980s)
Before “Agile” existed as a formal term, engineers and researchers laid the groundwork through lean manufacturing and early iterative computing.
1957: IBM begins utilizing incremental development concepts under Gerald M. Weinberg.
1958: Software for Project Mercury (NASA’s first human spaceflight program) is developed using rapid half-day iterations.
1970: Dr Winston Royce publishes a paper describing the Waterfall methodology. Paradoxically, he presents it as high-risk, yet it becomes the dominant, rigid corporate framework for decades.
1980: Toyota refines “Just-In-Time” logistics and visual management system concepts, which later directly inspire Kanban and Lean software practices.
1986: Authors Hirotaka Takeuchi and Ikujiro Nonaka publish “The New New Product Development Game” in the Harvard Business Review. They introduce a holistic, “rugby-style” team approach, coining the term “Scrum”.
1988: Dr Barry Boehm introduces the Spiral Model, formalizing risk-driven, iterative lifecycle planning.
Era 2: The “Lightweight” Revolt (1990s)
Driven by frustration over the high failure rates and slow delivery of Waterfall, software pioneers independently build faster, more flexible frameworks.
1991: James Martin formalizes Rapid Application Development (RAD), highlighting timeboxing, prototyping, and active customer involvement.
1993: Jeff Sutherland, John Scumniotales, and Jeff McKenna deploy the very first operational Scrum process at Easel Corporation.
1994: The Dynamic Systems Development Method (DSDM) is launched in the UK, providing one of the earliest structured frameworks for iterative project delivery.
1995: Ken Schwaber and Jeff Sutherland co-present the formal Scrum Framework to the public at the OOPSLA conference.
1996: Kent Beck introduces Extreme Programming (XP), introducing core engineering mechanics like pair programming and test-driven development (TDD).
1997: Jeff De Luca and Peter Coad design Feature-Driven Development (FDD) to focus strictly on client-valued functional results.
Era 3: The Manifesto Moment (2000 – 2001)
The pivotal pivot point where separate iterative movements unite into a single, cohesive global movement.
2000: Pre-meeting alignment occurs. Martin Fowler publishes his definitive article on Continuous Integration (CI), and Extreme Programming teams begin adopting Scrum’s three-question daily standup format.
February 2001: The Agile Manifesto is Born. Seventeen software development pioneers meet at a ski resort in Snowbird, Utah. They discover common ground, author the Manifesto for Agile Software Development, and establish the 4 Core Values and 12 Principles.
Late 2001: The Agile Alliance non-profit is established to safeguard, evolve, and distribute Agile education globally.
Era 4: Mainstream Adoption & Scaling (2002 – 2019)
Agile shifts from a rebellious IT trend into a standard corporate expectation, requiring frameworks that can scale across massive enterprises.
2002: Ken Schwaber co-founds the Scrum Alliance to offer standardized certifications (like Certified ScrumMaster), dramatically accelerating global adoption.
2003: Mary and Tom Poppendieck publish Lean Software Development, cleanly mapping Toyota’s manufacturing efficiencies directly onto digital projects.
2009: The Software Craftsmanship Manifesto is created to ensure technical excellence and code quality are not forgotten during rapid business sprints.
2011: Dean Leffingwell releases the Scaled Agile Framework (SAFe), allowing massive corporate enterprises to align hundreds of agile teams across entire portfolios.
2015: Global project management authorities officially pivot; AXELOS releases PRINCE2 Agile, and the Project Management Institute (PMI) introduces Agile certifications into its core curriculum.
Era 5: Modern Continuous Agility (2020s – Present)
Agile transcends IT entirely, cementing its place as an overarching organizational strategy for business survival in an uncertain world.
2020: The Scrum Guide receives its most significant structural update, streamlining language, eliminating prescriptive micro-management, and focusing intensely on a single, unified team working toward a singular “Product Goal”.
2021–2023: Business Agility explodes. Non-technical departments—including HR, Marketing, Legal, and Finance—broadly restructure their workflows into iterative agile backlogs to manage volatile hybrid work environments.
2024–Present: AI-Driven Agility becomes standard practice. Project management tools use generative AI to automatically draft user stories, estimate team velocity, and dynamically rewrite project sprint backlogs based on real-time market shifts.
XPNET (often distributed as part of the NET24 suite) is a proprietary, mission-critical Message-Oriented Middleware (MOM) and network management infrastructure developed by ACI Worldwide.
It is designed to run primarily on fault-tolerant HPE NonStop (Tandem) systems. XPNET acts as the foundational layer for ACI’s globally dominant payment engines, BASE24 and BASE24-eps.
It provides the multi-node network architecture, data routing, inter-process communication, and transaction logging required to safely process hundreds of millions of ATM, Point of Sale (POS), and mobile payments daily.
Key Architectural Technical Description
Core Function: XPNET acts as the vital gateway between terminal devices (ATMs, POS terminals), regional interchanges (Visa, MasterCard), and a bank’s back-end host system.
Network Environment File (NEF): All physical and logical configurations of an XPNET deployment—including nodes, links, processes, stations, and communications lines—are centrally defined inside the NEF.
Fault Isolation: XPNET monitors processes using a distributed architecture. If an interface process or line drops, XPNET safely queues or reroutes transactions to achieve “five-nines” (99.999%) financial system uptime.
Audit and Tracing: XPNET intercepts all systemic message traffic, managing the core Transaction Log File (TLF) and generating event messaging for fraud monitoring and performance profiling.
Detailed XPNET Historical Timeline Breakdown
The evolution of XPNET is deeply intertwined with ACI’s flagship software, scaling alongside the transformation of global electronic funds transfers (EFT).
1982 – 1989: The Genesis Era
1982: ACI launches BASE24 to manage early ATM networks. To handle low-level Tandem interprocess communication, ACI designs precursor communication layers.
1986: ACI scales internationally to 131 major clients across 14 countries, increasing the demand for a standard, highly secure, policy-driven message-switching architecture to accommodate disparate global telecommunication protocols.
1990 – 1999: NET24 and XPNET Standardisation
1993: ACI is reorganised under Transaction Systems Architects (TSA). The communications infrastructure is formalised as NET24-XPNET, decoupled cleanly from application logic.
1995: ACI goes public on NASDAQ. XPNET becomes the mandatory structural platform for any financial institution deploying BASE24 “Classic”.
1998: ACI acquires IntraNet. XPNET is updated to handle wholesale wire transfers and high-value Automated Clearing House (ACH) data alongside retail consumer swipes.
2000 – 2009: The Next-Gen Transition (BASE24-eps)
2002: ACI launches BASE24-eps (Enterprise Payments System). XPNET is radically re-engineered to support both classic structural architecture and next-generation message formats, utilizing its Common Transport Subsystem (CTS) to act as a Tandem Pathway client/server.
2008: ACI optimises BASE24-eps for IBM System z architectures, but updates the NonStop-native XPNET to Version 08.2 to handle expansive regional payment networks across Europe and Asia.
2010 – 2019: Litigation and Global Footprint Consolidation
2011 – 2014: Third-party performance suites, such as IR Prognosis XPNET Manager,Insider Technologies XPERT24 and Reflex ONE24 explode in popularity, allowing banks to map live visual diagnostics of their XPNET lines and queues.
2017: ACI and MasterCard reach an agreement to resolve a massive legal dispute. As part of the settlement, MasterCard purchases a perpetual components license for NET24-XPNET middleware to legally fuel its core debit-switching network infrastructure.
2020 – 2026: Legacy Modernisation & The API Era
2021: With financial institutions pivoting toward digital microservices, ACI introduces hybrid compatibility layers. Companies like NuWave introduce direct API bindings to XPNET, allowing legacy HP NonStop payment architectures to map to modern REST web services without rewriting base COBOL/C code.
2025 – 2026: ACI celebrates 50 years of enterprise infrastructure engineering. While cloud-native solutions like ACI Connetic roll out for real-time rails, NET24-XPNET Version 4.x remains a heavily maintained, actively running baseline layer across tier-1 legacy banking systems worldwide.
XPERT24 (XPNET Performance Monitoring and Tracking) is a specialised financial middleware software product developed by Insider Technologies Limited. It provides real-time transaction tracking and operational counter monitoring for the BASE24™ transaction processing infrastructure.
Product Description
XPERT24 functions as a critical diagnostics layer for companies running BASE24 bank card payment systems. Built to sit on HP NonStop systems, the software uses PATHWAY servers to automatically detect, capture, and analyse data points from the underlying network. Its core features include:
XPNET Counter Monitoring: Tracks infrastructure health via rate, state, and data queue counters.
Interchange Performance: Monitors live transaction metrics, including approval and denial rates for ATM and POS transactions.
Throughput Optimization: Provides clear system visibility to avoid high-volume traffic jams or transaction delays.
Detailed Timeline Breakdown
The lifecycle of the XPERT24 software package moved from initial technical specification into corporate ecosystem expansions:
2001 — Initial System Baseline & Prep
Training and Scoping:Insider Technologies Limited launched internal Sales & Marketing campaigns to map mid-market banking software demands.
System Language Adaptation: Engineering teams refined core HP NonStop transaction tracking metrics.
2006 — Structural Architecture Layout
Design Initiatives: Product groups commenced documentation guidelines to build customer-facing technical literature.
Database Modeling: Initial designs mapped how transaction records could safely pass without lagging the live bank engine.
2007 — Server Logic Creation
Server Infrastructure Setup: Developers initiated building structural frameworks inside development kits.
Pathway Server Logic: Logic was written to make sure the software query scripts safely gathered data without interrupting processing.
2008 — Production Release & Launch Era
Official Software Launch: Insider Technologies launched the operational XPERT24 system to production status.
Hypervisor UI Integration: The company produced dedicated BASE24-eps™ and XPNET layer Hypervisor graphical displays.
Industry Showcase: Technical user interfaces were presented directly to the Electronic Banking User Group (EBUG) and the Satellite Transaction User Group (SATUG).
Web Monitoring Foundations: Teams rolled out technical requirements to present live transaction counters into standard web browsers.
2011 — Project Management & Standardization
Agile Shift: Development pipelines migrated entirely onto the Scrum framework.
Process Alignment: The product management structure was retrofitted to follow strict PRINCE2 guidelines to help service major government and banking institutions.
SAFe (Scaled Agile Framework) events are structured, time-boxed ceremonies designed to drive synchronization, alignment, and continuous improvement across different levels of an enterprise.
These events are primarily categorized into Team-level events (which mirror standard Scrum practices) and Agile Release Train (ART) level events (which orchestrate multiple teams working toward a shared goal).
The core events within Essential SAFe are broken down below by organizational layer.
👥 Agile Team-Level Events
These recurrent ceremonies occur inside a short timebox called an Iteration (typically lasting 2 weeks) and focus on local execution.
Iteration Planning: Teams refine the iteration plan, select backlog stories, and commit to a set of Iteration Goals.
Team Sync (Daily Stand-up): A brief, daily 15-minute meeting where team members align on progress, discuss daily goals, and highlight impediments.
Iteration Review: A cadence-based showcase at the end of the iteration where teams demo working software to gather immediate feedback.
Iteration Retrospective: Held at the end of each iteration to reflect on the process, team dynamics, and behaviors to drive relentless improvement.
Backlog Refinement: A weekly meeting where the Product Owner and team flesh out, estimate, and prep user stories for upcoming iterations.
🚊 Agile Release Train (ART) Level Events
These higher-level events drive the Planning Interval (PI), an 8 to 12-week timebox where an entire “train” of 5–12 teams delivers cross-functional value.
PI Planning: The multi-day flagship event of SAFe where all teams, stakeholders, and leaders align on a shared business vision, map dependencies, and commit to PI objectives.
System Demo: A regular event occurring every iteration where the integrated functionality built by the entire ART is demonstrated to stakeholders for feedback.
Coach Sync (formerly Scrum of Scrums): Facilitated by the Release Train Engineer (RTE), Scrum Masters meet to resolve cross-team dependencies, risks, and progress hurdles.
PO Sync: Product Owners and Product Management meet to track milestone progress, manage scope adjustments, and ensure the train remains aligned with business goals.
ART Sync: A combined session of Coach Sync and PO Sync used to streamline communication regarding execution and deployment.
Inspect & Adapt (I&A): A major event held at the end of the PI consisting of a system demo, quantitative measurements, and a problem-solving workshop to implement systemic backlog improvements.
Summary of Differences
For a quick comparison, you can look at how responsibilities scale across the framework:
SAFe (Scaled Agile Framework) events are structured, time-boxed ceremonies designed to drive synchronization, alignment, and continuous improvement across different levels of an enterprise
Sentra is a premier tracking and service management software platform developed by Insider Technologies Limited. Designed specifically for high-volume, mission-critical operations, Sentra is deployed across major financial, government, and defense institutions. It specializes in real-time tracking, information mediation, and multi-platform service level agreement (SLA) monitoring.
Insider Technologies in 2003 (San Jose), Business, Process and Systems Management for the Financial and Messaging Markets
The system operates across Windows, HP NonStop, Linux, and Unix environments to guarantee maximum uptime for transaction processing and data transmission.
Product Description & Capabilities
Sentra acts as a powerful tracking diagnostics framework. It evaluates the flow of files, payments, and system events to prevent costly service outages.
Real-Time Transaction Extraction: Utilizes extraction agents to pull live transaction data—such as ATM and Point-of-Sale (POS) logs—from core banking applications.
High-Speed Middleware Ingestion: Relays transaction lifecycle files (TLF) directly to a Windows server and Microsoft SQL database. This uses the company’s proprietary, high-speed TCP/IP sockets protocol known as FastPipe.
Rigorous SLA Enforcement: Provides end-to-end monitoring metrics optimized to help financial firms achieve extremely demanding targets, including 99.999% system availability.
Detailed Timeline Breakdown by Year
Because Insider Technologies is a private, specialized enterprise software house, its continuous internal product updates are primarily mapped through corporate evolution and key platform milestones:
1989 — Corporate Foundation
Insider Technologies Limited is incorporated in Manchester, UK. It targets 24×7 mission-critical systems like Tandem Computers (which later evolved into HP NonStop computing architecture).
1990s to Early 2000s — The Monitoring Evolution
The company relies heavily on its early flagship monitoring software suites, Reflex and MultiBatch.
Recognizing a shift toward heterogeneous environments, engineering teams begin conceptualizing Sentra to bridge real-time tracking between Windows and legacy systems.
2004 — Core Sentra Framework Launch
Official design, infrastructure layout, and core coding begin for the specialized Sentra platform architecture.
Sentra is formalized to extend tracking metrics outside of traditional mainframe environments into multi-platform Linux, Unix, and Windows installations.
2006 — Banking Application Integration
Development accelerates on custom add-ons to integrate Sentra directly with core banking infrastructure.
Teams design specialized mechanisms to track high-volume transactions routed via ACI Worldwide’s popular BASE24™ transaction-processing software.
2008 to 2011 — The RTLX Reactor Expansion
Insider Technologies releases RTLX Reactor, a major add-on module built entirely on top of the Sentra framework.
This expands Sentra’s market footprint by offering retail banks direct, real-time diagnostic visibility into live ATM and POS cash terminal traffic.
2013 — Framework Optimization & Digital Web Presence
A multi-year architectural overhaul wraps up, introducing enhanced information mediation and updated corporate digital resources mapping the platform’s core tracking methodologies.
Celebrating 30 years in operation, Insider Technologies rolls out modernised visual dashboards and broader diagnostic tracking capabilities across the Sentra portfolio. This addresses the escalating scale of electronic payments.
2024 to 2026 — PartnerOne Era & Cyber-Resilience
Insider Technologies transitions into operating as part of the global PartnerOne group.
Sentra continues to serve as an indispensable middleware tracking and monitoring asset. It runs alongside updated proactive cybersecurity, XDR, and IT operations infrastructure tailored for the UK government, defense sector, and multinational banking institutions.
ActionView.400 is an enterprise tracking and diagnostics software solution developed by Insider Technologies Limited. It was purpose-built as a dedicated monitoring tool for the Open System Interconnection / Message Handling System (OSI/MHS) X.400 subsystem deployed on Tandem, Compaq, HP, and HPE NonStop server platforms.
The software acts as a critical infrastructure layer used heavily by banking institutions, telecommunications providers, and government/military defense sectors.
It ensures that high-volume, secure electronic mail infrastructure meets strict Service Level Agreements (SLAs) by allowing engineers to account for every message, calculate end-to-end processing times, and issue real-time tracking metrics.
Detailed Timeline Breakdown by Year
1989: Insider Technologies Limited is incorporated in Manchester, England, by a collective of IT industry veterans. The firm initially focuses on building service management and custom tracking middleware for the rapidly expanding Tandem NonStop server ecosystem.
1990s (Early to Mid): As X.400 protocols become the global standard for secure EDI (Electronic Data Interchange) and military messaging, Insider Technologies develops ActionView 400. The product is integrated directly into Tandem’s core software stack and begins shipping natively with Tandem NonStop platforms.
1997: Tandem Computers is acquired by Compaq. ActionView 400 is sustained through this transition to maintain critical operations for tier-one banks and national military infrastructures relying on NonStop systems.
2002: Compaq merges with Hewlett-Packard (HP). ActionView 400 is bundled under the HP NonStop software catalog (product designation T8443), managing and diagnosing log audits like the AUDLOG framework.
2000s (Mid to Late): Insider Technologies starts shifting forward-looking tracking requirements toward its newer central architecture platform, Sentra. While ActionView 400 continues handling legacy X.400 pipelines, Sentra begins acting as a unified web console to consolidate both X.400 and modern SMTP/MIME email flows across multi-vendor systems.
2015: HP splits its corporate structures. The NonStop computing line and the management of ActionView 400 shift over to Hewlett Packard Enterprise (HPE).
2018: In December 2018, HPE officially moves ActionView 400 to Obsolete status, marking the formal end of its product life cycle and standard vendor service life.
2019 – Present: Despite official obsolescence on the HPE hardware list, Insider Technologies continues to directly support and maintain the solution for deep-legacy military, defense, and governmental bodies. Because these sectors still mandate uncompromised, zero-loss X.400 message accounting, the software remains active, feeding tracking telemetry directly into Insider’s modern Middleware Monitoring and Sentra platform interfaces.
Sentra – unified web console to consolidate both X.400 and modern SMTP / MIME email flows across multi-vendor systems
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.
Completing the Stakeholder List using Process Analysis
Completing a stakeholder list using process analysis involves tracing the end-to-end lifecycle of a process to identify every individual, team, or organization that interacts with, influences, or is impacted by it. This ensures no hidden users, bottlenecks, or approvers are missed.
A four-step approach will ensure your list is thorough and actionable:
1. Map the Process Flow
Create a step-by-step flowchart of the current or future process. Break it down into key phases: Inputs, Activities, Outputs, and Outcomes. This visual map acts as a blueprint to spot every touchpoint where someone is involved.
2. Identify Stakeholders at Each Touchpoint
Go through each phase of your process map and ask the following dependency questions to pinpoint roles:
Input Stage: Who supplies the data, materials, or funding? (e.g., vendors, regulators, finance departments)
Activity Stage: Who performs the work or oversees it? (e.g., project teams, department managers, QA testers)
Output Stage: Who receives the final deliverable? (e.g., end-users, clients, customers)
Outcome Stage: Who is affected by the long-term results? (e.g., the community, executives, maintenance teams)
3. Classify and Prioritize
Once your comprehensive list is built, categorize stakeholders using the Power/Interest Matrix. This helps allocate your engagement efforts efficiently:
High Power, High Interest: Manage closely and collaborate heavily (e.g., Project Sponsors, Product Owners).
High Power, Low Interest: Keep satisfied but do not over-communicate (e.g., Regulators, Steering Committees).
Low Power, High Interest: Keep informed and consult regularly (e.g., End-users, Support Staff).
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.
HPE NonStop MultiBatch is an advanced workload automation and scheduling manager designed explicitly for mission-critical HPE NonStop environments. Originally created to support complex scheduling needs in banking and finance, it automates job flows and parallel processing across multiple CPUs.
Detailed Description
The original NonStop batch scheduler (NetBatch) was built for basic sequential job queues. As large enterprises required deeper integration with databases, real-time events, and complex parallel schedules, MultiBatch (developed originally by Insider Technologies, now part of ETI-NET) emerged.
Core Functions: It automates job submission, tracks job flow, handles conditional parameters, manages event timers, and triggers jobs “On Demand” based on real-time system events.
High Availability: Like the underlying HPE NonStop system, MultiBatch is engineered for fault tolerance, ensuring automated workflows do not fail due to hardware or software interruptions.
Enterprise Integration: It supports Open System Services (OSS) and standardizes auditing, security, and menu-based operations across distributed NonStop systems.
Breakdown by Year / Era
The evolution of MultiBatch parallels the architectural changes of the HPE NonStop platform.
1985–1990s: Tandem Era & Origin
1985: Conceived. MultiBatch was developed by Insider Technologies specifically to meet the complex batch schedule demands of large financial institutions that exceeded native NetBatch capabilities.
Early 1990s: The system was officially rolled out for Tandem processors to automate transaction data loads and daily reconciliation tasks for ATMs and financial ledgers.
1997–2014: Compaq & Early HP Era
1997: Following Compaq’s acquisition of Tandem, MultiBatch was adapted to support the NonStop Himalaya systems and server software, which expanded data and network scaling.
2000s: During the HP Itanium and MIPS Era, MultiBatch evolved to support more dynamic processing pools and expanded job limits, increasing fault tolerance under the HP-UX integrated environment.
2014–2020: Transition to NonStop X & Modernization
2014: As HPE shifted the platform to standard Intel x86-64 processors (NonStop X), MultiBatch was updated for L-series operating systems to run efficiently on high-speed InfiniBand fabrics.
2019: Insider Technologies made significant updates to MultiBatch to modernize the GUI and improve code stability for the new generation of NonStop users transitioning to X-series hardware.
2020–Present: MultiBatch 10 & 10.2
2023: MultiBatch 10 was released. It included a new Operations GUI Server, significantly increased configuration limits (e.g., supporting up to 2,500 jobs), enhanced conditional parameters, improved processing of Open System Services (OSS), and “On Demand” job capabilities.
2025: MultiBatch 10.2 was released by ETI-NET. This update focused heavily on digital resilience, providing deep alignment with the NIST Cybersecurity Framework to protect against operational and cyber threats.
Current Status: Fully integrated into modern systems supporting the HPE GreenLake consumption-based cloud model, MultiBatch 10.2 serves as the primary automation engine for large enterprises executing complex HTAP (Hybrid Transaction/Analytical Processing) workloads.