IT & Project Management training spans over three decades

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).

More training detail and certificates 1) and 2)

Jira plus Claude to Support Project Management Delivery

Jira + Claude to Support Project Management Delivery
Jira plus Claude to Support Project Management Delivery
Jira plus Claude to Support
Project Management Delivery

Project Management Templates to be tailored as required with FREE upgrades

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).

Project Management Templates to be tailored as required with FREE upgrades
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
    • SDLC (Software Development Life-cycle) plans
  • Tracking & Control:
    • Weekly and monthly Status Reports
    • Meeting Minutes
  • Governance & Team Management:
    • Project Organization charts
    • RACI trackers (Responsible, Accountable, Consulted, Informed)
    • Stakeholder Analysis (influence vs. impact)
    • Team onboarding kits and quizzes

📂 Specialized & Framework-Specific Templates

  • Risk & Issue Management: Comprehensive RAIDs log (Risk, Action, Issue, Opportunity, Lessons Learned, Dependencies) with built-in summary charts.
  • 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.
Project Management MS Excel XLS Agile Scrum Sprint Burn Down and Up Templates to be tailored as required with FREE upgrades
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.
Project Management MPP Project Templates to be tailored as required with FREE upgrades
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

Project Management Acronyms

Project Management Acronyms
Project Management Acronyms
Example Project Management Acronyms

Project Management, Budgeting vs Forecasting

Project Management, Budgeting vs Forecasting
Project Management Budgeting versus Forecasting
Project Management, Budgeting vs Forecasting

12 Pillars of Project Management

12 Pillars of Project Management
12 Pillars of Project Management
  • Stewardship: Act with integrity, care, trustworthiness, and strict compliance to responsibly manage assets, finance, and social impacts.
  • Team: Foster a highly collaborative, respectful, and trusting project team environment to optimize productivity and collective learning.
  • Stakeholders: Engage proactively and effectively with all impacted individuals or groups to advance value delivery and counter opposition.
  • Value: Maintain a continuous focus on outcomes and intended business benefits rather than tracking empty operational outputs.
  • Systems Thinking: Evaluate and respond dynamically to internal and external system interactions to recognize how different project parts interconnect.
  • Leadership: Demonstrate adaptable, ethical leadership behaviors across all team members, regardless of formal titles or authority status.
  • Tailoring: Adapt the management framework iteratively based on context, unique project objectives, scope, governance, and environmental constraints.
  • Quality: Embed rigorous evaluation and acceptance criteria directly into project processes and deliverables to satisfy required expectations.
  • Complexity: Continuously identify, evaluate, and navigate project complexities arising from erratic human behaviors, system interactions, or ambiguity.
  • Risk: Optimize response mechanisms to systematically mitigate negative threats while proactively capturing positive project opportunities.
  • Adaptability & Resilience: Build structural flexibility into plans to rapidly recover from sudden setbacks and accommodate shifting environments.
  • Change: Prepare and support stakeholders for the targeted future state to avoid change fatigue and successfully implement new behaviors.

Critical Path Method CPM in Project Management

Critical Path Method CPM in Project Management
Critical Path Method CPM in Project Management

The Critical Path Method (CPM) is a project management algorithm used to identify the longest sequence of dependent tasks required to complete a project. It establishes the shortest possible project duration and highlights the “critical” activities that cannot be delayed without extending the entire project’s deadline.

How the Critical Path Works

CPM relies on finding the path through your project’s workflow that takes the most time from start to finish.

  • Critical Activities: Tasks on the critical path have zero “float” (or slack), meaning any delay directly impacts the final delivery date.
  • Non-Critical Activities: Other task sequences may have buffer time, allowing them to be delayed without throwing off the main project timeline.

