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.

eBUG (European BASE24 User Group) Conference Overview and Chronological  Timeline

The eBUG (European BASE24 User Group) Conference is the premier annual gathering for financial institutions, retail banking professionals, and technical architects utilizing ⁠ACI Worldwide’s foundational retail payment engine, BASE24 and BASE24-eps.

Operating alongside global HPE NonStop hardware environments, the conference traditionally functions as a collaborative technical focus group (TFG) and customer roundtable. It brings together industry experts to address mission-critical transaction switching, regulatory compliance mandates, payment security architectures, and core software migrations.

Detailed Era Breakdown & Timeline

Era 1: The Classic BASE24 & ITUG Tandem Era (1980s – Late 1990s)

Focus: Evolution of core ATM/POS switching on Tandem (HPE NonStop) platforms, localized compliance, and basic card processing networks.

  • 1982–1985: The birth of the early European user networks following the launch of BASE24 software by Applied Communications Inc. (now ACI Worldwide). Early meetings are heavily dependent on regional vendor user group support.
  • 1992: Initial formations of explicit regional sub-committees under the International Tandem User Group (ITUG). The European base of users establishes formal communication pipelines.
  • 1996: Increased focus on the early adoption of regional card mandates, standardising early transaction switching over X.25 networks, and prepping mainframe systems for high-availability roundups.
  • 1999: A definitive milestone focused on Y2K compliance readiness. Conferences during this era are heavily centered on stress-testing legacy BASE24 code blocks, ensuring clock dates rollover flawlessly across financial networks without disrupting global merchant processing.

Era 2: The EMV Mandate & “Classic-to-EPS” Transition Era (2000 – 2010)

Focus: Overhauling core code for Chip & PIN (EMV) regulations, migrating toward open system frameworks, and introducing the next-generation BASE24-eps payment platform.

  • 2003: The EMV Blueprint Era. The conference takes a primary steering role for European banks facing strict Eurocard, Mastercard, and Visa (EMV) liabilities. User sessions heavily focus on updating terminal messaging scripts.
  • 2005: Introduction of BASE24-eps to the wider user group community. Discussions shift away from the classic architecture toward modern open-systems deployments, leveraging UNIX, Linux, and IBM z/OS alongside traditional NonStop environments.
  • 2007 (Istanbul, Turkey): The group expands geographic footprints into the borders of Europe and Asia. Themes heavily stress global interoperability, cross-border transactional routing, and real-time fraud monitoring.
  • 2008 (Vienna, Austria): High-water mark for attendance during the mid-2000s. Presentations focus on deep-dive technical configurations of BASE24-eps Release 08.2, service-oriented architecture (SOA) wrappers, and high-availability testing matrices.
  • 2009 (Prague, Czech Republic): Real-time monitoring tools become a central talking point. Despite global financial pressures, the user community explicitly defends the strength of ⁠HPE NonStop infrastructure for running foundational retail networks.

Era 3: Security Hardening & The Independent Pivot Era (2011 – 2018)

Focus: Adapting payment loops to rigid PCI-DSS requirements, cloud capability tracking, and shifting the conference structure to independent consulting sponsorships.

  • 2011: Focus turns squarely onto PCI-DSS Compliance and tokenisation. Roundtables detail architectural techniques to secure transaction journals, encrypt key lines, and prevent man-in-the-middle exploits at the ATM level.
  • 2012 (London, UK): Held at the historic ⁠Trinity House near Tower Bridge, this event marks a structural pivot. Moving away from a pure ACI-hosted workspace, independent payment consultancies (such as PayX) drive user discussions. This Technical Focus Group explicitly evaluates the limits of legacy systems against “intelligent” multi-vendor ATM software.
  • 2015: Immediate focus addresses the challenges of Real-Time / Instant Payments mandates across the Eurozone. Systems engineers share optimization scripting paradigms to support sub-second processing SLA ceilings.
  • 2018: The rise of Open Banking / PSD2 Regulations. Technical breakout sessions outline how to safely open classic BASE24 architectures to third-party APIs through microservices wrappers and middleware adapters without breaking strict system uptime criteria.

Era 4: Modernisation & Cloud-Native Coexistence Era (2019 – Present)

