Mark Whitfield is a highly experienced SC-cleared Senior IT Project Manager and Engagement Manager with over 30 years of experience in the software development lifecycle (SDLC), specializing in Agile and Waterfall delivery for financial, automotive, and public sector clients. He has a strong background in HP NonStop (Tandem) systems and currently works for Capgemini.
Mark Whitfield, Senior IT PM and Project templates author
1990–1994: The Software Partnership (Runcorn): Programmer specializing in electronic banking software (sp/ARCHITECT-BANK) on Tandem Computers.
1994–1995: Deluxe Data (formerly TSP): Lead Analyst/Programmer, focusing on software investigation, design, coding, and on-site installation for clients like TSB, Bank of Scotland, and Rabobank.
Development & Technical Specialization (1995–2013)
1995–2013: Insider Technologies Limited: Spent 18 years progressing from Senior Development Engineer to Project Manager for Strategic Technical Initiatives.
Key Roles: Managed Reflex 80:20 and Reflex ONE24 product development, technical pre-sales, and consultancy. Developed diagnostic software for monitoring payment systems (BASE24).
Notable Project: Managed a bid to replace legacy ATM tools at LloydsTSB (5000 ATMs) with Reflex ONE24.
Banking & Digital Project Management (2013–2016)
2013–2014: Wincor Nixdorf: Project Manager in the Professional Services Banking Division, managing a £5m+ work stream for Lloyds Banking Group’s Self-Service Software Replacement (SSSR) programme.
2014–2016: Betfred: Senior Digital Project Manager for the Online and Mobile Division, delivering payment gateways and sportsbooks for iOS, Android, and Windows.
Senior Engagement Management (2016–Present)
2016–Present: Capgemini UK: Engagement Project Manager responsible for delivering both Waterfall and Agile digital projects.
2016 (Approx.): Assigned to a UK-wide Air Traffic organization (NATS) for Apple iOS app delivery.
2018–2019: MuleSoft (Secondment): Served as a Delivery Manager for the Anypoint Platform.
Current Focus: Cloud Migration (Hybrid) of 130 apps for UK Government.
Agile Management: “Mark provided an excellent barrier between us (developers) and a difficult client…ensuring that we followed the agile principles” — Callum Marriage (Developer).
MuleSoft/Capgemini Engagement: “Customers loved him. His was extremely detailed oriented and understood the often-complex needs…never became flustered in high pressure situations” — Delivery Manager, MuleSoft.
Betfred (2015): “I would highly recommend Mark for his ability to successfully multi-task under significant pressure… [he] produced a very comprehensive handover document” — IT Compliance Analyst, Betfred.
Capgemini/JLR Project: “Mark was able to do a good planning, with the correct resources, on time delivery and with good relationship between stakeholders” — Head of Integration Development.
Mark Whitfield’s website (mark-whitfield.com) serves as a professional portfolio and resource hub for his 30+ year career as a SC-cleared Senior IT Project Manager. It offers over 200 editable project management templates for Agile, Waterfall, and PRINCE2 methodologies, alongside career insights and project experience.
Website & Content Overview
Project Management Resources: The site, often known as PROject Templates, provides downloadable templates for planning, scheduling (Gantt charts), project initiation (PID), and project control.
Methodology Focus: Resources are tailored for PRINCE2 (including Agile Scrum), and Agile/Waterfall delivery methods.
Career Portfolio: Features his work history as a Senior IT Project Manager, including roles at Capgemini, Betfred, and various financial institutions.
Technical Specialization: Highlights expertise in HP NonStop systems, digital projects, and payment/transaction systems.
Professional Background: Mentions his experience with major clients such as Jaguar Landrover, Heathrow, Royal Mail, and various banks.
The site is designed for project managers looking for templates to speed up project documentation and for clients looking to review his career accomplishments.
Senior IT Project Manager & Project Templates author – Mark Whitfield
Templates sold on this website are designed for Microsoft Office (Excel, Word, PowerPoint) and MS Project (MPP) and are used for tracking and planning software development lifecycle (SDLC) projects.
Template Breakdown
The templates, often sold in a bundle, include over 200+ editable items aimed at project delivery. Key components include:
Project Planning (MS Project & Excel): Detailed Waterfall project planners with Gantt views, Agile Sprint plans, and Plan on a Page (POaP) examples.
RAID Logs (Risk, Action, Issue, Dependency): Comprehensive Excel trackers for managing risks, issues, assumptions, and dependencies.
Financial & Resource Management: Project finance trackers (forecasts, actuals, variance) and resource trackers for tracking team members and costs.
This is a detailed, comprehensive historical timeline of project management methodologies, tracing the evolution from ancient practices to modern adaptive frameworks.
I. Pre-Modern Era (Before 1900): Foundation of Task Coordination
2570 BC (Great Pyramid of Giza): Completion of the pyramids, demonstrating early project organization with managers for each of the four faces, planning, and logistics.
208 BC (Great Wall of China): Construction of the Great Wall, involving massive workforce organization divided into soldiers, citizens, and criminals.
1850s (Transcontinental Railroad): US railroad projects requiring large-scale resource and schedule management.
1896 (Harmonogram): Karol Adamiecki developed the harmonogram, a predecessor to the Gantt chart (published in 1931).
II. Early Modern Era (1910s–1950s): The Scientific Management Era
This era brought “scientific management” to project control, focusing on efficiency and visualization.
1910s (Gantt Chart): Henry Gantt developed the Gantt chart, a visual tool for scheduling tasks over time.
1911 (Scientific Management): Frederick Taylor published The Principles of Scientific Management, focusing on efficiency and time-saving.
1931–1936 (Hoover Dam): One of the first large-scale applications of Gantt charts for complex scheduling.
1942–1945 (Manhattan Project): Development of the atomic bomb, creating a need for rapid, complex planning and large-scale team coordination.
III. The “Golden Age” of Project Management (1950s–1960s): Formal Methodologies
This era introduced mathematical models for managing complex, interdependent tasks.
1956 (AACE Formed): The American Association of Cost Engineers (now AACE International) was formed, specializing in cost control and scheduling.
1957 (Critical Path Method – CPM): Developed by Dupont Corporation to manage chemical plant maintenance shutdowns.
1958 (Program Evaluation and Review Technique – PERT): Created by the US Navy Special Projects Office for the Polaris missile submarine project to manage task time and risk.
1962 (Work Breakdown Structure – WBS): The US Department of Defense mandated the use of WBS for large, complex projects.
1965 (IPMA Founded): The International Project Management Association (IPMA) was launched, the world’s first project management association.
1969 (PMI Founded): The Project Management Institute (PMI) was launched to promote the profession, later developing the PMP certification.
IV. The “Silver Age” (1970s–1980s): Systems and Controls
1970s (Waterfall Introduction): While used informally earlier, the Waterfall methodology was formalized for software development in the 1970s, emphasizing sequential phases.
1975 (PROMPTII): Simpact Systems Ltd created PROMPTII, a methodology to handle cost overruns in computer projects, which later formed the basis of PRINCE.
1975 (Mythical Man-Month): Fred Brooks published his seminal work on software engineering project management.
1978 (Toyota Production System): Lean production and Kanban techniques, used in manufacturing, began to influence project workflow.
1984 (Theory of Constraints – TOC): Dr. Eliyahu Goldratt published The Goal, introducing the Theory of Constraints for managing constraints (bottlenecks).
1986 (Scrum): Takeuchi and Nonaka defined Scrum as a project management style for fast-paced development.
1987 (PMBOK Guide): The Project Management Institute published the first Project Management Body of Knowledge (PMBOK) white paper.
1989 (PRINCE): The UK government launched PRojects IN Controlled Environments (PRINCE), the standard for information systems projects.
V. Rebirth and Modern Era (1990s–2000s): Agile and Adaptive Methods
1994 (CHAOS Report): The Standish Group published the first report documenting high IT project failure rates.
1995 (Scrum Formalization): Jeff Sutherland and Ken Schwaber formally defined the Scrum framework.
1996 (PRINCE2): PRINCE was updated to PRINCE2 to become a generic, more flexible methodology applicable to all project types.
1997 (Critical Chain Project Management – CCPM): Eliyahu Goldratt invented CCPM, based on the Theory of Constraints.
1998 (PMBOK Standard): The American National Standards Institute (ANSI) recognized PMBOK as a standard.
2001 (Agile Manifesto): 17 software developers met to publish the Manifesto for Agile Software Development, prioritizing collaboration and adaptability over rigid plans.
2007 (Kanban for Software): David Anderson adopted Kanban for software development, focusing on visualizing work and limiting work-in-progress.
VI. The Contemporary Era (2010s–Present): Hybrid, AI, and Speed
2012 (ISO 21500): The International Organization for Standardization published ISO 21500:2012, “Guidance on Project Management”.
2017 (PMBOK 6th Ed & PRINCE2 Update): PMI introduced Agile/adaptive practices into PMBOK, while AXELOS released a more flexible PRINCE2.
2018 (PRINCE2 Agile): PRINCE2 Agile was launched to combine the governance of PRINCE2 with the flexibility of Agile.
2021 (PMBOK 7th Ed): A major shift in PMI standards, moving from process-based to principle-based, focusing on project outcomes.
2020s–Present (AI/Hybrid): Rise of AI-driven project management, automated reporting, and hybrid methodologies combining Waterfall stability with Agile speed.
Project Management Methodologies, historical timeline by era and year
Mark Whitfield is a highly experienced IT Senior Project Manager and Engagement Manager based in Manchester, UK, specializing in Agile Scrum, PRINCE2, and Waterfall methodologies. He holds a degree in Computing (1990) and has extensive experience in IT hardware solutions, financial services, and Aerospace & Defence.
Here is a comprehensive summary of his profile, with links based on the provided search data:
Professional Profile
Name: Mark Whitfield
Role: IT Senior Project Manager / Engagement Manager (SC Cleared)
Mark Whitfield is a highly experienced IT Project Manager, Senior Developer, and SC-cleared consultant with over 30 years of experience, specializing in HP NonStop (Tandem) systems, banking software, and digital transformation projects. He is currently an Engagement Project Manager at Capgemini.
Career Overview
Specialism: HP NonStop (Tandem) mainframes, BASE24, transaction monitoring, Agile/Waterfall methodologies.
1990: Graduated in Computing and started as a Programmer for The Software Partnership in Runcorn, specializing in sp/ARCHITECT-BANK on Tandem Computers.
1990-1994: Developed banking code for TSB, Bank of Scotland, Rabobank, and Girofon (Denmark).
1992: Worked on the Barclays Business Master II (BBM II) project in Knutsford.
1994: Company taken over by Deluxe Data (later FIS).
2. Insider Technologies & Monitoring Era (1995–2013)
1995–2013: Joined Insider Technologies Ltd as a Senior Development Engineer and Project Manager.
1995-2004: Developed monitoring/diagnostic software (Reflex 80:20, Reflex ONE24) for HP NonStop payment systems.
1997: Worked on projects for CRESTCo.
Early 2000s: Focused on HP NonStop transaction/payment monitoring for ATM/POS devices using ACI’s XPNET.
2005-2013: Managed first HP OpenView Operations Smart Plug-In certification for NonStop; designed XPERT24.
2011: Certified as a PRINCE2 Practitioner.
3. Banking Transformation & Consultancy Era (2013–2016)
2013–2014: Wincor Nixdorf UK – Worked as a Project Manager in Professional Services for the Banking Division.
2013-2014: Assigned to Lloyds Banking Group (LBG) for the Self-Service Software Replacement (SSSR) program (ATM estate upgrade).
2014–2016: Joined Betfred as an IT Project Manager in the gambling/casinos industry, delivering mobile/online payment gateways (iOS, Android).
4. Digital Transformation & Capgemini Era (2016–Present)
2016: Joined Capgemini UK as a client-facing Engagement Manager.
2016-2017: Led digital projects for automotive, local government, and aerospace sectors.
2017: Obtained Microsoft Excel Expert skills and Advanced Engagement Management certifications.
2018–2019: Augmented into MuleSoft as a Delivery Manager for the Anypoint Platform.
2022: Completed Microsoft Azure Fundamentals (AZ-900) certification.
2023–2024: Assigned to a UK Government account for a cloud migration of 130+ applications and the Fish Export Service (FES) project.
Key Qualifications
PRINCE2 Practitioner & Agile Scrum
ITIL Certified
SC Cleared (UK Government)
Technical Skills: C, C++, MS SQL, COBOL, TAL, Java, ASP.NET, HP NonStop
Scrumban is a hybrid Agile project management framework that blends the structured planning and roles of Scrum with the continuous flow and visualization of Kanban. Originally designed as a transition method for teams moving from Scrum to Kanban, it has evolved into a popular, distinct approach for teams needing to manage unpredictable work (e.g., support, maintenance) while maintaining prioritized planning. It focuses on pull-based workflows, limiting Work-in-Progress (WIP), and continuous improvement.
Scrumban Summary
Best Used For: Teams needing more flexibility than Scrum (no rigid sprints) but more structure than Kanban (needs planning cycles).
Key Features: Visual board (Kanban), Work-in-Progress (WIP) limits, on-demand or iterative planning, and a pull-based workflow.
Differences from Parent Frameworks:
vs. Scrum: No set sprint length or rigid roles; work is pulled continuously rather than planned in batches.
vs. Kanban: Uses planning meetings and team retrospectives, whereas classic Kanban is purely continuous.
Detailed Historical Timeline of Scrumban
1. The Pre-Scrumban Era (Pre-2008)
1950s (Kanban Origin): Toyota develops Kanban to optimize manufacturing production processes, focusing on Just-in-Time (JIT) production.
1986 (Scrum Concept): Takeuchi and Nonaka introduce the “rugby” approach to product development in the Harvard Business Review, fostering flexible, team-based development.
1995 (Scrum Introduced): Ken Schwaber and Jeff Sutherland formalize the Scrum framework for software development.
2001 (Agile Manifesto): Release of the Agile Manifesto, establishing core agile principles.
2004 (Kanban in Software): David J. Anderson suggests applying Kanban practices to software development to improve workflow.
2000-2007 (Evolution): Microsoft teams begin experimenting with “feature crews” that mix structured planning with continuous delivery, planting the seeds for hybrid approaches.
2. Conception and Definition (2008–2010)
2008:Corey Ladas coins the term “Scrumban” and introduces the concept in his work, proposing it as a mechanism for teams to transition from Scrum to Kanban, or as a sustainable hybrid for maintaining focus while reducing iteration overhead.
2008: Ajay Reddy discusses the “Scrumban (R)evolution,” emphasizing that Scrumban is a distinct, powerful approach, not merely a blend.
2009: Ladas publishes “Scrumban: Essays on Kanban Systems for Lean Software Development,” providing the definitive framework for the approach.
3. Formalization and Adoption (2011–2019)
Early 2010s: The methodology gains popularity in specialized software areas, such as maintenance and support teams, where unpredictable bugs demand faster flexibility than two-week sprints.
2016: Ajay Reddy releases “The Scrumban [R]Evolution: Getting the Most Out of Agile, Scrum, and Lean Kanban,” providing practical guidelines for applying the methodology.
2018-2019: Adoption expands beyond software development into agile marketing and HR, looking for reduced bureaucracy.
4. Mature Hybrid & Continued Growth (2020s–Present)
2020s: Scrumban is recognized as a standard agile framework within major project management tools (e.g., Jira, Miro, Monday).
2025-2026: Further refinement as teams integrate AI-driven task management with visual Kanban workflows to increase throughput and automate WIP tracking.
Core Principles of Modern Scrumban (2026 Perspective)
Pull System: Work is pulled by team members when capacity allows, rather than pushed into the team.
Visual Board: All tasks are visualized to show bottlenecks.
WIP Limits: Restricting the number of active tasks at any stage to improve efficiency.
No Required Roles: Teams can keep Scrum roles (Product Owner, Scrum Master) or remove them, depending on their needs.
Adaptive Planning: Planning occurs on-demand or at short intervals, not just in strict timeboxed sprints.
Scrumban project management summary and detailed historical timeline by era and year
Scrum is an Agile framework for managing complex, innovative product development through small, cross-functional teams working iteratively in short time-boxes called Sprints. Inspired by a 1986 “rugby” approach to product development, it was formalized in the early 1990s by Jeff Sutherland and Ken Schwaber to improve team productivity and deliver value quickly.
Scrum is based on empiricism—transparency, inspection, and adaptation—and is defined by specific roles (Product Owner, Scrum Master, Developers), events (Sprint Planning, Daily Scrum, Sprint Review, Retrospective), and artifacts (Product Backlog, Sprint Backlog, Increment).
Detailed Historical Timeline
The Conceptual Era (Pre-1990s)
1986: Takeuchi and Nonaka publish “The New New Product Development Game” in Harvard Business Review. They introduce the “rugby” approach—a team working together, passing the ball back and forth, to increase speed and flexibility.
Scrum Takes Shape (1990–1999)
1993: First Scrum implementation: Jeff Sutherland, John Scumniotales, and Jeff McKenna at Easel Corporation apply these concepts to software development.
1995: Ken Schwaber and Jeff Sutherland present a paper, “The SCRUM Development Process,” at the Object-Oriented Programming, Systems, Languages & Applications (OOPSLA) conference in Austin, Texas, formally introducing the framework.
1996: Ken Schwaber and Mike Beedle refine the process, focusing on software development.
1999: Mike Beedle, Martine Devos, Yonat Sharon, Ken Schwaber, and Jeff Sutherland publish “SCRUM: An extension pattern language for hyperproductive software development”.
Agile and Formalization (2000–2009)
2001: Ken Schwaber, Jeff Sutherland, and 15 others create the “Agile Manifesto” in Snowbird, Utah. Schwaber and Beedle publish the first book on Scrum: Agile Software Development with Scrum.
2002: Ken Schwaber, Mike Cohn, and Esther Derby found the Scrum Alliance to provide certifications.
2004: Ken Schwaber publishes Agile Project Management with Scrum.
2006: Jeff Sutherland founds Scrum Inc..
2009: Ken Schwaber leaves the Scrum Alliance and founds Scrum.org to provide Professional Scrum accreditation.
The Scrum Guide Era (2010–Present)
2010: First “Scrum Guide” is published by Ken Schwaber and Jeff Sutherland to define the framework, often revised in subsequent years (2011, 2013, 2016, 2017).
2017: PRINCE2 Agile is published, adding governance layers for organizations using Scrum.
2020: The latest Scrum Guide (November 2020) is released, focusing on a more minimal, less prescriptive definition, introducing the “Product Goal” and changing “Development Team” to “Developers”.
Mark Whitfield provides a comprehensive suite of over 200 editable project management templates designed for both Agile and Waterfall delivery. These tools are built based on 21+ years of IT project delivery experience and are formatted for Microsoft Office (Excel, Word, PowerPoint) and Microsoft Project (MPP).
Core Planning & Tracking Templates
Detailed Project Plans: Comprehensive MPP and Excel files covering the full Software Development Life-cycle (SDLC), including Waterfall and Agile Scrum sprints.
Plan on a Page (POaP): High-level visual summaries in PowerPoint or Excel for client reporting and executive snapshots.
RAID Log: A central tracker for Risks, Actions, Issues, and Dependencies, often including tabs for Decisions, Opportunities, and Lessons Learned.
RACI Matrix: A tracker to define roles and responsibilities (Responsible, Accountable, Consulted, Informed).
Financial & Resource Management
Project Finance Tracker: Tools for managing project budgets, including forecasts vs. actuals, margin analysis, and variation tracking.
Resource Planning: Grid templates for costing project resources per phase and tracking team allocations.
Benefits Realisation: A spreadsheet to compare initial project goals against actual business outcomes and costs.
Reporting & Communication
Status Reports: Weekly and monthly templates in Word and PowerPoint that include milestone dashboards, project health indicators, and “next steps”.
Organisation Charts: Templates for visualising the project hierarchy and stakeholder contacts.
Agile Dashboards: Excel-based Burn Down and Burn Up charts for teams that do not have access to tools like Jira.
Methodology Support
PRINCE2 7th Edition: Specific MPP and Excel templates aligned with the latest PRINCE2 standards.
Agile Frameworks: Templates for Sprint Planning, Daily Stand-ups, and Sprint Retrospectives.
These templates are available for purchase on Mark Whitfield’s official site and typically include free lifetime upgrades.
Free Upgrade Project Management Templates Download by focus area
Mark Whitfield is a Senior, SC cleared IT Project and Engagement Manager with over 30 years of experience, specializing in the software development lifecycle (SDLC) for large-scale digital and financial payment systems.
Mark Whitfield is a Senior, SC cleared IT Project and Engagement Manager
Key Projects: Leading high-value digital transformations and cloud migrations for UK Government applications, automotive (Jaguar Land Rover), and aerospace (Air Traffic Management iOS apps).
2014–2016: Betfred Limited (UK)
Role: IT Senior Digital Project Manager, Online and Mobile Division.
Key Projects: Managed multiple Agile SCRUM projects for payment gateways, sportsbooks, and virtual gaming components across iOS, Android, and Windows platforms.
2013–2014: Wincor Nixdorf Limited (UK)
Role: Project Manager, Professional Services – Banking Division.
Key Projects: Managed a £5M+ workstream for Lloyds Banking Group’s Self-Service Software Replacement (SSSR) program, migrating legacy HP NonStop systems to AIX-based Oracle technologies.
Mark Whitfield’s project management (PM) template collection is a comprehensive professional toolkit containing over 200 editable templates. Designed for both Agile Scrum and PRINCE2/Waterfall delivery, the set is built on over 24 years of real-world experience and is available for purchase on his official website and Etsy.
Core Planning & Tracking Templates
Detailed Project Plans: Comprehensive Microsoft Project (MPP) and Excel plans mapped to the Software Development Life Cycle (SDLC).
Plan on a Page (POaP): High-level visual summaries for client presentations, provided in both Excel and PowerPoint.
RAID Log: A robust Excel tracker managing Risks, Assumptions, Issues, and Dependencies, often including tabs for Change Requests and Lessons Learned.
Financial Trackers: Detailed spreadsheets for tracking project forecasts, actuals, variance, and resource costing.
RACI Matrix: Essential for defining roles (Responsible, Accountable, Consulted, Informed) within the project team.
Methodology-Specific Artifacts
Agile Scrum: Includes burn-down and burn-up charts, sprint planning logs, and templates for daily stand-ups and retrospectives.
PRINCE2/Waterfall: Tailored plans for 7th Edition standards, including project mandates, transition plans, and close-out checklists.
Reporting & Documentation
Status Reports: Weekly and monthly templates in Word and PowerPoint to communicate project health to stakeholders.
Walkthrough Guides: The ZIP package includes Microsoft Word documents explaining how to use and customise each major template.
This is a Project Management Group Café for PM students, graduates and professionals looking to either locate, discuss or contribute ideas for PM templates for; Agile, Scrum, Kanban, PRINCE2 Waterfall projects, e.g. Plan on a Page (POaP), RACI, MPP, RAID logs, finance trackers, status reports, org charts etc. etc.
A gallery and inventory of screenshots for the Project Management Templates (both Agile and PRINCE2 waterfall projects) that are all available to be purchased as a bundle from this website link (note: upgrades to the latest template package after purchase, are totally FREE).
PM templates include MS Project MPP and MS Excel detailed plans including PRINCE2 and Agile delivery, Gantt Plan on a Page examples (POaP), finance trackers, status reports, RAID logs (Risk, Issue, Assumption, Dependency log), RACI tracker (Responsible, Accountable, Consulted, Informed), agile burn down chart and burn up chart, resource tracker, benefits realization plan etc. etc.
PRINCE2 and Agile Project Management Templates Galleryexamples
MPP Microsoft Project Plan ExamplesAgile Scrum Burn Down (and Up) Chart in Microsoft ExcelExample Microsoft Excel Spreadsheet Examples for Project Planning