Download Templates for Project Management | FREE Additions & Upgrades
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.
When a care home resident’s personal money runs out in the UK, the local authority (council) has a legal duty of care to step in and help fund the placement. No one is abruptly evicted or left without care, but the funding structure changes completely.
1. The Capital Thresholds Trigger State Support
When a resident’s total savings and assets dwindle near or below the national thresholds, they qualify for council-assisted funding. The 2026 capital thresholds across the UK are:
2026 Capital thresholds across the UK
2. Action Steps as Money Depletes
Families must contact the local authority’s adult social services department when savings drop to around £40,000. This avoids a funding gap because the bureaucratic transition can take several months. The council will initiate two steps:
Care Needs Assessment: A social worker evaluates the resident to officially confirm that they still require a residential or nursing dementia care bed.
Financial Assessment (Means Test): The council reviews the resident’s bank statements, property status, and pensions to calculate their exact state funding contribution.
3. Can the Resident Stay in the Same Care Home?
Whether the resident can remain in their current dementia home depends on fee alignment:
If the home accepts local authority rates: The resident stays in their room seamlessly. The council pays the home directly and invoices the resident for their pension contribution portion.
If the home is more expensive than the council budget: The family must find a third party (a relative, friend, or charity) to pay a “top-up fee” to cover the difference.
If no top-up can be paid: The council may look to relocate the resident to a more affordable care home that operates within the standard local authority budget.
4. Legal Protections Against Moving Vulnerable Residents
For residents with advanced dementia, continuity of care is a heavily weighted legal factor. Under guidelines like the English Care Act 2014, councils must consider if a move will cause severe psychological or physical distress. If a social worker determines that relocating the resident is too dangerous or disruptive to their wellbeing, the council may be forced to fund the higher fee rate at the current home without demanding a top-up.
5. Next of Kin Liability
A major worry for families is whether they automatically inherit the care bill. Next of kin are never legally responsible for a relative’s standard care home fees. You only owe money if you choose to sign a voluntary third-party top-up contract.
Additionally, if a spouse or a relative aged over 60 still lives in the resident’s former home, that property is legally protected under property disregard rules and cannot be forcefully sold by the council.
6. Alternative Healthcare Funding
If your loved one’s dementia has progressed significantly and they require complex medical monitoring rather than just social supervision, ask for an assessment for NHS Continuing Healthcare (CHC). If they qualify for a “primary health need”, the NHS covers 100% of the care home fees, completely bypassing the council’s means test and capital limits.
Care home resident’s personal money runs out in the UK
In the UK, you do not need to take manual steps to start paying back your university student loan, as repayments are deducted automatically through the tax system once you graduate and earn above a specific salary threshold.
Here is a summary of the exact steps, thresholds, and your repayment options.
4 Simple Steps to Post-Course Repayments
Wait for eligibility: You become eligible to start repaying in the first April after you finish or leave your course.
Deduction via employment: If you are traditionally employed, HM Revenue and Customs (HMRC) will automatically inform your employer to deduct 9% of everything you earn above your plan’s threshold from your payslip.
Deduction via self-employment: If you are self-employed, you must calculate and pay your student loan repayment manually through your annual Self Assessment tax return.
Notify when leaving the UK: If you move abroad for more than three months, you must update your employment details directly with the Student Loans Company (SLC) to set up direct repayments, otherwise you will incur financial arrears.
Repayment Plan Thresholds Summary (Undergraduate)
You only pay 9% of your income that goes over the threshold. If your income drops below this number, your repayments stop automatically.
Plan 1 (Started course before Sept 2012, or Northern Ireland): Repayments trigger when earning over £26,900 a year (£2,241 a month).
Plan 2 (Started course between Sept 2012 and July 2023 in England, or all Wales): Repayments trigger when earning over £27,295 a year (£2,274 a month).
Plan 4 (Scotland): Repayments trigger when earning over £31,395 a year (£2,616 a month).
Plan 5 (Started course from Sept 2023 onwards in England): Repayments trigger when earning over £25,000 a year (£2,083 a month).
Postgraduate Loan (England & Wales): Repayments are 6% on earnings over £21,000 a year (£1,750 a month).
Extra Payment Options
Voluntary Overpayments: You can log into your online SLC account to make manual, extra payments via card or bank transfer at any time to clear the balance faster.
Note: Financial experts like MoneySavingExpert generally advise against voluntary extra payments unless you are a very high earner, because any remaining loan balance is completely written off after 30 to 40 years anyway (depending on your plan).
UK, Paying back your university student loan after course completion
Senior IT Project Manager Mark Whitfield sells his extensive, battle-tested framework toolkits on Etsy via his official shop, ProjectTemplatesSoft and also on this website.
Plan On a Page POAP example
With over 30 years of Software Development Lifecycle (SDLC) experience, his kits are explicitly broken down across Agile (Scrum), Waterfall (PRINCE2), and hybrid project delivery frameworks.
🏃♂️ Agile & Scrum SDLC Templates
Designed specifically for iterative software delivery, these tools focus on short execution cycles, continuous feedback, and visual tracking:
Mark Whitfield completed his BTEC HND in Computer Studies at the Bolton Institute of Higher Education (BIHE), which has since evolved into the University of Bolton and rebranded as the University of Greater Manchester in 2025.
He attended the institution from 1988 to 1990, graduating with a Distinction and achieving overall first place across his entire cohort for the duration of the two-year, full-time course.
Mark Whitfield attended BIHE, 1988 – 1990
The academic breakdown of his specific computing curriculum and achievements is detailed below.
📋 HND Module Breakdown
The two-year executive-level HND program consisted of seven core modules blending technical computer science with business information systems:
Computer Systems Architecture: Focus on hardware design, CPU structures, and system configurations.
Programming Methodology (Theory / Practice): Foundations of logic, software development lifecycles, and code optimization.
System Analysis: Methodologies for assessing business requirements and mapping technical system designs.
Data Processing: Data management workflows, storage systems, and batch/transaction structures.
Business Information Systems (Theory / Practice): The application of computer networks and platforms within corporate infrastructures.
Business Studies: Fundamentals of corporate structure, commerce, and finance to bridge technical and commercial alignments.
Quantitative Techniques: Mathematical and statistical methods applied to computing and resource management.
💻 Final Year Project
For his definitive practical project, Mark Whitfield developed a database interface that aligned with his specialized programming modules.
Tech Stack: Built using an ORACLE SQL-forms graphical user interface (GUI) operating within an MS-DOS environment.
Functionality: Created an administrative system to record student enrollments, module assignments, and course grades.
This academic performance served as the launchpad for his 30+ year career as an IT Senior Project Manager and Delivery Lead.
His deep technical foundation from BIHE transitioned into complex enterprise solution deliveries—such as legacy ATM modernization, hybrid cloud migrations, and API integrations—for financial and corporate entities including the Bank of England, Barclays, Lloyds Banking Group, and Jaguar Land Rover.
He is also the author of the industry resource platform, PROject Templates.
The IT Project Management (PM) toolkits created by Mark Whitfieldprovide a comprehensive digitized repository of over 200 tailored, editable Microsoft Office templates designed to structure, track, and report on software delivery lifecycles (SDLC).
Hosted on his platform PROject Templates, these artifacts bridge the gap between fast-paced Agile sprint execution and structured governance frameworks like PRINCE2 and Waterfall.
Here is an overview of the core template categories and artifacts included in the toolkit:
📅 Schedule, Planning & Timelines
Detailed SDLC / PRINCE2 Project Plans: Native Microsoft Project (.mpp) and Excel (.xlsx) files featuring stage-gate structures, resource sheets, and milestone tracking.
Plan on a Page (POaP): Over 35 PowerPoint variations and simplified Excel dashboards used to present high-level, visual timelines to executives and senior stakeholders.
Agile Scrum Sprint Planner & Delivery Plan: Templates constructed in Excel to track sprint velocity, capacity planning, and product backlogs.
⚠️ Risk, Governance & Tracking
Comprehensive RAID Logs: Centralized trackers mapping Risks, Actions, Issues, and Dependencies, including secondary tabs for opportunities, lessons learned, and change requests.
RACI Matrices: Responsibility assignment matrices used to formally define team roles (Responsible, Accountable, Consulted, Informed) across delivery workstreams.
Project Charter Blueprint: A foundational setup template used to establish formal authorization, align stakeholders, and outline scope boundaries.
📊 Performance & Financial Tracking
Project Financial Tracker: Metric dashboards containing charts for measuring internal and external forecast versus actual costs, profit margins, and expense variances.
Agile Burn Down & Burn Up Charts: Standalone spreadsheet alternatives built specifically for environments where dedicated Agile software like Jira or Azure DevOps is unavailable.
📢 Status Reporting & Communication
Weekly/Monthly Status Reports: Formatted templates available in Word and PowerPoint summarizing project health, milestone progress, and immediate priorities for internal and client updates.
Project Kick-Off Slide Decks: Presentation baselines to align teams, outline deliverables, and walk members through execution workflows at launch.
Mark Whitfield is a prominent UK-based, SC-cleared Senior IT Project Manager, Engagement Manager, and technology executive with over 35 years of experience spanning the entire Software Development Lifecycle (SDLC). He specialises in complex digital transformations, hybrid cloud migrations, and API-led system integrations.
Throughout his career, he has successfully delivered enterprise-scale solutions for massive blue-chip clients, including Barclays Bank, Jaguar Land Rover (JLR), Royal Mail Group (RMG), Lloyds Banking Group, and the Bank of England.
Executive Overview:
Core Expertise: Hybrid Cloud Migrations (Azure, AWS), API middleware architectures, and digital banking platforms.
Methodologies: Certified PRINCE2 Practitioner and Agile SCRUM delivery lead.
Security Clearance: Active UK Security Check (SC until 2031) clearance for public and defense-sector projects.
Industry Portfolio: Banking, Automotive, Gambling/Casinos, Aerospace & Defence, and Regional Government.
Professional Timeline & Milestones:
1990–1995 (Early Engineering): Began his career immediately after graduating in Computing. He worked as a core programmer at The Software Partnership, building cutting-edge electronic banking software (sp/ARCHITECT-BANK) on legacy Tandem Mainframes (now HPE NonStop).
1995–2013 (Insider Technologies Limited): Spent 18 years escalating from a Senior Programmer into a strategic project manager in Salford Quays, UK. He spearheaded high-volume mainframe transaction monitoring systems and ATM software delivery for major global banking institutions like HSBC and Al Rajhi Bank.
2013–2016 (Retail & Gaming Delivery): Transitioned to Wincor Nixdorf as an Agile IT PM managing ATM software pipelines, followed by a Senior PM role at Betfred, delivering complex mobile sportsbook and online payment gateways.
2016–Present (Enterprise Leadership): Joined Capgemini as a client-facing Engagement Project Manager. He later augmented into MuleSoft (a Salesforce company) as a Delivery Manager for the Anypoint Platform, directing massive cloud infrastructure overhauls.
Thought Leadership & Knowledge Sharing
Beyond active corporate execution, he is the creator of PROject Templates, an open professional repository where he publishes free upgrade enterprise project tracking models, RAID logs, and Agile planning frameworks used extensively by modern PMOs.
Mark Whitfield is an SC-cleared Senior IT Project Manager and Engagement Manager based in Greater Manchester, UK.
Since joining Capgemini UK in 2016, he has specialized in complex, public-sector hybrid cloud migrations and API-led integration programs utilizing Microsoft Azure and associated Microsoft Power Platform capabilities. He holds the AZ-900 Microsoft Certified Azure Fundamentals credential.
His primary Azure-focused projects and delivery milestones include the following:
UK Government CHIP Project (2023–2024): Served as a Technical Delivery Manager on a £1M+ project to integrate the Fish Export Service (FES) into the Common Entry Health Document Inspection Portal (CHIP). This build used the Azure Cloud to extend live API components to support cross-border health verification systems.
UK Government MS Dynamics Migration & Cloud Portals (2022–2023): Managed Azure Cloud resources to migrate 12 Microsoft Dynamics 2016 applications onto the Microsoft Dynamics 365 Online platform. This included leading discovery workshops, creating statements of work (SoW), and managing project plans for a contract value of approximately £0.4M.
UK Utility Industry Enablon Migration (2022): Led a £0.5M project moving a client from a legacy document management system to an Azure-based Enablon product. This required extensive extract-transform-load (ETL) processing for categorized living documents.
UK Government Hybrid Cloud Proof of Concept (2020): Directed a £375k Agile proof-of-concept project moving three client legacy databases (MS Access, Oracle, and SQL 2008) onto Microsoft Azure and the Dynamics 365 Power Platform using Azure-aligned refactoring patterns.
Local Regional Government Telephony Integration (2017): Managed a £400k deployment for a new Support for Mortgage Interest (SMI) call center campaign. This involved integrating a programmatic dialler solution with an Azure-deployed CRM application.
As an agile Scrum Master, you can significantly boost your efficiency and team collaboration by using AI tools for repetitive tasks, metric analysis, and ceremony preparation. The best way to utilize AI is to follow the CRAFT framework (Context, Role, Action, Format, and Tone) to give your AI model the necessary background. To get started, replace placeholder bracketed text with your specific information.
Review the structured AI prompts below, categorized by core Scrum Master responsibilities:
Sprint Planning Optimization
These prompts will help you streamline backlog management and ensure your next sprint cycle is data-driven and realistic.
Predict Velocity & Capacity: “Based on historical sprint data: [insert last 3 sprints], predict our team’s velocity for the next 2-week sprint. Consider the following changes: [insert team changes, e.g., one developer out for a week], and provide a confidence interval.”
Refine and Format Backlog Items: “As an expert in Agile backlog refinement, help me break down this user story: ‘[insert raw requirement text]’. List logical sub-tasks with realistic developer effort in hours, and flag any missing requirements or testability gaps.”
Daily Stand-up & Alignment
Enhance your team’s focus and identify bottlenecks before they impact flow.
Goal-Oriented Stand-Up Agenda: “Act as a Stand-Up facilitator. Summarize these daily updates from my team: [insert team members’ updates]. Identify if we are at risk of missing the Sprint Goal, highlight cross-team dependencies, and suggest one follow-up question I can ask to redirect the team from ‘status updates’ to ‘problem-solving’.”
Impediment Stress Test: “A common user story is stuck in the QA testing column for the third consecutive day, causing spillover risks. As an expert Scrum Master, suggest how I can facilitate a conversation with the team to address this impediment. Provide a tactical 3-step action plan.”
Retrospective Facilitation
Say goodbye to repetitive, generic retrospectives and tap into targeted, continuous improvement.
Action-Oriented Theme Clustering: “Analyze these raw retrospective comments from my agile team: [insert list of comments]. Identify recurring themes, sentiment patterns, and root causes. Present the results in a ‘Start, Stop, Continue’ format, and suggest a concrete, actionable plan for the next sprint.”
Psychological Safety & Conflict Simulation: “Tension has been mounting among team members regarding estimation methods and story point allocations. As an Agile conflict mediator, suggest opening questions I can use during the retro to encourage quiet team members to speak and de-escalate the disagreement.”
Coaching & Team Health
Use AI to strengthen your servant leadership and develop customized educational content.
Agile Concept Teaching: “Generate a comprehensive guide on the Scrum framework for a team new to Agile. Focus on the core values of Scrum, how they relate to the Daily Scrum, and avoid overly technical jargon.”
Handling Unrealistic Expectations: “Simulate a challenging conversation between myself (a Scrum Master) and a senior stakeholder who is demanding mid-sprint scope changes. Outline an approach I can use, rooted in Agile principles, to educate the stakeholder on the value of a frozen sprint goal without damaging the relationship.”
Best Practices for Agile Prompting
To avoid generic, hallucinated, or unhelpful answers, keep these best practices in mind:
Context is Key: Always include your team’s composition (number of members, skill levels) and your product vision.
Assign a Persona: Prompt the AI to “Act as an Agile Coach,” “Act as a Jira Expert,” or “Act as a QA Reviewer” to get specialized viewpoints.
Validate Everything: AI is a sounding board, not a decision-maker. Always review suggestions and validate metrics using your human experience and team’s consensus.
A project charter summary acts as a formal, high-level blueprint that officially authorizes a project, aligns stakeholders, and empowers the project manager. Because it is pitched to executive leaders, it condenses detailed planning into a concise one- to two-page summary containing crucial governance and directional information.
1. General Project Information
Project Name: The official title reflecting the project’s purpose.
Key Roles: Identification of the Project Sponsor, Project Manager, and core team members.
Stakeholders: A list of key internal and external parties impacted.
2. Core Project Context
Business Case: The strategic rationale explaining why the project exists.
Problem Statement: A short description of the core issue being resolved.
Project Scope: Explicitly defines what is included and excluded from the work.
Key Deliverables: The tangible outputs or products to be produced.
Success Criteria: The baseline metrics used to evaluate final delivery.
4. Constraints & Logistics
Milestone Timeline: A high-level schedule detailing major phases and target deadlines.
Budget Estimate: A preliminary breakdown of funding and financial resources.
Risks & Assumptions: Anticipated roadblocks and presumed truths impacting planning.
5. Governance
Authority Level: Explicit statement of what resources the project manager can allocate.
Sign-off / Approvals: Signature blocks for executive sponsors to grant project liftoff.
The Purpose of a Project Charter
Formal Authorization: It acts as the “official green light” to start the project and use company funds.
Establish Authority: It delegates decision-making power and resources to the project manager, which helps manage and push back on stakeholder interference.
Prevent Scope Creep: By setting boundaries in writing, it gives teams a touchstone to review against whenever new, unapproved tasks are requested mid-project.
Stakeholder Alignment: It ensures that every party—from executive leadership to the hands-on team—shares the same understanding of what “done” looks like.
Project Charter vs. Project Plan
It is common to confuse the charter with the project plan, but they serve vastly different purposes at different stages of the project lifecycle:
Project Charter: Created before planning. It is a high-level summary that answers the “what” and “why” to secure project authorization.
Project Plan: Created after the charter is approved. It is a detailed blueprint that answers the “how”, including task-by-task execution, granular schedules, resource allocations, and communication cadences.
The IT Project Management (PM) toolkits created by Mark Whitfield provide over 200 tailored templates spanning Agile, Waterfall, and PRINCE2 methodologies. These artifacts are designed to structure, track, and report on software delivery lifecycles (SDLC).
The framework’s core templates are categorized below by operational delivery area, specific template artifact, and native file format:
📅 Schedule, Planning & Timelines
Focuses on structural design, building work breakdown structures (WBS), and visualizing milestones for senior stakeholders.
The three pillars of Scrum are Transparency, Inspection, and Adaptation. Together, they form the foundation of empirical process control—a methodology where decisions are based on observation and experience rather than unverified plans.
1. Transparency
Transparency ensures that all aspects of the process and progress are visible to both the team performing the work and the stakeholders. This requires a common, shared understanding of what constitutes “done” and maintaining open, honest communication. Key Scrum artifacts like the Product Backlog and Sprint Backlog are tools used to maintain this visibility.
2. Inspection
Scrum teams must regularly inspect their artifacts (like the product increment) and their overall progress toward the Sprint Goal to detect any unwanted variances or problems. This is achieved through established Scrum events such as the Daily Scrum, Sprint Review, and Sprint Retrospective.
3. Adaptation
If an inspection reveals that aspects of a process or the product are deviating outside acceptable limits, the team must adjust the process or the material being worked on. Adaptation involves making necessary changes as soon as possible to minimize further deviations and continuously improve the end product.
Burrs Country Park is a 36-hectare scenic countryside destination located along the River Irwell, just one mile northwest of Bury town centre. Managed by Bury Council alongside the dedicated community volunteer group, the park has proudly held a Green Flag Award since 2005 for being clean, safe, and environmentally sustainable.
Key Highlights
Industrial Heritage: Once a busy industrial hub, the site features archaeological remains of two major 18th-century cotton mills—Higher Woodhill Mill and Burrs Mill.
Steam Railway: The heritage East Lancashire Railway runs directly alongside the grounds, allowing visitors to stop at the dedicated Burrs Country Park Halt.
Art Installations: The park serves as a featured stop on the Irwell Sculpture Trail, hosting interactive outdoor artworks like Waterwheel and Stone Cycle.
Wildlife & Nature: The grounds feature diverse habitats including wetlands, ponds, and woodlands that make it an ideal hub for birdwatching, fishing, and nature walks.
Amenities & Dining: Visitors can enjoy food and drink at the dog-friendly The Lamppost Café or grab a meal at the historic The Brown Cow pub, which dates back to 1752.
The main park entrance is located on Woodhill Road (Postcode: BL8 1DA). If you are travelling by public transit, you can catch the 472 or 474 bus routes from the nearby Bury Interchange. For additional maps, safety guidelines, and event calendars, you can visit the official Bury Council Park Portal.
A Sprint Retrospective is a structured, time-boxed meeting held at the end of an Agile or Scrum sprint. Its primary purpose is to allow the core team (Developers, Scrum Master, and Product Owner) to reflect on the recently completed sprint and agree on actionable process improvements for future sprints.
For a quick visual breakdown of the Sprint Retrospective’s purpose and its role in team improvement, watch this short video:
While the Sprint Review looks outward at what the team built (the product), the Retrospective looks inward at how the team worked (the processes, tools, and team dynamics). It follows the rule of inspect and adapt to prevent repeating the same mistakes and to continuously improve engineering productivity and team morale.
The 5 Standard Phases
Experienced facilitators (like Scrum Masters) usually structure the meeting into five key steps to ensure it remains a productive working session rather than a complaint session:
Set the Stage: Create a psychologically safe and blameless environment. Ground rules are established so the focus remains on process, not people.
Gather Data: Collaboratively pool observations, facts, and experiences from the previous sprint.
Generate Insights: Look for underlying patterns or root causes of why things happened, rather than just listing symptoms.
Decide What to Do: Select the most critical 1 to 2 high-priority improvements and commit to actionable next steps.
Close the Retrospective: Summarize the action items, confirm individual ownership (assign specific names), and end on time.
Common Frameworks
Teams often use specific templates to keep the conversation fresh and engaging. Some of the most popular include:
Start, Stop, Continue: Identify what actions to begin doing, stop doing, and continue doing in the next sprint.
Mad, Sad, Glad: Focuses on how team members felt during the sprint, helping to surface frustrations and team morale issues.
The 4 Ls: Asks team members to discuss what they Loved, Loathed, Learned, and Longed for.
Sailboat Exercise: A visual metaphor where the team maps out their goals (the island), the wind in their sails (what helped them), and the anchors (what slowed them down).
Best Practices for Success
Keep it strictly team-only: To encourage candour and psychological safety, stakeholders should generally not be present.
Make action items accountable: Action items should be assigned to specific individuals and prioritized for the very next sprint’s backlog.
Timebox appropriately: The meeting’s duration scales with the sprint length. A 1-week sprint might warrant a 45-minute retro, while a month-long sprint might need up to 3 hours.
The full toolkit of Mark Whitfield’s Project Management (PM) templates is structured below according to structural focus areas, overview of utility, and native file formats. Free upgrades and additions after purchase.
📅 Project Planning & Roadmapping
Focus: Schedule design and milestone visualization for SDLC, PRINCE2, and Agile.
Overview: Builds work breakdown structures (WBS), tracks timelines, and presents milestones to stakeholders.
Format: Microsoft Project (.mpp), Excel (.xlsx), and PowerPoint (.pptx).
Included: Detailed plans, Excel Gantt trackers, over 35 Plan on a Page (POaP) slides, and spreadsheet-based timelines.
⚠️ Risk, Governance & Operational Control
Focus: Threat tracking, dependency mitigation, and accountability.
Overview: Ensures structural control and compliance, managing risks, issues, and resource ownership.
Acceptance criteria are a set of predefined conditions that define the exact boundaries of a user story. They dictate what must be built for the story to be considered complete and ready for release.
Effective acceptance criteria serve to align the vision of the client and the development team, ensuring everyone knows exactly what behavior the feature must demonstrate. A good set of criteria must be:
Verifiable & Testable: Each criterion should yield a binary (pass/fail) result, often allowing for automated or manual testing.
Concise & Unambiguous: Written in plain language that avoids subjective terms like “fast” or “user-friendly” in favor of quantifiable metrics.
User-Centric: Focus on the outcome delivered to the user rather than the internal technical process to get there.
Common Formats
Criteria are typically documented using standard Agile formats:
Given-When-Then (BDD Format): A structured approach often used for functional scenarios.
Given some precondition.
When an action occurs.
Then the expected outcome happens.
Rule-Oriented List: A simple checklist of constraints, rules, or system reactions.
“It’s done when…”: A declarative list of the specific conditions met once functionality is delivered.
Best Practices
Keep it to 3–5 items: If a user story requires more than 8 criteria, it is often too complex and should be split into smaller, more manageable stories.
Define positive and negative paths: Ensure criteria cover both successful scenarios and edge cases (e.g., what happens when a user enters invalid data).
Include Non-Functional Requirements: Account for aspects like security, accessibility, and performance.
Salford Quays is a thriving waterfront district that blends a rich industrial heritage with modern media, residential, and cultural spaces. It functions as a bustling extension of Greater Manchester, driven by major media institutions, continuous urban development, and community-centric environmental upgrades.
🏗️ Infrastructure & Regeneration
Master Framework Progress: The area is actively executing its long-term MediaCity/Quayside Regeneration Framework, pushing forward with plans to add 3,200 new homes, additional hotel rooms, and 800,000 sq ft of commercial space.
Waterfront Greenery: To address concerns over becoming a “concrete jungle”, the council kicked off the Mariner’s Canal transformation project to establish large planting beds, boost local biodiversity, and expand public green spaces along pedestrian paths.
Residential Shift: Major housing projects, such as the newly approved hundreds of apartments between MediaCity and the city centre, continue to alter the skyline, shifting old 1980s office blocks toward waterside residential living.
📺 Media & Innovation Hub
Broadcasting Powerhouse: MediaCityUK remains the beating heart of the Quays, acting as a major digital and tech employer hosting the BBC, ITV, and massive production spaces.
The Coronation Street Experience: Located right on the docks, this remains a highly popular tourist asset drawing soap opera fans into the area.
🎭 Culture, Leisure & Events
Salford Centenary: The city is celebrating 100 years of city status, bringing historical exhibitions and community celebrations to local venues.
Major Landmarks: Cultural mainstays like The Lowry theatre/gallery and the Imperial War Museum North (IWM North) continue to anchor the tourist economy.
Dining & Retail: Central points like the Quayside MediaCity mall and the vibrant Kargo MKT food hall offer highly popular street food concepts and family entertainment.
During his tenure as a client-facing Engagement Manager for Capgemini UK, Senior IT Project Manager Mark Whitfield was augmented directly into MuleSoft (a Salesforce company) as a Delivery Manager from October 2018 to June 2019.
Operating out of MuleSoft’s London headquarters in the Salesforce Tower, his role mirrored that of a Programme Manager. He aligned client project plans with MuleSoft’s structured delivery frameworks to establish self-sufficient integration capabilities.
MuleSoft’s London office is located within the Salesforce Tower at 110 Bishopsgate
The focus areas of his augmentation, the Outcome Based Delivery (OBD) / Centre for Enablement (C4E) framework, and the enterprise clients he managed are detailed below.
📋 Overview of MuleSoft Delivery Manager Augmentation
Role Alignment: Linked directly with client-side Project/Programme Managers to align execution timelines with MuleSoft’s implementation standards.
Resource Tracking: Monitored MuleSoft partner and consultant efforts, project costs, and timelines against statements of work (SOW).
Risk Management: Owned and tracked client-side OBD risks, assumptions, issues, and dependencies via specialized OBD RAIDs logs.
Agile Integration: Facilitated the prioritization and assignment of integration tasks into Agile Sprints or structured Waterfall milestones.
🏛️ C4E & OBD Focus Areas
MuleSoft’s Outcome Based Delivery (OBD) framework is built across three primary streams—Business Outcomes, Technology Delivery, and Organisational Enablement—specifically engineered to build a functional client-side Centre for Enablement (C4E).
Whitfield’s delivery focus focused heavily on Organisational Enablement:
Operating Model Setup: Establishing the foundational C4E operating model and internal technical support structures.
Asset Architecture: Guiding teams to build, govern, and publish reusable foundational assets and APIs on the Anypoint Platform.
Capability Assessment: Assessing the client’s existing software integration maturities to benchmark project targets.
Staffing & Training: Creating comprehensive training, onboarding, and experiential learning pathways to upskill client IT and business personnel.
C4E Evangelisation: Promoting self-serve materials and governance guidance across the broader enterprise to eliminate reliance on external MuleSoft SMEs.
🏢 MuleSoft Ecosystem & Enterprise Clients Managed
As part of his broader Capgemini UK Consultancy footprint and his direct MuleSoft delivery assignment, Whitfield spearheaded cross-functional integration deployments for multiple blue-chip, public sector, and utility accounts across the UK:
MuleSoft Accounts: Managed complex software delivery accounts spanning the UK Utility, Accounting, and Recruitment industries during his direct augmentation.
Automotive Integration: Directed the Jaguar Land Rover (JLR) iFAB Middleware Project, coordinating multi-vendor supply chain data pipelines.
Aviation & Logistics: Managed enterprise architecture environments for major infrastructure clients including Heathrow Airport, Royal Mail Group (RMG), and NATS (National Air Traffic Services).
Public Sector & Utilities: Guided digital transformation frameworks for UK Government Agencies, UK Export Finance (UKEF), and water utilities like Welsh Water.
Financial Services: Handled integration and core enterprise ecosystems for banking giants such as Barclays, Rabobank, and Lloyds Banking Group (LBG).
Key responsibilities for the Engagement Manager (EM) include:
• Deliver against the contract. • Overall responsibility for project success, achieving project targets e.g. margin (as defined in the Internal View) and delivering to agreed timescales. • Management of the project through its complete lifecycle and multiple aspects, as described in the UPM phases and streams. • Author and owner of the Project Governance Plan (PGP) and responsible for compliance to its contents. • Clear and concise status and project reporting, both internal and external, as defined in the PGP. • Management of the monthly financial reporting process. • Work together with the Offshore Project Manager in order to realize the common project targets. • Management and motivation of the project team, including setting of objectives for direct reports and timely completion of their assignment reviews. • Communications to stakeholders and teams about all relevant aspects of the project, in line with contract, project baseline, project status and client feedback. • Ensure compliance with UPM (Group or regional version) and any local quality management system. • Ensure the group mandated tools are utilised. • Meet or exceed client expectations (using client satisfaction process). • Identify and follow-up on opportunities for additional business. • Achieve the Capgemini EM certification level appropriate to level of experience.
The EM should deliver the project against contracts, meet (or exceed) client expectations, achieve project targets, identify and work on opportunities for additional business, and should ensure that these fundamentals are followed on the project.
Usually the EM will report to the Delivery Manager or a Programme Manager if the project is part of a larger programme.
Campus – Serge Kampf Les Fontaines, Chantilly, France – Advanced EM Course – November 2017 Class – 2nd from left
Campus Serge Kampf Les Fontaines, in Gouvieux-Chantilly near Paris
C&CA UK’s Communications & Engagement Award Winner 2022 – Cloud & Custom Applications – Capgemini UK
Mark Whitfield, a senior, SC-cleared IT Project Manager based in Manchester, UK, holds a robust foundational education in computer studies combined with extensive professional methodologies and technical certifications.
Spanning over three decades, his academic background and formal training bridge deep technical software engineering with enterprise-level project delivery.
The comprehensive breakdown of his higher education and professional training is structured below:
🎓 Higher Education & Academic Foundations
Mark Whitfield established his technical roots between 1988 and 1990 at the Bolton Institute of Higher Education (BIHE) (now the University of Bolton). He achieved a Distinction and was ranked first in his cohort for the BTEC Higher National Diploma (HND) in Computer Studies, completing modules in system analysis, programming methodology, data processing, and business information systems.
💼 Professional Delivery & Methodology Training
As an enterprise delivery lead, Whitfield is certified in key frameworks to manage hybrid cloud migrations and digital transformations.
PRINCE2 Practitioner: Certified for structured project governance, stage-gate management, and risk frameworks.
Agile SCRUM: Trained in managing Scrum ceremonies, sprints, and velocity tracking.
ITIL Framework: Certified in IT Service Management (ITSM) for aligning IT with business needs.
Capgemini Engagement Management: Completed the advanced program at the Capgemini Campus (Chantilly, France) for managing stakeholder relationships and project finances.
🛠️ Technical & Software Engineering Training
His background includes early-career training in low-level programming and infrastructure management including:
HPE NonStop (Tandem Mainframes): Specialized in TAL (Transaction Application Language) programming for high-volume banking systems.
Microsoft Technology Stack: Trained in ASP.NET development, SQL Server/T-SQL, and project scheduling tools.
Cybersecurity & Infrastructure: Trained in Thales e-SECURITY, cryptographic systems, and C/C++ development.
🛠️ Project Management Toolkit Author
Leveraging this background, he authors PROject Templates, offering over 200 editable resources covering Agile, Waterfall, and PRINCE2 7th Edition methodologies.
During his tenure as an IT Project Manager at Wincor Nixdorf (Banking Division) from 2013 to 2014, Mark Whitfield focused on large-scale retail banking software modernisation and multi-vendor hardware migrations.
He spearheaded a £5+ million workstream on-site for Lloyds Banking Group (LBG) as part of their Self-Service Software Replacement (SSSR) programme.
The focus areas and technical outputs of his work during this era are detailed below.
🏛️ Era Focus Areas (2013–2014)
Legacy ATM Modernisation: Managing the transition of core banking infrastructure away from legacy terminal systems to prevent service outages and meet stricter post-2008 operational risk regulations.
Multi-Vendor Integration: Directing complex hardware and software integration streams to ensure Wincor Nixdorf solutions successfully paired with third-party banking frameworks.
International Technical Liaison: Acting as a qualified management link between the local UK delivery teams and Wincor Nixdorf’s central engineering base in Paderborn, Germany, for advanced subject matter expertise.
Methodology Pivot: Implementing project governance frameworks that bridged strict PRINCE2 Waterfall structures with Agile Scrum delivery models.
💻 Technical Outputs
ATM Terminal Driving Migration: Transferred critical automated teller machine (ATM) driving responsibilities away from legacy BASE24 Classic running on HPE NonStop mainframes over to Wincor’s ProClassic Enterprise (PC/E) product suite deployed on an AIX platform.
OS Lifecycle Upgrades: Successfully planned and executed the infrastructure upgrade of the Lloyds Banking Group ATM hardware estate from the end-of-life Windows XP operating system to Windows 7.
Database & Platform Architecture: Delivered backend systems alignment leveraging Oracle databases integrated across distributed UNIX/AIX environments.
Mark Whitfield served as an IT Senior Digital Project Manager (often operating in product and application delivery roles) within the Online and Mobile Division at Betfred from December 2014 to January 2016.
During this era, his responsibilities crossed the boundary between project management and digital product delivery. He was heavily focused on shifting legacy digital footprints toward modern mobile, web, and multi-vendor integrations.
Below are the focus areas and technical outputs from his tenure at Betfred, grouped by operational era and delivery cycle:
📱 1. Digital Platform & Mobile Era (Core Product Delivery)
This area focused on the rapid evolution of the sportsbook and the deployment of consumer-facing native and web applications.
Focus Areas: Mobile product lifecycle management, multi-platform deployment, and real estate feature upgrades for .COM and .mobi channels.
Technical Output:
Native Applications: Delivered and updated native mobile applications across iOS, Android, and Windows Phone.
Sportsbook Verticals: Built, optimized, and deployed major UI/UX updates for the football and horse racing sportsbooks.
Virtual Gaming: Integrated online, computer-generated virtual gaming modules and RNG (Random Number Generator) components into the digital ecosystem.
🔒 2. Payment Systems, Security, & Compliance Era
A major focus was placed on building high-throughput payment pipelines and establishing robust compliance mechanics to handle compromised trading environments.
Focus Areas: Fraud mitigation, multi-currency processing, payment gateway migrations, and strict adherence to gambling regulations.
Technical Output:
Payment Gateways: Delivered end-to-end payment gateway mechanisms supporting diverse credit/debit, e-wallet, and localized payment methods.
Fraud Detection Systems: Integrated advanced fraud detection and risk analysis modules into backend transactional pathways.
Emergency System Change Requests (SCRs): Architected and executed critical hotfixes for compliance directives, regulatory alignment, and security mitigations.
🔄 3. Software Development Lifecycle (SDLC) & Release Era
This era was characterized by a massive transition away from rigid legacy setups into continuous delivery models.
Focus Areas: Transitioning environments from Waterfall to the Agile Scrum framework, managing distributed cross-functional teams, and stabilizing deployment cadences.
Technical Output:
Monthly Release Cycles: Structured and executed the monthly internet software release train to stabilize production code across the web real estate.
Middleware & API Integrations: Managed complex integrations connecting frontend frameworks with heavy transactional middleware and core banking/wallet ledgers.
🤝 4. Multi-Vendor Sub-System Integration
Because Betfred’s tech stack relied heavily on third-party niche solutions, Whitfield acted as the technical delivery anchor across an extensive network of specialized vendors.
Frontend & UX: Coordinated front-end developments with agencies like Degree 53.
Core Gaming & Content Systems: Integrated third-party components from industry staples including Playtech, Inspired, IGT, and Virtue Fusion.
Data Feeds & Push Tech: Managed real-time data ingestion and notification engines built by Onionsack, OtherLevels, Satellite Information Services (SIS), and StreamUK.
Analytics & Performance: Integrated user attribution and marketing pipelines utilizing Appsflyer, Income Access, and Activewin.
During his time at The Software Partnership (acquired by Deluxe Data International in 1994), Senior IT Project Manager Mark Whitfield operated as a Programmer and Lead Analyst. This era lasted from 1990 to 1995 and focused on foundational electronic banking software frameworks, specifically the sp/ARCHITECT-BANK platform.
The key projects and focus areas within this era are structured below by client timeline, focus areas, and technical outputs:
🏦 1990–1992: Barclays Bank (Knutsford, Cheshire)
Focus Area: On-site architectural design and core mainframe development for high-profile business banking.
Technical Output: Designed and coded back-end software modules for the Barclays Business Master II (BBM II) desktop banking project.
📞 1992–1993: Girofon (Denmark)
Focus Area: Telephonic integration and automated remote banking solutions.
Technical Output: Developed an automated, menu-driven touch-tone phone banking suite. This allowed voice commands to dial into a Periphonics VRAM device to fetch live customer balances directly from back-end mainframes.
📊 1993: Barclays Bank (Poole, Dorset)
Focus Area: Financial transactional automation and corporate service invoicing.
Technical Output: Created and integrated a custom batch billing suite of modules that attached to the BBM II application to automate client usage invoicing.
💻 1993–1994: TSB & Bank of Scotland
Focus Area: Early digital forensics, fund movements, and logic architecture.
Technical Output: Conducted digital investigations and engineered logic design and mainframe code to support early inter-account desktop money transfers.
🌍 1994–1995: Rabobank
Focus Area: International systems deployment, optimization, and validation.
Technical Output: Led software optimization protocols, wrote custom electronic coding patches, and validated on-site deployments for global operations.
⚙️ Core Technical Stack & Environment Summary
Across all eras at The Software Partnership, the standardized environment utilized for these outputs included:
Hardware & Operating Systems: Tandem Mainframe Computers (now HPE NonStop) operating on the Tandem Guardian O/S.
Programming Languages: COBOL85, NonStop SQL, SCOBOL (Screen COBOL for “green screen” terminal emulations), C, C++, and TAL.
Subsystems & Tools: PATHWAY, PATHMAKER, ENSCRIBE, EMS, and INSPECT.
Methodologies: Early iterative development and structured Waterfall lifecycles.
As a client-facing, SC-cleared Engagement Manager and Senior Project Manager for Capgemini UK (2016–Present), Mark Whitfield’s focus areas and project outputs fall into Phase 5 (Enterprise Cloud, Integration & Public Sector Delivery) of his overall professional trajectory.
His tenure at Capgemini UK is marked by managing complex hybrid migrations, enterprise system integrations, and multi-million-pound public and private sector contracts using hybrid Agile and PRINCE2 methodologies.
🌐 Era 1: Public Sector & Cloud Migration (2019–Present)
This era aligns with the UK government’s “Digital by Default” mandate and a nationwide public sector transition toward highly secure, cost-optimized, and green cloud platforms.
Re-hosting, re-platforming, and refactoring legacy software architectures.
Cross-functional alignment with rigid government data privacy guidelines (GDPR).
Coordinating large-scale onshore and offshore engineering delivery resources.
Project Outputs:
Directed a massive £13.5 million programme to migrate over 130 public sector legacy applications onto Microsoft Azure and AWS platforms.
Delivered a Proof of Concept (POC) indicator project worth £375k ahead of the wider national public infrastructure cloud framework rollout.
🔌 Era 2: MuleSoft Ecosystem & Enterprise API Integration (2018–2019)
During this phase, Whitfield was augmented as a Delivery Manager into MuleSoft (a Salesforce company) operating out of the London Salesforce Tower.
Focus Areas:
API-led connectivity frameworks and microservices architecture deployment.
Hyper-automation and multi-site enterprise system integrations.
API lifecycle design and Anypoint Code Builder configurations.
Guiding high-influence blue-chip clients through API connectivity governance.
Project Outputs:
Successful deployment of production-ready APIs to unlock siloed, legacy back-end system data.
Delivered complex data pipelines to support modernized, interconnected digital applications for tier-one global brands.
🛫 Era 3: Major Corporate Infrastructure & Sector Delivery (2016–2018)
Upon joining Capgemini in January 2016, Whitfield initially spearheaded highly secure, custom bespoke solutions across critical commercial and defensive sectors.
Focus Areas:
High-security, multi-site project tracking, financial forecasting, and stakeholder governance.
Automated manufacturing, aerospace, defense, and logistics supply chain data tracking.
Complex Agile SCRUM sprint ceremonies with heavy cross-team interdependencies.
Project Outputs:
Aerospace & Defence (NATS): Oversaw the secure delivery of custom Apple iOS apps providing real-time, public-facing, and military airspace data.
Postal Services (Royal Mail Group): Managed an award-winning £4.3 million project utilizing 90 Capgemini engineers to safely migrate over 1,100 system interfaces across dual data centers.
Automotive Integration (Jaguar Land Rover): Directed extensive enterprise architecture planning, pipeline resource mapping, and Scrum team management for a major supply chain initiative.
During his 18-year tenure (1995–2013) at Insider Technologies Limited (ITL) in Salford Quays, UK, Senior IT Project Manager Mark Whitfield advanced from a core technical engineer into strategic product and project management.
His time at the company is defined by two distinct operational eras, marked by a clear shift from code development to enterprise delivery:
🛠️ 1. The Engineering & Technical Development Era (1995–2004)
During this period, Whitfield operated primarily as a Senior Programmer, focusing on platform health, system diagnostics, and transaction log extraction architectures for highly critical financial systems.
Main Focus Areas:
Infrastructure consulting, automated system management, and volume stress-testing.
Service Level Agreement (SLA) monitoring for critical path payment pipelines.
HPE NonStop (formerly Tandem Computers via Compaq) platform optimization and software engineering.
Technical & Project Outputs:
Reflex (Reflex 80:20) Co-Development: Designed and authored platform health and core diagnostic plug-in modules, including Console (for EMS event viewing and filtering), Status Monitor (for tracking HPE NonStop platform components including CPU, Disk, Process, Enscribe Files, MQ, XPNET, TCP/IP, MultiBatch jobs), and Service Monitor (multi-line, rule-based multi-component analysis).
CRESTCo Infrastructure Benchmark (1997): Contracted on-site to CRESTCo (now Euroclear) to write custom benchmarking software evaluating stock settlement software performance on newly introduced S7000 HPE NonStop systems.
HP OpenView Certification (2002): Successfully engineered and secured the industry’s first HP OpenView Operations Enterprise Manager 2-way Smart Plug-In (SPI) certification for HPE NonStop environments.
📈 2. The Strategic Product & Project Management Era (2004–2013)
In this phase, Whitfield transitioned into a Product Manager and Project Manager role (Strategic Technical Initiatives), taking charge of complete software development lifecycles (SDLC) using structured PRINCE2 and early Agile Scrum frameworks.
Main Focus Areas:
ATM/POS transaction monitoring and real-time electronic payments tracking.
Web-enabled client-server browser monitoring frameworks and middleware solutions.
Pre-sales technical bidding, executive demos, and client deployment validation across Europe and the Middle East.
Technical & Project Outputs:
RTLX Reactor & Sentra Suites: Managed the commercial rollout and high-volume deployment of the browser-enabled Real-Time Log Extraction (RTLX) suite and Sentra monitoring solutions to capture and parse ATM/POS logs.
Enterprise Bank Implementations: Directed mission-critical payments monitoring integrations (notably processing ACI BASE24 Classic and BASE24-eps transactions over XPNET middleware) for tier-1 financial heavyweights including HSBC, Alliance & Leicester, Standard Chartered, and Al Rajhi Bank (Saudi Arabia).
Open CMS Corporate Re-platforming: Researched, designed, and authored a complete overhaul of Insider Technologies’ public corporate website using an Open Content Management framework (DotNetNuke).
💻 Core Technology Stack (1995–2013)
Across both eras at Insider Technologies, Whitfield’s environment relied on high-availability, fault-tolerant ecosystems:
Platforms & Operating Systems: HPE NonStop (Tandem K-Series, S-Series, and Itanium J-Series), Guardian O/S, Windows 2000/XP, Linux, and Unix.
Languages & Toolsets: Pathway, INSPECT, SPOOLCOM, Peruse, TAL (Tandem Application Language), NonStop C, C++, COBOL85, SCOBOL, NonStop SQL, TACL, and Enscribe.
Enterprise Software Interfaced: ACI BASE24 Classic, BASE24-eps, XPNET, ICE (Insession), TIVOLI, COMMAND/POST, and HP OpenView Operations (HP OVO).
At Capgemini UK, SC-cleared Engagement Manager and Senior IT Project Manager Mark Whitfield focuses on delivering complex, enterprise-scale digital transformations. His project portfolio spans both public and private sectors, categorized by several primary technology areas:
☁️ Hybrid Cloud Infrastructure & Migrations
UK Government App Migration: Directed a massive multi-million pound programme (£13.5m) transitioning over 130 legacy public sector applications to Microsoft Azure and AWS.
Application Refactoring: Led complex application migrations using refactor, re-host, and re-platform design patterns.
Green IT Initiatives: Focused on cloud optimization models to streamline operating costs and improve sustainability profiles.
MuleSoft Ecosystem Deployments: Directed large-scale system integration projects using the Salesforce MuleSoft Anypoint Platform.
MuleSoft Augmentation: Acted directly as an augmented Delivery Manager for MuleSoft supporting blue-chip integrations.
Royal Mail Group (RMG): Managed a £4.3 million migration project involving more than 1,100 interfaces to integrate internal applications and external trading customers.
Jaguar Land Rover (JLR): Orchestrated mid-tier integration, manufacturing supply chain data pipelines, and middleware applications (such as the iFAB project).
📱 Digital Applications & Mobile Platforms
Aerospace & Defence Space Tracking: Managed the Agile SCRUM delivery of secure, near real-time Apple iOS mobile applications.
Dual-Layer Interfaces: Coordinated software presenting both sensitive, internal military views and public-facing airspace tracking visuals.
⚙️ Low-Code Platforms & Contact Centre Software (CCaaS)
Microsoft Power Platform: Structured data flows and modernised pipelines using low-code tools.
Serco Telephony Campaign: Managed a £400k CCaaS (Contact Centre as a Service) project establishing an automated, programmatic dialler integrated with an Azure-deployed CRM tool.
Based on Senior Project Manager Mark Whitfield’s professional portal, his Capgemini Engagement Manager eLearning and Group Training history spans 100+ distinct training modules and courses.
When broken down and totalled by the specific business and delivery focus areas outlined on his Capgemini Professional Training Tracker, the modules are structured as follows:
📋 Corporate Policy & Compliance (Modules 1–4)
Total Duration: 135 Minutes (2 Hours 15 Minutes)
Key Modules: Intellectual Property Rights (IPR), Group Anti-Corruption, and Group Competition Laws.
🛡️ Cybersecurity Essentials (Modules 5–9)
Total Duration: 60 Minutes (1 Hour)
Key Modules: Five-part series spanning safe email/social media usage, identifying cyber-risks and engineering threats, workstation protection, data classification, and travel security.
🤝 Sales & Digital Engagement Innovation (Modules 10–13)
Total Duration: 65 Minutes (1 Hour 5 Minutes)
Key Modules: Innovative Selling for Digital EMs, Appraising Digital Opportunities, and navigating the Applied Innovation Exchange (AIE).
⚙️ Delivery Methods, Agile & Quality Systems (Modules 14–22)
Total Duration: 140 Minutes (2 Hours 20 Minutes) (Note: Module 20 “Bluebook” duration is unlisted/self-paced).
Key Modules: Agile Basics & Tools, Scaling Up Agile frameworks, UniQuE Quality Management System portal, Lean Foundation, and the Contract Clauses Negotiating Guide (CCNG).
🔄 Global Transition Methods & Enterprise Delivery (Modules 23–55)
Total Duration: 8.5 Days + 186 Minutes
Key Modules: End-to-end Transition Management methodologies (V4.1) covering finance, contracts, work-in-progress, and organizational change streams. It culminates in intensive classroom sessions for UK BU Project Financial Management and his formal Advanced Engagement Management (Level 2) qualification.
Mark Whitfield’s IT and Project Management training spans over three decades, tracking his progression from a senior technical developer into an enterprise-level, SC-cleared Senior IT Project Manager.
His official training records and professional certificates listed on PROject Templates are grouped below by specific skill areas.
Project Management Methodologies & Frameworks
PRINCE2 Practitioner: Registered Practitioner certification achieved via ILX (May 2011).
Agile SCRUM Framework: Dedicated training completed for Agile SCRUM delivery mechanics (May 2011).
Advanced Engagement Management: Level 2 Exam certification completed during his tenure at Capgemini (November 2017).
Project Management Fundamentals: Core foundational training in Successful Project Management (February 2000).
Multi-Project Administration: Training in Managing Multiple Projects, Objectives, and Deadlines (October 1999).
Capgemini, Engagement Manager – eLearning and Group Training, 100+ Training Modules, see link 1) at bottom of this post.
Cloud & Database Infrastructure
Microsoft Azure Fundamentals: Certified under the official AZ-900 cloud training track (February 2022).
Transact-SQL Database Administration: Course M2071 covering Querying Microsoft SQL Server 2000 (March 2009).
Software Engineering & Legacy Systems (HPE NonStop)
Web Application Engineering: Developing Microsoft ASP Web Applications utilizing the MS Visual Studio .NET ecosystem (January 2007).
C++ OOP Programming: Accelerated Object-Oriented development training via “C++ for Non-C Programmers” (March 1997).
Tandem/HPE NonStop Systems Architecture: High-level platform training covering the TANDEM Guardian Principles (May 1993).
Tandem Performance & TAL Programming: Advanced courses in TANDEM Performance Analysis & Tuning (June 1995) and TANDEM TAL Programming (December 1995).
VPS Architecture: Mainframe application architecture training under VPS 7000/9000 Series Application Development VOS 4.3 (September 1994).
Productivity & Project Control Tools
Microsoft Project Enterprise: Orange Belt certification in Managing a Single Project via Microsoft Office Project (May 2000).
Advanced Data Management: Microsoft Excel Expert Skills training (April 2017) followed by an Excel Refresher Certification via Udemy (July 2024).
Digital Content & Professional Design
Web Design Analytics: Training in Website Visibility and Promotion by Design (May 2009).
Digital Copywriting: Professional framework training in Writing for the Web (May 2009).
Desktop Publishing: Strategic training on designing attention-grabbing brochures, catalogues, ads, newsletters, and corporate reports (April 2006).
Mark maintains an unranked Top 30 Movies collection, alongside a broader list of favorite movie clips, which span the Golden Age of cinema to modern blockbusters.
His selected top favorites across different cinematic eras showcase a deep appreciation for classic epics, suspenseful westerns, war dramas, and high-octane modern sci-fi, some examples below:
Mark Whitfield is a UK-based, SC-cleared Senior IT Project Manager, Engagement Manager (Capgemini), and technology executive with over 35 years of hands-on and leadership experience across the Software Development Lifecycle (SDLC).
Mark Whitfield, High-Level Career Summary from 1990 thru 2026
Specialising in complex digital transformation, hybrid cloud migrations, and API-led system integrations, Mark graduated with an HND (Distinction) in Computing in 1990 and has delivered major enterprise solutions for clients such as Barclays Bank, Jaguar Land Rover (JLR), Royal Mail Group (RMG), Lloyds Banking Group, and the Bank of England. He is also the author of the PROject Templates resource platform, which provides project management toolkits.
The following comprehensive biography and career timeline breakdown details his professional trajectory by era.
Phase 1: Early Programming & Lead Analysis Era
Era Focus: Electronic banking software development, establishing foundational desktop access to company accounts.
Deluxe Data International, Wingate House, Northway, Runcorn
Main Focus Items: Core software design, coding, and back-end integration for electronic desktop banking.
Project Outputs: Software design, coding, and back-end integration for electronic desktop banking. Developed batch billing suite modules (NonStop SQL embedded COBOL85) to attach to the BBM II application, in Poole, Dorset (1993).
Milestones: Transitioned banking from purely paper-based to electronic systems. Made early remote banking a reality.
Methodology: Early iterative development & structured Waterfall lifecycles.
Highlights: Helped in the design and development of the Barclays Business Master II application while on-site in Knutsford, and later successfully developed and deployed a batch-billing suite for the bank in Poole, Dorset (1993).
Political Landscape: Early post-deregulation European banking markets. The Single European Act drove a need for cross-border electronic financial transparency and transaction systems.
Technology Landscape: Desktop PCs were novel; banking was driven by mainframe computing, specifically Tandem NonStop systems (now HPE NonStop).
Phase 2: Technical Consultancy & Product Management Era
Era Focus: Transitioning to product management, system and transaction monitoring, and SLA monitoring for critical-path financial hardware/ software.
Insider Technologies Limited, Salford Quays, Greater Manchester (UK)
Locations: Salford Quays, UK (head office); London, UK; International client sites
Clients included: Global Payments, Standard Chartered, Girofon, Rabobank, CRESTCo (Euroclear), Alrajhi Bank, LloydsTSB, HSBC, Santander, Bank of Ireland, Bank of Valletta (Malta) and both Commercial and Piraeus Bank (Greece)
Budget: Internal operational budgets and R&D capital expenditure
Main Focus Items: Infrastructure consulting, volume testing, system management & monitoring, and Service Level Agreement (SLA) monitoring for critical path payment applications. Attending related conferences, EBUG, ITUG, BITUG, SATUG
Project Outputs: Developed platform health and diagnostic modules for the Reflex monitoring product. Successfully delivered BASE24 ATM/ POS/ transaction Cross-border monitoring.
Milestones: Achieved the first HP OpenView Operations Enterprise Manager 2-way Smart Plug-In (SPI) certification for HPE NonStop in 2002.
Highlights:Consultant for CRESTCo in 1997, producing volume testing/benchmark software to test Stock Settlement applications on the newly introduced S7000 HPE NonStop systems.
Political Landscape: The late 1990s and 2000s saw the creation of the Eurozone, demanding high-capacity regional clearing and settlement networks that required robust transaction monitoring.
Technology Landscape: Market expansion of ATM and Point-of-Sale (POS) devices; ACI BASE24 Classic payments; move toward centralized, multi-platform GUI monitoring.
Also: Designer and author of a new company website using an Open Content Management framework identified as part of a Research phase. Authored a major technical summary published globally in the recognized HPE NonStop industry journal, The Connection, defining payment software lifecycles.
Phase 3: Professional Services Banking Delivery
Era Focus: IT Project Management and delivery of legacy migrations to primary UK high-street banks.
Project Outputs: Managed the Wincor Nixdorf workstream for Lloyds Banking Group’s Self-Service Software Replacement (SSSR) programme. Modernising legacy ATM software and directing hardware/ software transitions. Implementing ProClassic/Enterprise and PC/E SmartClient (Win 7) to replace the existing ProCash/NDC (Win XP) Stacks on a variety of multivendor devices.
Milestones: Transferred ATM driving responsibility away from BASE24 Classic on HPE NonStop to Wincor’s PC/E product on the AIX platform. Managed international rollout and off-shore resources.
IT Training: Agile, ITIL methodologies.
Methodology: Wincor project management methodology, with regard to planning, control, status reporting, documentation, quality, change control, risk analysis and management.
Highlights: Successfully upgraded LBG ATM hardware estate from Windows XP to Windows 7.
Political Landscape: Post-2008 financial crisis regulations brought stricter compliance and operational risk rules, accelerating the modernisation of core legacy banking systems to prevent service outages.
Technology Landscape: Transition from proprietary mainframe terminal driving to AIX, Oracle, and Windows-based banking environments.
Technology Areas: Multi-vendor hardware & software integration for ATMs.
Supplier Management: for external software suppliers like Degree53, Playtech, Onionsack, Intelligent Payments (Myriad), Inspired, iovation, StreamUK, Finsoft, Ineda, OtherLevels, Appsflyer, Income Access, Activewin, Virgo, Virtue Fusion, In Game Media, Satellite Information Services (SIS) and IGT
Budget: Managed multiple project budgets for Betfred apps, tracking via weekly effort burn rates
Programming Methodologies: Agile SCRUM in conjunction with Degree53
IT Products: iOS, Android, and Windows native apps, Football/ Horse Racing Sportsbook platforms
Main Focus Items: Taking new sports and virtual gaming components live, integrating payment gateways, managing app release cycles, and handling regulatory compliance.
Locations: Manchester (local office above), London, Birmingham, UK
Clients included: Jaguar Land Rover (JLR), Heathrow Airport, Royal Mail Group (RMG), National Air Traffic Services (NATS), UK Export Finance (UKEF), Welsh Water
Budget: Managed multi-million pound digital transformation and cloud refactoring contracts
Highlights: Maintained full SC Clearance. Authored and managed comprehensive Project Governance Plans (PGPs) to realize project targets, streamline margins, and successfully navigate complex off-shore delivery models.
Political Landscape: The government focus on “Digital by Default” for public services, coupled with significant public and corporate drives for green IT and cloud adoption to optimize operating costs.
Minutes of Meeting (MoM), or MOM, is the official written record of a project meeting, capturing critical discussions, decisions made, and assigned action items.
In project management, MOM serves as a single source of truth to hold team members accountable, track project requirements, and provide a legal paper trail to prevent disputes over scope, timeline, or budget.
Essential Elements of an Effective MOM
To be effective, your meeting minutes should always contain the following core components:
Meeting Overview: Project name, meeting title, date, time, and location (or virtual platform).
Attendees & Absentees: A clear list of who was present (and their roles) and who gave apologies for being unable to attend.
Agenda: The topics scheduled for discussion.
Key Discussion Points: A concise summary of what was debated and the context behind decisions.
Decisions Made: Clear, unambiguous notes on agreements, approvals, or rejections.
Action Items: The most critical section. Every task must include a description, the Person in Charge (PIC), and a Due Date.
Next Meeting: The date, time, and objective of the follow-up meeting.
Best Practices for Project Managers
Draft Immediately: Write or format your minutes within the first hour post-meeting while the discussions are still fresh.
Distribute for Sign-Off: Circulate the finalized document to all stakeholders to ensure everyone’s understanding matches and to allow for corrections.
Store Securely: Maintain a chronological, searchable digital repository for all project meetings.
Mark Whitfield is a UK-based, SC-cleared Senior IT Project Manager and Engagement Manager whose career spans over three decades of evolution within the software development lifecycle (SDLC) and project delivery areas.
Graduating with a Distinction level Higher National Diploma (HND) in Computing from the University of Bolton (formerly the Bolton Institute of Higher Education, BIHE), his professional journey documents a foundational shift from hands-on mainframe engineering to managing enterprise-scale cloud migrations and API-led integration ecosystems.
His professional transformation reflects broader shifts across four technological eras and political-economic landscapes:
1. Mainframe & Early Electronic Banking (1990–1995)
Technology Era: Dominated by localized infrastructure, Tandem Mainframe Computers (now HPE NonStop), COBOL, C, C++, TAL, PATHWAY, and Jackson Structured Programming (JSP).
Political & Economic Landscape: The aftermath of Thatcherite deregulation (the 1986 “Big Bang”) triggered intense competition in retail banking. Financial institutions aggressively adopted bespoke desktop and telephone banking applications to acquire market share.
Role & Projects: Working as a Programmer and Lead Analyst for The Software Partnership (acquired by Deluxe Data International in 1994), Whitfield engineered core software architectures like sp/ARCHITECT-BANK. He spent significant time on-site at Knutsford and Poole (Dorset) delivering the Barclays Business Master II (BBM II) platform, pushing desktop corporate banking into reality before the commercial internet matured.
2. Infrastructure Middleware & System Monitoring (1995–2013)
Technology Era: Shift toward web-enabled browser monitoring, middleware solutions, client-server architectures, and automated system diagnostics.
Political & Economic Landscape: The rise of New Labour, globalisation, and cross-border European integration. Financial sectors faced stricter service levels and skyrocketing volumes due to the growing ubiquity of ATMs, Point-of-Sale (POS) systems, and cross-border settlement demands.
Role & Projects: Joining Insider Technologies Limited (ITL) at Salford Quays (Manchester), Whitfield ascended from a Senior Programmer to an IT Project Manager overseeing strategic technical initiatives.
He co-developed system diagnostic modules for the Reflex platform.
He famously secured the first HP OpenView Operations Enterprise Manager 2-way Smart Plug-In (SPI) certification for HPE NonStop platforms.
Managing structured Waterfall frameworks, he led high-volume automated transaction deployments (notably BASE24 Classic and EPS) via the browser-enabled RTLX (Real-Time Log eXtraction) Reactor for heavyweights like HSBC, Alliance & Leicester, and Standard Chartered.
Technology Era: The definitive mass pivot from rigid Waterfall, PRINCE2 models toward Agile Scrum frameworks, mobile applications (iOS, Android), and multi-vendor hybrid software integration.
Political & Economic Landscape: Post-2008 financial crash regulatory overhauls paired with UK coalition government-driven austerity. High-street legacy architectures required rapid rationalization, while private entertainment industries (like consumer gambling) exploded due to mobile deregulation.
Role & Projects:
Wincor Nixdorf (2013–2014): Served as an award winning Agile IT PM modernizing legacy ATM networks and deploying multi-vendor software integrations (PC/E Enterprise, Oracle, Windows 7) for Lloyds Banking Group.
Betfred (2014–2016): Pivoted to the gambling sector as a Senior IT Project Manager. He spearheaded multiple complex Agile release cycles to take mobile sportsbook components, virtual gaming, and secure fraud-detection payment gateways live.
4. Enterprise Cloud, Security, & API Integration (2016–Present)
Technology Era: Modern hybrid cloud platforms (Azure, AWS), SaaS, MuleSoft Anypoint Platform, API-led connectivity, and microservices.
Political & Economic Landscape: The post-Brexit geopolitical landscape coupled with heightened national security frameworks. Public and private sectors faced mounting mandates for secure, interoperable architectures, requiring professionals to carry strict government Security Clearance (SC) credentials to manage critical infrastructure.
The MediaCityUK Photographic Build Timeline Journal is an extensive, long-term documentary project created by Mark Whitfield. It captures the transformation of Salford Quays from an empty dockland into a major UK media hub.
Working nearby as an IT Project Manager, Whitfield utilized his close proximity to the site to methodically photograph the construction lifecycle literally from the ground up.
MediaCityUK Photographic Build Timeline Journal is an extensive, long-term documentary project created by Mark Whitfield
Project Overview and Scope
Timeframe: The photographic project formally spans from May 2007 through 2010 for its core construction phase, with continuous updates extending into later developments.
Volume: The total project comprises a massive archive of over 15,000 to 16,000 photographs.
Curated Journal: An abridged timeline consisting of roughly 200 high-resolution selections was published to highlight key structural milestones chronologically.
Perspectives: Photos were captured weekly from multiple high-vantage reference points, including the Imperial War Museum North, the local Designer Outlet, and Broadway.
MediaCityUK BBC North, Salford Quays
Core Phases Documented
The Blank Canvas (Mid-2007): Captures the initial flat, unused grassland and docklands just before the first diggers arrived on site in June 2007.
The Structural Rise (2008–2009): Documents the erection of massive tower cranes and the core framework of the studio blocks rising over Salford Quays.
The Final Fit and Branding (2010–2011): Details the external completion of the main blocks, the installation of the iconic BBC North logos, the construction of the public piazza, and the implementation of the media tram stop.
Community and Media Discussions
Whitfield’s timeline served as a primary public and professional visual archive during the build. He actively managed a linked professional LinkedIn Group that grew to thousands of members. This space was widely used by industry professionals, media researchers, and regional planners to discuss ongoing jobs, architectural layouts, and local infrastructure impacts.
His updates were also featured directly on BBC corporate blogs to give incoming staff an authentic glimpse of their new northern headquarters.
Between 1988 and 1990, IT Project Manager Mark Whitfield completed a BTEC Higher National Diploma (HND) in Computer Studies at the Bolton Institute of Higher Education (BIHE). He graduated with a Distinction and achieved the overall first place across the entire two years of the course.
Bolton Institute of Higher Education now University of Greater Manchester
The institution has since evolved, later becoming the University of Bolton and subsequently rebranding as the University of Greater Manchester.
Mark Whitfield’s PM template library features over 200 editable project management and PMO templates. These templates span the entire project lifecycle and are categorized by focus area and framework (e.g., Agile, Waterfall, PRINCE2).
Many POaP templates to be tailored as required
The resources are formatted natively for the Microsoft Office suite, allowing them to be opened on all devices, including desktops, tablets, and smartphones.
The templates are divided into specific categories based on the standard project delivery phases:
📁 Core Template Categories
Planning & Execution:
Detailed MS Project schedules
Excel and PowerPoint Plan on a Page (POaP) examples (over 35 slide examples) to save time constructing from scratch
Financials: Project Financial Trackers for internal/external costs, forecasting vs. actuals, margin/variation, and expenses.
Agile Frameworks: Agile Story Dependency tracking, Burn Down & Burn Up charts, and Sprint tracking guides.
MS Excel XLS Agile Sprint Burn Down and Up Chart Examples
💻 File Formats
All templates are fully editable, and the package provides the following file formats for universal compatibility:
Microsoft Word (.docx): Used for walkthrough guides, governance documentation, and standard project status reports.
Microsoft Excel (.xlsx): Utilized for task trackers, financial dashboards, RAID logs, and non-MS Project Gantt charts.
Microsoft PowerPoint (.pptx): Used for Kick-Off decks, team hierarchy charts, and visual POaP (Plan on a Page) slides.
Microsoft Project (.mpp): Detailed work breakdown structure (WBS) and scheduling files for traditional and Agile-hybrid projects.
MS Project MPP file templates to be tailored as required
You can download or purchase the complete inventory of these editable files at the Mark Whitfield PROject Templates Store (or via the Etsy Storefront if you prefer that platform). Once purchased, you are also entitled to free lifetime upgrades and additions.
Project Management Templates to be tailored as required with FREE upgrades
Closing a project successfully requires more than just stopping work; it ensures deliverables are accepted, finances are reconciled, and knowledge is transferred for future success.
A comprehensive checklist includes: verifying and handing over all final deliverables, securing formal stakeholder sign-off, finalizing budgets and closing vendor contracts, releasing project resources, archiving all documentation, conducting a post-mortem or lessons learned review, and celebrating your team’s achievements.
Follow this structured, step-by-step closeout checklist to ensure no loose ends are left behind.
1. Deliverables & Acceptance
Verify Scope: Compare original project objectives and specifications to the final deliverables.
Quality Check: Conduct a final walkthrough to ensure all technical and operational requirements have been successfully met.
Client Handover: Transfer the final product, assets, or software over to the clients, end-users, or maintenance team.
Secure Sign-Off: Obtain formal, documented approval or a signature of acceptance from the project sponsor and key stakeholders to prevent future disputes.
2. Finance & Contract Closure
Budget Reconciliation: Compare final spending to your initial budget and document any variances.
Process Final Invoices: Ensure all outstanding payments, contractor fees, and expenses are cleared.
Close Vendor Contracts: Verify that all suppliers and subcontractors have met their contractual obligations, then formally close their contracts.
Close Cost Codes: Shut down active financial codes or billable accounts associated with the project.
3. Documentation & Archiving
Final Project Report: Compile a summary report of the project’s performance regarding scope, timeline, and budget.
Handover Documentation: Ensure the operational team receives all necessary manuals, standard operating procedures, and known-issues lists.
Organize and Archive: Consolidate all project files, risk logs, and communications into a secure, centralized company repository for future reference or audits.
Revoke Access: Remove project system access, revoke software licenses, and delete temporary shared accounts.
4. Team & Organization
Lessons Learned Session: Hold a post-mortem or retrospective meeting with your team to discuss what went well, what failed, and what can be improved for next time.
Update Knowledge Base: Document these insights so the broader organization can learn from the project.
Release Resources: Formally reassign team members to other projects or return them to their functional departments.
Celebrate: Take the time to recognize individual contributions and celebrate the completion of the project.
Microsoft Project—whose native file format extension is .mpp—is one of Microsoft’s longest-running products, originally originating from a DOS-based tool acquired in 1984. Over its four-decade lifespan, it has evolved from a basic critical path method (CPM) scheduler into a core enterprise project and portfolio management (PPM) system.
The .mpp format, which is the proprietary binary file structure used to store metadata, task hierarchies, schedules, and resource assignments, has undergone multiple structural changes to support new features like Agile workflows, critical path mapping, and multiple timelines. Buy MPP MS Project templates (like those above) here.
Chronological Timeline of Microsoft Project (1984 to Present)
1984 – 1986 (The DOS Era): The first commercial version, MS Project 1.0, was released for MS-DOS in 1984. It laid the foundation for Critical Path Method (CPM) scheduling.
1990 – 1993 (Transition to Windows/Mac): The first Windows version (Project 1.0 for Windows) launched in 1990. Microsoft subsequently released a Macintosh version in 1991, but officially ceased its Mac development by 1994.
1995 – 2003 (The Office Integration): With releases like Project 95, Project 98, and Project 2000, the software began to mirror Microsoft Office’s user interface, introducing PERT charts (later renamed Network Diagrams), multiple baselines, and resource pooling.
2007 – 2010 (The Ribbon and Server Era): Project 2010 became the first 64-bit version, introducing a modern ribbon and Backstage view. This era saw widespread use of Project Server for enterprise collaboration.
2013 – 2019 (Cloud & Modern UX): Integrating deeply with the Microsoft 365 environment, these versions introduced resource capacity heat maps, agile task fields, and native Plan-on-a-Page (POAP) timeline views.
2021 – 2024 (Modern Desktop Suite): The latest perpetual releases (Project 2021 and Project 2024) act as heavy-duty scheduling engines that integrate with modern tools like Power BI and Microsoft Teams.
Future Direction of the .MPP Format and Project Management
As of 2026, Microsoft is executing a major platform restructuring. The .mpp format will remain the standard file extension for the standalone, offline desktop application (e.g., Project Professional 2024/Subscription Edition), serving enterprise users who require complex scheduling, multi-project rollups, and deep resource optimization. Buy MPP MS Project templates here.
However, Microsoft is shifting its cloud and portfolio-level infrastructure entirely away from legacy SharePoint-based architectures. This structural shift impacts the .mpp ecosystem in several key ways:
Retirement of Project Online: Microsoft Project Online (the cloud-based service that previously stored and synchronized .mpp projects in the cloud) is officially fully retired.
Consolidation under Microsoft Planner: Microsoft’s cloud-based work management is converging entirely under the unified Microsoft Planner app (which incorporates former “Project for the web” capabilities).
Transition to Modern Cloud Formats: In the web and cloud ecosystem, the rigid and complex .mpp file is being replaced by Microsoft’s cloud-native architecture (which can be exported to standard .xml formats for interoperability).
Continued Desktop Support: Organizations requiring complex WBS (Work Breakdown Structure) views, complex dependencies, and local file storage can still utilize the desktop client versions (e.g., accessed via Microsoft Project Plan 3) which natively open .mpp files.
Viewer and Interoperability Utilities: Because native .mpp files cannot be opened by Microsoft Planner or Excel, Microsoft provides the XML Format Standard (MS-XDI) as the primary avenue for transferring custom scheduling data between desktop platforms and modern cloud APIs.
Microsoft Project MPP format, timeline & future direction
Mark Whitfield’s IT conference attendance timeline spans over three decades, highlighted by his presentations at international HPE NonStop (Tandem) and BASE24 transaction monitoring forums.
As a core developer, Product Manager, and Technical Project Manager at Insider Technologies Limited (ITL) from 1995 to 2013, he regularly showcased enterprise monitoring suites like Reflex and RTLX across Europe, the US, and South Africa.
The comprehensive, chronological timeline of his detailed IT conference attendance and speaking engagements is broken down below:
The Early Product Manager & Infrastructure Era (1995–1999)
Late 1990s (BITUG and EBUG): Following his transition to Product Manager for the Reflex 80:20 monitoring system, Whitfield began speaking at the British Isles Tandem User Group (BITUG) and the European BASE24 User Group (EBUG). He presented technical tracks regarding how Reflex managed complex Guardian operating system procedures and automated automated Y2K code auditing.
1999 (SATUG – South Africa): Whitfield traveled to South Africa to represent ITL at the South African Tandem User Group (SATUG) conference. He delivered presentations focused on real-time ATM/POS transaction monitoring and system infrastructure tracking ahead of the millennium date rollover.
Global Expansion & Peak Product Promotion (2000–2009)
Early 2000s (EBUG Expansion): As EBUG annual conferences grew in industry prestige, Whitfield frequently traveled across Europe to give technical track sessions. His presentations focused on BASE24 classic transaction logging, Point-of-Sale (POS) networks, and software resilience utilities.
2003 (ITUG – San Jose, USA): He attended and spoke at the high-profile International Tandem User Group (ITUG) conference in San Jose, California. He presented a specialized technical track detailing ITL’s strategic approaches to HP NonStop Enterprise Management integration.
2005 (BITUG SIG): Whitfield attended the BITUG Special Interest Group (SIG) event in the UK, engaging with regional banking stakeholders and system engineers to showcase platform diagnostics.
2007 (EBUG – Istanbul, Turkey): Whitfield managed the ITL corporate footprint and product presentations at the international EBUG meeting in Istanbul. This event highlighted the extraction capabilities of their next-generation RTLX tracking software.
2008 (SATUG – South Africa): He marked his second attendance at SATUG. He paired this international trip with presentations on high-availability monitoring for African financial networks.
2008 (EBUG – Vienna, Austria): At this pivotal European summit, Whitfield presented amid a massive industry transition. His sessions addressed real-time transaction tracking options as immediate payments emerged in Europe and ACI announced the retirement of legacy BASE24 Classic systems.
2009 (EBUG – Prague, Czech Republic): He attended the Prague conference to champion continued technical support, monitoring solutions, and software extensions for banking platforms still utilizing Tandem servers.
Miscellaneous European EBUG Presentations
Throughout his 18-year career at ITL, Whitfield also consistently attended and delivered product update presentations at EBUG chapters across other major European capital cities. These locations included:
Madrid, Spain
Lisbon, Portugal
Malta
Budapest, Hungary
Athens, Greece
Edinburgh, Scotland
Senior Leadership & Agile Training Era (2010–Present)
November 2017 (Capgemini Campus – Chantilly, France): Following a career shift toward cloud transformations, Digital Delivery, and enterprise architecture, Whitfield attended the intensive Advanced Engagement Manager (EM) Course at the Capgemini Campus (Serge Kampf Les Fontaines). This event focused on high-scale Agile Scrum project management frameworks rather than legacy hardware engineering.
The European BASE24 User Group (EBUG) was established in the 1980s as an independent, community-led organization for users of the BASE24 payment processing system developed by Applied Communications, Inc. (now ACI Worldwide).
Originally a regional forum for IT professionals in Europe to discuss HPE NonStop (Tandem) transaction monitoring and network security, the group expanded globally over time.
Insider Technologies regularly attended EBUG, booth in 2007 – RTLX now ETI-NET C-Deep
Following ACI’s withdrawal of direct corporate backing, EBUG evolved into “The Independent Group for All Payments System Users”—affectionately known as the Everybody Belongs User’s Group—welcoming users of multiple payment platforms like Postilion.
The detailed historical timeline of EBUG and the evolution of its core system, BASE24, outlines its development from a regional user collective to a global payments forum:
The Foundation Era (1975–1989)
1975: ACI is founded in Omaha, Nebraska, initially developing software for fault-tolerant Tandem NonStop computers to connect ATMs to bank networks.
1982: The BASE24 product family is officially launched globally, acting as “baseline” software for 24-hour financial operations.
1980s:EBUG is established as a regional European community for BASE24 users to collaborate on ATM networking and transaction processing.
Early 2000s: EBUG annual conferences grow in prestige, featuring technical tracks on BASE24 transaction logging, Point-of-Sale (POS) networks, and network resilience.
2007: EBUG hosts a high-profile international conference in Istanbul, Turkey.
2008: EBUG hosts its annual meeting in Vienna, Austria, which is historically noted as a pivotal year where ACI began supporting immediate payments in Europe and discussed a strategic shift toward IBM platforms. ACI officially announces the future retirement of “BASE24 Classic”.
2009: The conference is held in Prague, Czech Republic, maintaining strong community support for BASE24 on Tandem servers despite broader industry shifts.
Global Expansion, Rebranding & The Cloud Era (2010–Present)
2012: ACI introduces BASE24-eps, their next-generation, platform-independent payments engine designed to replace the legacy BASE24 on HPE NonStop. EBUG’s technical focus shifts to real-time payments and log extraction.
2013: With ACI ending direct involvement, the user group officially rebrands as the “Everybody Belongs User’s Group” at their conference in London, expanding attendance to professionals from Mexico, South Africa, and Australia.
2015: ACI celebrates 40 years in payments. EBUG solidifies its status as a supplier-agnostic payments forum, opening sessions to non-BASE24 users.
2020s: With BASE24 Classic retired, legacy users migrate to modern systems like BASE24-eps for cloud deployments and immediate payments.
Recent Years: ACI goes live as a pioneer in the Federal Reserve’s FedNow Service, building upon the decades-long transaction switching architecture first developed in the 1970s and 1980s.
European BASE24 User Group (EBUG) Timeline from Inception
Mark Whitfield is a UK-based, SC-cleared Senior IT Project Manager and Engagement Manager with over three decades of experience in software development lifecycle (SDLC) delivery.
Mark Whitfield, High-Level Career Summary from 1990 thru 2026
Over his career, he has transitioned from deep technical engineering on legacy systems (HPE NonStop formerly Tandem Computers) to enterprise-scale digital transformation, cloud migrations, and API-led integrations. He is also the author of a comprehensive online toolkit for project delivery frameworks.
Click the ‘Company Worked‘ links below for more detail as required.
Project Management Career Breakdown:
1. Early Engineering & Technical Analysis Era (1990–1995)
Geographical Location: Salford Quays, UK (office); London, UK; Client sites across Europe/ Middle East
Clientsinclude: Global Payments, Standard Chartered, Girofon, Rabobank, CRESTCo (Euroclear), Alrajhi Bank, LloydsTSB, HSBC, Santander, Bank of Ireland, Bank of Valletta (Malta) and both Commercial and Piraeus Bank (Greece)
Main Focus Items: Infrastructure consulting, volume testing, system management & monitoring, and Service Level Agreement (SLA) monitoring for critical path payment applications. Attending related conferences, EBUG, ITUG, BITUG, SATUG
Technology Areas: HPE NonStop monitoring, ATM/POS system & transaction monitoring and stock settlement.
Geographical Location: Woking / Bracknell / UK wide
Client: Lloyds Banking Group
Main Focus Items: Modernising legacy ATM software and directing hardware/software transitions. Implementing ProClassic/Enterprise and PC/E SmartClient (Win 7) to replace the existing ProCash/NDC (Win XP) Stacks on a variety of multivendor devices.
Technology Areas: Multi-vendor hardware & software integration for ATMs.
Geographical Location: Wigan / Greater Manchester, UK
Client: Betfred Online and Mobile
Supplier Management: for external software suppliers like Degree53, Playtech, Onionsack, Intelligent Payments (Myriad), Inspired, iovation, StreamUK, Finsoft, Ineda, OtherLevels, Appsflyer, Income Access, Activewin, Virgo, Virtue Fusion, In Game Media, Satellite Information Services (SIS) and IGT
Main Focus Items: Taking new sports and virtual gaming components live, integrating payment gateways, managing app release cycles, and handling regulatory compliance.
In addition to his consultancy work, Mark Whitfield actively publishes his extensive collection of Project Management Templates, which are actively utilized across the industry for RAID Logs, Agile Burndown Charts, and Plan on a Page (POaP) blueprints.
Requirements gathering is the foundational process of identifying, documenting, and managing what a project must achieve to deliver maximum business value. According to the Project Management Institute (PMI), nearly 70% of project failures are directly attributed to poor requirements collection, highlighting its role as the ultimate “scope anchor” for project managers.
Below is an overview of the core steps, techniques, classification categories, and tracking methods needed to establish an airtight requirement framework.
The 6-Step Requirements Gathering Process
Executing a structured lifecycle ensures that raw client requests are transformed into precise, measurable technical blueprints.
Identify and Analyze Stakeholders
Map out every individual invested in the project baseline.
Separate them into internal (executives, developers) and external entities (vendors, customers).
Utilize a stakeholder register to analyze their influence and prioritize conflicting needs early.
Establish Goals and Alignment
Define overarching high-level business milestones before hunting for product features.
Separate broad targets (goals) from specific deliverables or tasks (objectives).
Filter out scope proposals that fail to directly support these core goals.
Elicit Stakeholder Requirements
Conduct interactive discovery sessions tailored to user availability and project context.
Use direct one-on-one sessions for specific detail validation.
Use data gathering structures for broader user bases.
Document and Categorize
Translate conversational feedback into clear, unambiguous definitions.
Store information inside a centralized, accessible collaborative hub.
Record relevant project assumptions and hard technical boundaries.
Prioritize and Validate
Organize requests into strict low, mid, or high urgency classifications.
Apply prioritization frameworks like MoSCoW (Must-have, Should-have, Could-have, Won’t-have).
Conduct structured internal reviews to confirm value connection back to the business.
Baseline Sign-off and Change Control
Request formal verification from the main project sponsors.
Set a fixed baseline to prevent unauthorized project feature updates.
funnels all future adaptations through a strict change control system.
Core Categories of Requirements
To prevent scope gaps, information must be analyzed from a 360-degree technical and strategic perspective.
Business Requirements: Define the ultimate overarching problem or strategic objective the business needs to resolve.
Stakeholder Requirements: Capture the specific desires, expectations, and operational pain points of the end users.
Functional Requirements: Spell out exactly what the target solution must execute or how a user interacts with it.
Non-Functional Requirements: Specify system traits such as performance, data security parameters, and growth scalability.
Technical Requirements: Detail the internal IT setups, environments, and languages the project must operate inside.
Essential Gathering Techniques
Choosing the right collection methodology depends on the size of your audience and the technical complexity of the work.
Project Requirements Gathering Essentials
Scope Governance: The Traceability Matrix
Once requirements are baselined, they are tracked using a Requirements Traceability Matrix (RTM). This tool links every approved feature back to its source stakeholder and forward into production and testing.
Bi-Directional Tracking: Traces forward from need to test case, and backward from code to initial business authorization.
Eliminates Scope Creep: Ensures that development engineering teams only spend resources on validated features.
Prevents Orphaned Elements: Flags code built without initial business justification, or targets missing a test plan.