Focus: ISO 20022 message standard migrations, cloud-native deployments, and containerization strategies.

  • 2020–2022: Transition to hybrid tracking methodologies due to travel constraints. The baseline focus targets data integration, remote system management, and virtualized system-hardening techniques.
  • 2023–2024: The ISO 20022 Mandate. Sessions are dominated by the industry-wide migration from legacy ISO 8583 message lines to the XML-based ISO 20022 financial standard. Systems architects present automated script parsers to translate real-time payment formats across legacy logic systems.
  • 2025–2026: Integration of ⁠Cloud-Native BASE24-eps architectures. Contemporary meetups explore containerized execution patterns, utilizing AI models within the authorization loop to spot edge-case fraud patterns in real-time, and evaluating long-term roadmaps for hardware-security modules (HSMs).

eBUG (European BASE24 User Group) Conference Overview and Chronological  Timeline

AI Artificial Intelligence and Project Management Approaches

Artificial intelligence is transforming project management by shifting software from passive data repositories into active, predictive engines that automate tedious administration and improve decision accuracy.

The breakdown below covers the primary AI approaches and the specific tools driving each function.

🧠 Core AI Approaches in Project Management

Rather than basic, rule-based automation (“if X happens, do Y”), true AI uses model-driven machine learning, natural language processing (NLP), and predictive analytics.

  • Predictive Analytics & Forecasting: Machine learning models evaluate past team velocity, budget trends, and historical timelines to forecast delays and cost overruns before they occur.
  • Natural Language Processing (NLP): Large Language Models (LLMs) digest unstructured data like unstructured chats, customer emails, and meeting transcripts to extract action items, drafting project updates automatically.
  • Resource Optimisation: Algorithms match team members’ skills, existing workloads, and availability with upcoming project requirements to distribute work sustainably and efficiently.
  • Proactive Risk & Scope Creep Detection: AI monitors real-time activity and flags deviations from the initial project charter, alerting teams to emerging bottlenecks.

🛠️ AI Project Management Tools Broken Down by Use Case

1. All-in-One Work Operating Systems (Work OS)

These comprehensive platforms integrate AI deeply into everyday task tracking, workflows, and communication.

  • Monday.com: Features an integrated AI Assistant that auto-generates task descriptions, brainstorms project ideas, and summarizes long activity threads across cross-functional workspaces.
  • ClickUp: Uses its unified “ClickUp Brain” engine to break down major project milestones into contextual subtasks, answer project-related queries instantly, and write status updates.
  • Asana: Leverages AI smart agents to recommend task assignments, identify workflow blockers early, and suggest ideal task prioritisation based on team capacity.
  • Wrike: Focuses heavily on predictive analytics and intelligent insights, allowing larger organisations to move past traditional tracking into data-driven risk monitoring.

2. Meeting & Communication Intelligence

These tools alleviate the administrative burden of manually taking notes, tracking ownership, and summarizing align-meetings.

  • Otter.ai: Transcribes team calls in real time and automatically creates bullet-point action items, keyword summaries, and structured meeting recaps.
  • Microsoft Copilot / Google Gemini: Seamlessly pulls historical data from your workspace ecosystem (emails, documents, calendars) to draft project charters or assemble stakeholder reports with minimal context.

🛠️ AI Project Management Tools Broken Down by Use Case

1. All-in-One Work Operating Systems (Work OS)

These comprehensive platforms integrate AI deeply into everyday task tracking, workflows, and communication.

  • Monday.com: Features an integrated AI Assistant that auto-generates task descriptions, brainstorms project ideas, and summarizes long activity threads across cross-functional workspaces.
  • ClickUp: Uses its unified “ClickUp Brain” engine to break down major project milestones into contextual subtasks, answer project-related queries instantly, and write status updates.
  • Asana: Leverages AI smart agents to recommend task assignments, identify workflow blockers early, and suggest ideal task prioritisation based on team capacity.
  • Wrike: Focuses heavily on predictive analytics and intelligent insights, allowing larger organisations to move past traditional tracking into data-driven risk monitoring.

2. Meeting & Communication Intelligence

These tools alleviate the administrative burden of manually taking notes, tracking ownership, and summarizing align-meetings.

  • Otter.ai: Transcribes team calls in real time and automatically creates bullet-point action items, keyword summaries, and structured meeting recaps.
  • Microsoft Copilot / Google Gemini: Seamlessly pulls historical data from your workspace ecosystem (emails, documents, calendars) to draft project charters or assemble stakeholder reports with minimal context.

3. Engineering & Agile Backlog Management

