Mark Whitfield’s Project Management templates are a comprehensive, editable suite of over 200 documents designed for Agile, Waterfall, and PRINCE2 methodologies, based on over 30 years of project delivery experience. Available through his website (click banner link above), Etsy, Flevy and Eloquens, these templates are designed to be used across the project lifecycle—from initiation to closure—and include lifetime free updates and additions.
Many POaP Plan On a Page examples
Full Overview of Mark Whitfield Template Bundle
The bundle, priced at around £38.00 (as of April 2026), provides tools for MS Excel, Word, PowerPoint, and MS Project (.mpp).
1. Planning & Scheduling
MS Project (MPP / MSP): Includes full PRINCE2 7th Edition, Agile Scrum, and SDLC (Software Development Life-cycle) plans.
Excel Detailed Plans: Includes Gantt chart tracking for users without MS Project.
Plan on a Page (POaP): Over 30 PowerPoint examples for executive summaries.
Example Plan On a Page POaP
2. PRINCE2 & Governance
Full set of over 200 documents including Project Initiation Document (PID), Business Case, Work Packages, Risk Management Strategy, and Configuration Item Records.
Reporting: Highlight reports, exception reports, and end-stage reports.
PRINCE2 Delivery Plan in MS Excel Example
3. Tracking & Risk Management
RAID Logs: Comprehensive trackers for Risks, Assumptions, Issues, and Dependencies (includes simple and detailed versions).
Finance Trackers: Simple and full project finance trackers (forecasting, actuals, variance, rate lookups).
SDLC: Detailed Software Development Life-cycle plans.
Deployment/Runbook: Execution and release planning documents.
Agile: Burn down and burn up charts.
Example Agile Scrum Burn Down Chart
Detailed Timeline by Project Life Cycle
Templates provide detailed MS Project (.mpp) and Excel schedules that map out the standard project life cycle over time. The plans include notes and color-coded tasks (black: standard task, blue: artifact creation, brown: decision/event, purple: artifact update).
Mark Whitfield is a highly experienced Senior IT Project Manager based in Manchester, UK, with over 31 years of experience in the IT industry specializing in both Agile and Waterfall methodologies. He holds SC clearance (valid until 2031) and has a strong technical background in banking and digital project delivery, including experience as a developer in software development lifecycles (SDLC).
Mark Whitfield is a highly experienced Senior IT Project Manager based in Manchester
Professional Biography
After graduating in Computing in 1990, Mark began his career as a programmer specializing in Electronic Banking software on Tandem Mainframe Computers (HPE NonStop). He spent five years coding in COBOL85 and NonStop SQL for banking clients before transitioning into project management.
Mark has operated as a Senior IT Project Manager for over two decades, delivering complex projects for major blue-chip clients, including Jaguar Landrover, Heathrow, Royal Mail Group, and various financial institutions. He currently provides project management templates based on his extensive experience via his website, PROject Templates.
Example POaP Plan On a Page templates by Mark Whitfield
Projects: Delivered Waterfall and Agile digital projects for automotive, local regional government (LRG), postal services, and aerospace & defence sectors.
C&CA UK’s Communications & Engagement Award Winner 2022
Betfred (Late 2014 – Jan 2016)
Role: Senior IT Project Manager.
Projects: Managed mobile and online gambling/casino projects, including payment gateways, sportsbook, and virtual gaming using Agile SCRUM.
Wincor Nixdorf (Sept 2013 – Late 2014)
Role: Agile IT PM, Professional Services – Banking Division.
Projects: Managed ATM software delivery (Wincor Nixdorf work stream >£5M) for Lloyds Banking Group/Halifax.
Mark Whitfield provides a variety of Plan On a Page (POaP) templates designed to simplify complex project schedules into a single, high-level visual. These templates are typically available through his official website as part of a larger project management toolkit that includes over 200 editable documents.
PowerPoint Plan On a Page (POaP) templates
Mark Whitfield’s POaP Template Formats
Whitfield’s templates are available across multiple platforms to suit different project needs:
PowerPoint POaP Templates
Includes over 35+ slide examples showing different ways to visualise a Software Development Life Cycle (SDLC) plan. These are ideal for client presentations where high-level detail is needed.
Excel POaP & Tracker Templates
Features Gantt views, resource costing grids, and Agile Sprint views. Some Excel versions allow you to align the POaP with resource availability and overall phase costs, useful for project bids.
MS Project (MPP) Templates
Detailed PRINCE2 and Waterfall templates that can be condensed into a “timeline” view to serve as a POaP. These are annotated for tasks like Agile Scrum ceremonies or specific PRINCE2 7th Edition stages.
Key Features of the POaP Templates
Adaptability: Templates are designed to be tailored for Waterfall (PRINCE2) or Agile (Scrum/Sprints) methodologies.
Integrated Tracking: Often bundled with RAID logs (Risk, Action, Issue, Dependency) and RACI trackers to provide a complete overview beyond just the schedule.
Visual Dashboards: Many versions include self-populating charts and summary dashboards for at-a-glance status reporting.
Availability: Templates can be purchased individually or as a bulk pack on Mark Whitfield’s Website or through platforms like Etsy and Eloquens.
A Service Delivery Manager (SDM) acts as the primary liaison between an organization and its clients, ensuring services are delivered efficiently, meeting contractual obligations (SLAs), and maintaining high client satisfaction. They oversee daily operations, manage client relationships, and drive continuous service improvements.
Key Responsibilities and Duties:
Client Relationship Management: Acting as the central point of contact for service-related issues, leading service review meetings, and ensuring client satisfaction.
SLA & Performance Monitoring: Monitoring key performance indicators (KPIs) and Service Level Agreements (SLAs) to ensure compliance with contractual obligations.
Operational Excellence: Implementing best practices, identifying areas for improvement, and managing continuous service improvement plans.
Incident Management: Managing escalated service issues, leading root cause analysis (RCA), and ensuring swift resolution to restore service.
Team Leadership: Providing guidance, mentoring, and support to technical or support teams to meet performance goals.
Financial Management: Overseeing budgets, managing service credits, and identifying opportunities for cost savings or added value.
Required Skills and Qualifications:
Experience: Proven track record in service delivery, customer success, or project management.
Framework Knowledge: Strong understanding of ITIL frameworks is often required.
Communication: Excellent verbal and written communication skills for building rapport with clients and stakeholders.
Analytical Thinking: Ability to analyze service performance data and make data-driven decisions.
Leadership: Strong leadership skills to drive improvements and resolve conflict.
Common Industries:
Information Technology (IT) & Managed Service Providers (MSPs)
A Project Management Office (PMO) is a centralized department or group that defines, maintains, and ensures project management standards across an organization. It serves as the “command center” that aligns project execution with broader business strategy to improve success rates and ROI.
Core PMO Models
The level of control a PMO exerts depends on its specific operational model:
Supportive PMO: Provides a consultative role by supplying templates, best practices, and training. It has low control, acting primarily as a project repository.
Controlling PMO: Enforces governance and requires compliance through specific frameworks and tools. It maintains a moderate degree of control.
Directive PMO: Directly manages projects by assigning project managers who report to the PMO. This model offers the highest degree of control and accountability.
Key Responsibilities
A PMO’s daily functions bridge the gap between high-level strategy and ground-level execution:
Common PMO Roles:
Common PMO Roles
Staffing varies by organization size, but typical roles include:
PMO Director/Manager: Oversees the entire office, ensuring processes are followed and goals are met.
PMO Analyst: Collects and analyzes project data to support decision-making and reporting.
Project/Portfolio Managers: Lead individual projects or entire portfolios to completion.
PMO Specialist: Focuses on implementing methodologies and providing expert advice on project management.
Organizational Levels
PMOs can operate at different tiers within a company:
Project PMO: Focused on a single, large-scale project.
Program/Department PMO: Oversees a group of related projects within a specific department (e.g., IT or Marketing).
Enterprise PMO (EPMO): Operates at the executive level, ensuring all projects across the entire organization align with strategic corporate goals.
Business Analysts and Artificial Intelligence AI, future
Artificial Intelligence (AI) is fundamentally shifting the role of the Business Analyst (BA) from a focus on routine data processing and documentation to more strategic, human-centric activities. While AI excels at identifying patterns and automating labor-intensive tasks, it currently lacks the contextual awareness and emotional intelligence required to manage complex stakeholder relationships.
Core AI Applications for Business Analysts
AI functions as a high-speed “copilot” that streamlines the traditional BA lifecycle.
Requirement Generation: AI can process meeting transcripts to draft an initial list of requirements, user stories, or a Business Requirements Document (BRD).
Data Analysis & Forecasting: Machine learning algorithms can identify subtle trends in large datasets and move analysis from descriptive (what happened) to predictive (what might happen).
Visual Modeling: Tools can now generate process flows, data models, and architecture diagrams from simple text descriptions, drastically reducing time spent on manual formatting.
Information Elicitation: Analysts can use AI to quickly extract key details from vast document repositories or prepare for stakeholder interviews by anticipating potential questions.
Skills That Remain Uniquely Human
As AI handles the “grunt work,” the most valuable BA skills are those that cannot be easily automated.
Strategic Thinking: Connecting big-picture organizational goals to specific technical solutions and defining the “why” behind an initiative.
Stakeholder Management: Navigating office politics, facilitating discussions to resolve disagreements, and building trust across teams.
Creative Problem Solving: Tackling ambiguous business challenges where there is no clear historical data for an AI to learn from.
Critical Evaluation: Fact-checking AI outputs to ensure they are accurate and free from “hallucinations” before they influence business decisions.
The Shift from “AI4BA” to “BA4AI”
A new perspective emerging in the field is that BAs shouldn’t just use AI, but should lead the organization’s AI adoption.
Guiding Implementation: BAs act as strategic enablers, ensuring that AI projects solve meaningful problems rather than just chasing technological trends.
Managing Risk: Analysts play a critical role in addressing ethical concerns, bias detection, and security risks associated with AI-driven systems.
Bridging the Gap: They serve as the essential link between technical AI teams and non-technical business leaders to ensure projects deliver tangible value.
Future Career Outlook
The consensus among industry experts is that AI will transform—rather than eliminate—the BA profession. The market for business analytics is projected to grow significantly through 2031. Analysts who successfully integrate AI into their workflow to enhance productivity are expected to replace those who do not.
PRINCE2 Agile combines the structured governance of PRINCE2 with the flexibility of agile methods (like Scrum and Kanban) to manage projects effectively. It focuses on maintaining control, transparency, and high-quality delivery while empowering teams, making it ideal for fast-paced environments.
Key Aspects of PRINCE2 Agile:
Structure + Flexibility: It provides the framework to guide projects, while allowing the use of agile techniques to build the product.
Key Focus Areas:
The Agilometer: Assesses the level of risk and agility in a project.
Requirements: Prioritized to ensure the most valuable features are delivered first.
Rich Communication: Emphasizes face-to-face interaction and team rooms.
Frequent Releases: Ensures regular delivery and feedback loops.
Tailored Governance: Allows projects to remain aligned with organizational goals while keeping the flexibility needed for innovation.
Compatibility: Works well with various agile methods including Scrum, Kanban, and Lean Startup.
Main Benefits:
Increased Flexibility: Enables faster adaptation to changes and new information.
Improved Quality: Focuses on delivering high-quality products that meet client needs.
Enhanced Control: Provides necessary governance for project success.
When to Use:
Projects requiring both structure and high responsiveness.
Teams using Agile techniques who need to satisfy governing bodies.
Situations demanding regular, iterative delivery of results.
PRINCE2 (PRojects IN Controlled Environments) is a structured, process-driven project management method used internationally to deliver projects within time, cost, and quality constraints. Originally developed for IT projects, it has evolved into a generic, flexible, and scalable framework applicable to any type of project, now owned by PeopleCert.
Detailed Overview of PRINCE2 (2026 Framework)
As of 2026, the current framework is PRINCE2 7th Edition, launched in late 2023. It is characterized by its focus on people, digital tools, and sustainability, while retaining its core focus on governance.
MS Project MPP template example
1. The Seven Principles (Why PRINCE2 is used)
Continued Business Justification: A project must have a valid business case.
Learn from Experience: Lessons are documented and used.
Defined Roles and Responsibilities: Clear organizational structure.
Manage by Stages: Projects are broken into manageable chunks.
Manage by Exception: Empowerment given to managers to act within tolerances.
Focus on Products: Focus on deliverables rather than activities.
Tailor to Suit the Project: Adapted to suit the project’s size, environment, and complexity.
2. The Seven Themes (What must be managed)
Business Case
Organization
Quality
Plans
Risk
Change
Progress
3. The Seven Processes (How to manage)
Starting up a Project
Directing a Project
Initiating a Project
Controlling a Stage
Managing Product Delivery
Managing a Stage Boundary
Closing a Project
4. Certification Levels
Foundation: Confirms basic knowledge of the methodology.
Practitioner: Tests the ability to apply and tailor the method to scenarios.
Detailed Timeline Evolution by Era and Year
PRINCE2 has evolved from a niche IT methodology to a global standard through three major revisions.
Era 1: The Foundations (1975–1989)
1975: Simpact Systems Ltd. creates the PROMPT (Project, Resource, Organization, Management, and Planning Technique) methodology.
Early 1980s: UK Central Computer and Telecommunications Agency (CCTA) licenses PROMPT.
1989: CCTA enhances PROMPT II, renaming it PRINCE (PROMPT in the CCTA Environment), mandated for UK IT projects.
Era 2: Launch and Public Adoption (1990–2005)
1990: PRINCE is released into the public domain.
1996:PRINCE2 is released by CCTA, designed for a broader range of projects (non-IT).
2000: Ownership transfers to the UK Office of Government Commerce (OGC).
2002/2005: Major revisions to the manual structure, strengthening the “product-based planning” approach.
Era 3: Modernization & Privatization (2009–2021)
2009: Major “Refresh” released, introducing the seven principles, themes, and processes. Focuses on simplicity and customizability.
2013: Ownership transfers to AXELOS Ltd, a joint venture between the UK Government and Capita.
2017:PRINCE2 2017 Update (6th Edition) is released, focusing on enhanced flexibility and tailoring guidance.
BRD vs FRD, Business Requirements vs Functional Requirements
The primary difference between a Business Requirement Document (BRD) and a Functional Requirement Document (FRD) is that the BRD focuses on “why” a project is needed (business objectives), while the FRD details “how” the system will work to meet those needs. The BRD serves stakeholders and leadership, whereas the FRD guides developers and technical teams.
Key Differences at a Glance:
BRD (Business Requirements Document):
Goal: Defines business objectives, goals, and high-level needs.
Key Content: Business problem, scope, ROI, high-level project goals.
FRD (Functional Requirements Document):
Goal: Translates business needs into detailed technical functionalities.
Focus: “How” the system will perform to meet requirements.
Audience: Developers, Testers, Technical Team, Business Analysts.
Key Content: Feature descriptions, user interactions, system workflows, data requirements, UI mockups.
How They Work Together: The BRD is created first to get approval for the project, while the FRD is developed based on the approved BRD. The FRD ensures the project is actionable, testable, and feasible. In Agile, these are often combined into smaller artifacts like User Stories.
Mark Whitfield is a highly experienced, SC-cleared Senior Project Manager and IT professional with over 31 years of experience in both public and private sectors, specializing in software development, cloud migration, and IT systems delivery.
He is currently associated with Capgemini (since 2016) and runs a project management resource website, PROject Templates.
Joined Capgemini in 2016 having worked at ascending points in software development lifecycle projects for over 31 years
Key Qualifications & Experience:
Roles: Senior Project Manager, Engagement Project Manager, Delivery Manager, and former programmer.
Methodologies: PRINCE2 Practitioner, skilled in both Waterfall and Agile (SCRUM) approaches.
Sector Experience: Extensive experience in finance and banking, including ATM software swap-outs, cloud migration (Azure, AWS, Power Platform), and POS monitoring systems.
Background: Graduated in Computing in 1990; worked as a developer (COBOL, SQL, Tandem / HPE NonStop) before transitioning to project management.
PRINCE2 Practitioner, skilled in both Waterfall and Agile (SCRUM) approaches
Professional Highlights:
Delivered major projects for clients such as Barclays, Bank of England, HSBC, Royal Mail Group, UK & Welsh Government, Heathrow, and Jaguar Land Rover.
Led complex IT infrastructure projects and business transformations.
Maintains mark-whitfield.com, offering over 200 project management templates, trackers (RAID, budget, benefit, cost etc.), and many plans for Agile / Waterfall projects including 30+ Plan On a Page (POaP) and MS Project MPP examples (click on Blog above for a summary).
Provides specialized templates for PRINCE2 7th edition and MS Project (MPP).
December 2022 – C&CA UK’s Communications & Engagement Award Winner – Cloud & Custom Applications – Capgemini UKNovember 2017 – Advanced Engagement Management Course – Level 2 ExamJune 1990 – Higher National Diploma in Computer Studies, Distinction
As of 2026, AI is transforming project management by automating scheduling, risk management, and reporting. The best AI courses for project managers (PMs) focus on practical application, generative AI, and AI governance.
Top AI Courses and Certifications for Project Managers
PMI Certified Professional in Managing AI (PMI-CPMAI) (PMI)
Summary: The premier certification for managing AI projects from start to finish, including data prep and model deployment.
Best For: Advanced specialists managing AI projects.
Prioritization in AgileScrum is the systematic process of ordering Product Backlog items to maximize value delivery. These techniques are generally categorized by their primary focus: customer satisfaction, business value and economics, or collaborative consensus.
Category 1: Customer-Centric Frameworks
These methods prioritize features based on how they impact the end-user’s experience and satisfaction.
Kano Model: Categorizes features into three main types: Basic Needs (expected essentials), Performance Features (linear satisfaction), and Excitement Needs (unexpected “delighters”).
User Story Mapping: Visualizes the entire user journey to identify the most critical paths and “skeletal” features needed for a Minimum Viable Product (MVP).
Opportunity Scoring: Uses customer research to find gaps where importance is high but current satisfaction is low, identifying high-potential opportunities.
Category 2: Economic & Quantitative Models
These data-driven techniques use formulas to balance value against implementation costs or risks.
Weighted Shortest Job First (WSJF): Prioritizes tasks by dividing the Cost of Delay (value, urgency, and risk reduction) by Job Size (effort). The goal is to deliver the most value in the shortest time.
RICE Scoring: Calculates a score based on Reach (number of users), Impact, Confidence (certainty in estimates), and Effort.
Cost of Delay (CoD): Measures the economic impact or potential revenue loss of not delivering a feature within a specific timeframe.
Category 3: Stakeholder & Team-Based Consensus
These collaborative methods are used to reach agreement among diverse stakeholders or team members.
MoSCoW Method: A qualitative technique that buckets items into Must-Have, Should-Have, Could-Have, and Won’t-Have for a specific release cycle.
100-Dollar Test: Participants are given a hypothetical $100 to “spend” on features, revealing what they value most through resource allocation.
Priority Poker: A gamified, collaborative approach where team members anonymously vote on an item’s priority level to remove bias and foster discussion.
Category 4: Structural & Visual Matrixes
These tools help teams visualize trade-offs, typically using 2×2 grids.
Value vs. Effort Matrix: Plots tasks on two axes to identify Quick Wins (high value, low effort) and Major Projects (high value, high effort) while avoiding “thankless tasks”.
Risk/Value Matrix: Balances potential business rewards against technical or project risks to decide which high-value but high-risk items to tackle early.
Stack Ranking: A “forced ranking” method where every item has a unique, linear position (1 to N), preventing the “everything is high priority” trap.