Mark Whitfield, a Manchester-based Senior IT Project Manager, has completed extensive professional training throughout his career, focusing on project management methodologies, delivery software, and technical tools.
Core Project Management Methodologies :
PRINCE2 Practitioner: Certified as a registered PRINCE2 Practitioner in May 2011 via the ILX Group (Gold e-Learning).
Agile SCRUM Training: Attended in-house training with RADTAC in May 2011.
Advanced Engagement Management (Level 2): Completed at Capgemini in November 2017.
Project Management Fundamentals: Completed “Fundamentals of Successful Project Management” in February 2000 through Skillpath in Manchester.
Managing Multiple Projects: Attended “Managing Multiple Projects, Objectives and Deadlines” in October 1999/1998 via Skillpath.
Software & Cloud Platforms :
AZ-900 Microsoft Azure Fundamentals: Certified in February 2022.
Microsoft Project: Completed the Microsoft Project ’98 Certification Series in May 2000 through the IIL UK Education Centre in Reading.
Microsoft Excel Expert Skills: Upgraded skills via a 2017 Expert course and a July 2024 Udemy refresher.
Technical & Programming Courses :
Tandem / HP NonStop: Completed Tandem Guardian Principles (1993), Tandem Performance Analysis (1995), and Tandem TAL Programming (1995).
C / C++ Programming: Attended “C++ for Non-C Programmers” with Comtec Computer Training in March 1997.
Database Querying: Completed “Querying Microsoft SQL 2000 with Transact SQL” via QA Training in March 2009.
Web Applications: Attended “Developing MS ASP Web Applications using MS Visual Studio .NET” in January 2007.
Marketing & Communication Training :
Writing for the Web: Completed in May 2009 with gbdirect (iTrain Education in London).
Brochure & Document Design: Attended a SkillPath Seminar on designing marketing brochures and reports in April 2006.
A RAID log is a central project management tool used to track Risks, Assumptions, Issues, and Dependencies to ensure project success and stakeholder alignment. It is essential for complex projects, updated regularly to manage, monitor, and mitigate factors that could affect deliverables, typically maintained as a living spreadsheet or document.
Key Components of a RAID Log
Risks: Potential future problems identified and mitigated before they occur (e.g., “supplier may delay shipment”).
Actions: Specific tasks, action items, or decisions that need to be addressed, often used in agile projects.
Issues: Known, current problems that have already occurred and require immediate resolution.
Dependencies: Internal or external relationships that, if not managed, can cause delays, such as waiting on another team.
Benefits of Using a RAID Log
Proactive Planning: Allows teams to identify and prepare for potential issues early.
Centralized Information: Provides a single, updated document for tracking, improving communication with stakeholders.
Improved Decision-Making: Helps in making informed decisions by logging the impact of changes.
Audit Trail: Acts as a record for project meetings, reviews, and post-mortem analysis.
How to Implement a RAID Log
Start Early: Create the log during the project planning or initiation phase.
Update Frequently: Review and update the log consistently, at least after every team meeting or weekly.
Assign Owners: Ensure every risk and issue has a specific person responsible for it.
Use a Template: Use an Excel or project management software tool, tracking columns like description, owner, impact, and status.
While some teams use it primarily for risks and issues, the “A” and “D” can stand for Actions and Decisions, respectively, depending on the team’s needs.
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.