Built to address the rapid velocity changes and technical needs of software development teams.

  • Jira (Atlassian Rovo): Uses built-in AI agents to organize bloated backlogs, surface conflicting dependencies, and estimate how long features will take based on historical sprint velocities.

4. Document & Knowledge Management

Designed for centralizing organizational resources so teams don’t waste time hunting for internal data.

  • Notion AI: Acts as a central, conversational wiki workspace that synthesizes notes, translates documents, drafts release notes, and surfaces data buried in complex project databases.
  • NotebookLM: A powerful, localized research assistant that organizes complex internal project documentation, creates study guides for teams, and answers cross-document queries accurately.

⚖️ Traditional vs. AI-Powered Project Management

Traditional vs. AI-Powered Project Management
Traditional vs. AI-Powered Project Management

Agile Scrum Master Misconceptions versus Reality

Agile Scrum Master Misconceptions versus Reality
Agile Scrum Master Misconceptions versus Reality

Entex Space Invader handheld electronic game

The Entex Space Invader handheld electronic game is a classic VHF-style portable arcade unit released in 1980. It is highly sought after by collectors of vintage 1980s electronics. I used to have one in the early eighties, my first taste of computing technology and gaming.

Design & Hardware

Entex Space Invader handheld electronic game
Entex Space Invader handheld electronic game
  • Form Factor: Large wedge-shaped black plastic tabletop/handheld console designed by Entex Tokyo.
  • Display Type: Vibrant, bright-green Vacuum Fluorescent Display (VFD) that mimics retro arcade visuals.
  • Power Source: Requires 6 AA batteries or an external AC mains power adapter.
  • Controls: Physical mechanical buttons, including left and right directional keys and a dedicated fire button.
Entex Space Invader handheld electronic game, close up
Entex Space Invader handheld electronic game, close up

Gameplay Mechanics

  • Objective: Move your laser cannon horizontally across the bottom of the screen to shoot down descending waves of alien invaders.
  • Layout: Displays four distinct lanes of action with columns of moving digital alien targets.
  • Scoring System: Tracks and displays electronic numeric scoring up to a maximum of 1,000 points.
  • Audio: Features simple built-in, synthesized electronic space sound effects for firing lasers and alien tracking.

Known Product Variants

  • 1980 Black Model: The original release featuring a dark case, designed and programmed natively in Japan by Entex Tokyo.
  • 1981 Grey Model: A re-programmed version developed by Rick Dyer & AMS featuring slightly adjusted gameplay. The distinct grey casing was actually the result of a factory paperwork typo that swapped two Pantone color codes.
Entex Space Invader handheld electronic game, back of box
Entex Space Invader handheld electronic game, back of box

Agile Scrum Metrics, Inspect, Adapt, Improve

1. Agile Scrum Metrics, Inspect, Adapt, Improve
Scrum Metrics summarised
2. Agile Scrum Metrics, Inspect, Adapt, Improve
Scrum Metrics Overview

Free Upgrade MS Project Management Templates for Download

The ⁠Project Management Templates by Mark Whitfield constitute a comprehensive toolkit of over 200 editable resources designed to accelerate project delivery across Agile, Waterfall, and PRINCE2 frameworks.

The structural breakdown of the core templates is organised by functional category, specific template, integrated Microsoft Office tool, and operational description:

1. Project Planning & Scheduling

  • Detailed SDLC Project Plan
    • MS Tool: Microsoft Project (.mpp)
    • Description: A master schedule structured around the Software Development Lifecycle (SDLC) from development through testing, deployment, and Early Live Support (ELS), easily toggled between Agile Scrum and traditional Waterfall.
  • PRINCE2 7th Edition Project Plan
    • MS Tool: Microsoft Project (.mpp) & MS Excel (.xlsm)
    • Description: Fully annotated task list aligned with the 7th edition principles, colour-coded by activity type (blue for artifact creation, brown for management decisions, purple for updates).
  • Detailed Waterfall Project Planner
    • MS Tool: MS Excel
    • Description: A portable, license-free alternative to MS Project featuring baseline versus forecast tracking, an integrated Gantt chart view, and automated progress charts.
  • Plan on a Page (POaP)
    • MS Tool: MS PowerPoint & MS Excel
    • Description: High-level, executive-ready roadmaps containing over 30 slide variations used to communicate project timelines, key milestones, and work streams to senior stakeholders.