Steps to Calculate the Critical Path

  1. Identify Tasks: Break the project down into individual activities (often using a Work Breakdown Structure).
  2. Determine Dependencies: Map out which tasks must happen before others can begin.
  3. Estimate Durations: Assign a realistic time frame for completing each task.
  4. Draw a Network Diagram: Create a flowchart visually connecting tasks with arrows to illustrate the sequence.
  5. Analyze the Paths: Calculate the total duration for every possible sequence of tasks. The longest sequence is your critical path.

Key Terminology

  • Float (Slack): The amount of time a task can be delayed without causing a delay to subsequent tasks or the overall project.
  • Forward Pass: A calculation used to find the Earliest Start and Earliest Finish times for each task.
  • Backward Pass: A calculation used to find the Latest Start and Latest Finish times for each task before the project is delayed.

When and Why to Use It

Project managers use CPM during the planning phase to build realistic schedules and set clear baselines. It is highly beneficial for complex, predictable projects like construction or software rollouts, where many tasks rely on the completion of previous ones.

By knowing exactly which tasks control your timeline, you can prioritize resources, prevent bottlenecks, and use “fast-tracking” (doing tasks in parallel) if you need to compress a timeline.

To get started with building a timeline, you can map out your workflows using digital tools such as Asana’s Critical Path Guide, Wrike’s CPM Implementation, or Monday.com’s CPM Tutorial.

Types of Agile Delivery in Project Management

Types of Agile Delivery in Project Management
Types of Agile Delivery in Project Management

Agile delivery is an iterative approach to project management that focuses on delivering value early, frequently adapting to change, and maintaining continuous customer feedback. Rather than executing a project sequentially, teams break work into small increments to maximize flexibility and product quality.

The most common types and frameworks of agile delivery include the following structured methodologies:

1. Scrum

Scrum is the most widely used agile framework, characterized by highly structured, time-boxed iterations called Sprints (typically 1 to 4 weeks long).

  • Key Concept: Teams work toward a single, actionable goal during each sprint.
  • Key Roles: Product Owner (represents the customer), Scrum Master (removes obstacles and enforces the framework), and Developers.
  • Best For: Projects where requirements change frequently and close collaboration with clients is required.

2. Kanban

Kanban is a visual workflow management system that emphasizes continuous delivery and transparency without strict time-boxed iterations.

  • Key Concept: Work is tracked on a Kanban board divided into columns (e.g., “To Do,” “In Progress,” “Done”).
  • Key Roles: Self-organizing teams with a pull-based approach.
  • Best For: Operational workflows, support/maintenance teams, and organizations that need to limit “work in progress” (WIP) to prevent bottlenecks.

3. Lean Software Development

Adapted from Toyota’s lean manufacturing principles, Lean focuses on maximizing customer value while minimizing waste.

  • Key Concept: Focuses on “eliminating waste” (anything that doesn’t add value to the end user), amplifying learning, and delivering as fast as possible.
  • Best For: Optimizing overall organizational workflows and reducing overhead.

4. Extreme Programming (XP)

XP focuses heavily on technical excellence and software engineering practices to boost product quality and responsiveness.

  • Key Concept: Uses practices like pair programming, test-driven development (TDD), and continuous integration.
  • Best For: Development teams that need to release updates frequently while maintaining strict quality and low bug rates.

5. Feature-Driven Development (FDD)

FDD is a model-driven approach that is highly structured and focuses on building software in short, feature-by-feature iterations.

  • Key Concept: Work revolves around creating detailed software models and planning by specific features, which are built one by one.
  • Best For: Teams that prefer structured, step-by-step processes or environments with traditional hierarchical structures.

6. Scaled Agile Framework (SAFe)

SAFe is designed for larger enterprises that need to align cross-functional, multiple Agile teams toward a single business strategy.

  • Key Concept: Blends Lean, Agile, and DevOps principles to coordinate alignment, governance, and delivery across a massive scale.
  • Best For: Large organizations and complex projects requiring multiple teams to coordinate efforts.

For further implementation details, you can refer to comprehensive resources like the Atlassian Agile Project Management Guide or the ICAgile Types of Agile Methodology Overview.