1. Project Planning & Scheduling POAP MS PowerPoint
1. Project Planning & Scheduling POAP MS PowerPoint Templates
2. Project Planning & Scheduling MS Project Templates
2. Project Planning & Scheduling MS Project Templates
2. Project Planning & Scheduling MS Project Templates
3. Project Planning & Scheduling MS Excel Templates

2. Operational Control & Governance

  • Comprehensive RAID Log & Charts
    • MS Tool: MS Excel
    • Description: A highly detailed central registry featuring distinct tabs to track Risks, Actions, Issues, Opportunities, Dependencies, Lessons Learned, and Change Requests alongside visual metric dashboards.
  • Basic RAIDs Tracker
    • MS Tool: MS Excel
    • Description: A scaled-down, simplified version of the master RAID log optimized for quick turnarounds, minor bids, and low-complexity projects.
  • RACI Matrix
    • MS Tool: MS Excel
    • Description: A governance sheet mapping project deliverables against specific team roles to clarify who is Responsible, Accountable, Consulted, and Informed.
  • Agile Story Dependency Tracker
    • MS Tool: MS Excel
    • Description: A specialised log to document and track blocker stories tied to external suppliers or client-side dependencies that risk driving scope changes.
1. Operational Control & Governance MS Excel RACI Template
1. Operational Control & Governance MS Excel RACI Template

3. Financial & Resource Management

  • Project Financial Tracker
    • MS Tool: MS Excel
    • Description: A financial controller mapping internal and external forecast costs against actuals, factoring in margins, variances, supplier fees, and expense categories.
  • Resource, Sickness, & Leave Tracker
    • MS Tool: MS Excel
    • Description: An operational matrix monitoring annual leave, sickness, and training schedules to adjust resource availability and capacity within the master schedule.
1. Financial & Resource Management MS Excel Templates

4. Agile Delivery Metrics

  • Agile Burn Down & Burn Up Charts
    • MS Tool: MS Excel
    • Description: Manual data-table tracking solutions designed to visualise sprint or release velocity for teams operating without access to enterprise tools like Jira.
1. Agile Burn Down Chart in MS Excel
1. Agile Burn Down Chart in MS Excel Template Example
2. Agile Burn Up Chart in MS Excel
2. Agile Burn Up Chart in MS Excel Template Example

5. Communications & Administration

  • PRINCE2 Management Products
    • MS Tool: MS Word (.doc)
    • Description: A full portfolio of standard documentation masters including Project Initiation Documents (PID), Project Briefs, Highlight Reports, and Business Cases.
  • Project Status Report
    • MS Tool: MS Word & MS PowerPoint
    • Description: Weekly and monthly progress reporting templates featuring structured sections for milestones, blockers, financial status, and RAG indicators.
  • Kick-Off Deck & Mobilisation Kit
    • MS Tool: MS PowerPoint
    • Description: Onboarding and alignment slide decks designed to define scope, establish ground rules, and guide teams through project initiation.
  • Meeting Minutes Template
    • MS Tool: MS Word
    • Description: An action-oriented meeting layout tailored for capturing critical decisions, owners, and deadlines uniformly.
1. Communications & Administration MS Excel Status Report Template Example
1. Communications & Administration MS Excel Status Report Template Example

If you are looking to purchase or deploy these, the complete ecosystem is distributed on marketplaces like the ⁠ProjectTemplatesSoft Etsy Shop or through his official site Mark Whitfield’s Project Management Templates.

Best approach to writing a project plan with breakdown

The best approach to writing a project plan breakdown is to use a top-down decomposition strategy centered on a Work Breakdown Structure (WBS). This technique methodically slices a complex, high-level project into smaller, manageable chunks called work packages, ensuring that nothing is missed.

To build a flawless, actionable project breakdown, you must establish the project’s foundation before dissecting it into individual tasks.

1. Define the Scope and Deliverables

Before diving into a micro-level breakdown, you must know what you are building—and what you are not building.

  • Write a scope statement: Document the final outcomes, project boundaries, and explicit exclusions to prevent scope creep.
  • Identify major deliverables: Determine the high-level milestones or chunks of tangible value that must be completed.
  • Apply the 100% rule: The Project Management Institute (⁠PMI) notes that your WBS must include 100% of the internal, external, and interim project management work.

2. Structure the Levels of Decomposition

A good project plan breakdown uses hierarchical tiers. Do not mix daily tasks with macro phases. Instead, follow a logical breakdown hierarchy:

  • Level 1 (The Project): The overall project objective or final product.
  • Level 2 (Phases or Major Deliverables): Broad operational segments (e.g., Initiation, Design, Development, Testing).
  • Level 3 (Sub-deliverables): Specific components within a phase (e.g., under Development, you might have Frontend Architecture).
  • Level 4 (Work Packages): The lowest level of the WBS. These are discrete items that can be assigned to a specific team or individual and estimated for time and budget.

3. Apply the 80-Hour Rule

When decomposing down to the task level, determine how granular you need to be by tracking effort, not just calendar time:

  • The 80-hour threshold: A single work package should take no more than 80 hours (two weeks of full-time work) and no less than 8 hours to complete.
  • Avoid micro-management: If a task takes less than 8 hours, group it with others. If it exceeds 80 hours, it is too complex and needs to be broken down further.

4. Build a WBS Dictionary

A visual chart or list is helpful, but context prevents mistakes. For each work package at the bottom of your hierarchy, document:

  • Task description: Clear language outlining what “done” actually looks like.
  • Assigned owner: One single person or team responsible for the execution.
  • Pre-requisites and dependencies: Clarify which tasks must finish before the next can begin.

5. Sequence, Estimate, and Schedule

Once the work is broken down, pull it into a working chronological timeline using software like Microsoft Project (see MS .mpp templates in website banner), ⁠Asana or ⁠Monday.com.

  • Sequence activities: Map the chronological order and identify the critical path—the longest string of dependent tasks.
  • Estimate duration & resources: Gather the actual people doing the work to estimate time, capacity, and material needs realistically.
  • Add contingency: Factor in safety buffers to protect the project baseline from unexpected delays.

Microsoft Project Plan MPP Overview & Approach to Configuring a Good Plan

Microsoft Project is a powerful project management software used to plan, schedule, and oversee tasks, resources, and deadlines. Its native .mpp file format supports building Work Breakdown Structures (WBS), calculating critical paths, allocating resources, and monitoring project budgets within the Microsoft ecosystem.

Configuring a high-quality .mpp plan requires a systematic approach to ensure schedule accuracy and prevent logic errors. Follow this step-by-step methodology to build a robust plan:

1. Project Initialization

  • Set Project Information: Go to the Project tab, click Project Information, and define your Start Date. Ensure the scheduling is set to start from this date rather than a “Current Date” override.
  • Define Working Calendars: Adjust your project’s default calendar for weekends, statutory holidays, and company non-working time so the timeline accurately reflects actual working days.
  • Configure Default Scheduling: Go to File > Options > Schedule and set New tasks created to Auto Schedule. This ensures your tasks respond automatically to changes in predecessors and durations.

2. Work Breakdown Structure (WBS)

  • Brainstorm Task Lists: Before entering dates, list all project deliverables and normal tasks in the Gantt Chart view.
  • Apply Hierarchy: Use the Indent/Outdent features to organize tasks into major phases (Summary Tasks) and actionable subtasks (Work Packages).
  • Create Milestones: Set the duration of key deliverable completions or approval gates to 0 days to act as clear checkpoints on your timeline.

3. Task Dependencies & Logic

  • Establish Relationships: Link tasks in logical sequences (e.g., using Finish-to-Start relationships). Every task—except the very first one in the project—must have a predecessor.
  • Never Link Summary Tasks: Only link the lowest-level subtasks. Linking summary task bars introduces circular logic errors and unpredictability.
  • Avoid Hard Constraints: Do not type specific dates into the Start/Finish columns unless absolutely mandatory. Doing so creates “Must Start On” constraints that break the critical path when upstream tasks are delayed.

4. Resource Allocation

  • Setup the Resource Sheet: Navigate to the Resource Sheet and add all resources required to do the work, defining their standard rates, maximum capacities (e.g., 100% availability), and calendars.
  • Assign Resources: Return to the Gantt Chart and assign specific work resources (people) to corresponding tasks. This helps Microsoft Project calculate total effort and spot resource overallocations.
  • Resource Leveling: Use the built-in Resource Leveling feature to automatically adjust assignments and resolve conflicts when team members are overcommitted.

5. Finalizing and Tracking

  • Set a Baseline: Once the plan has been reviewed and approved by stakeholders, go to Project > Set Baseline. This captures a snapshot of your original scope, Start, Finish, Cost, and Work fields.
  • Set the Status Date: When recording progress, always set the Status Date to today’s date before entering percentage completions.