Download Templates for Project Management | FREE Upgrades & Additions
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.
You can review or download the targeted, one-page CV for Mark Whitfield (Senior Project Manager specializing in HPE NonStop systems) via the Mark Whitfield CV PDF link.
Mark Whitfield, High-Level Project Management Summary
The high-level, scannable overview of his professional profile is outlined below:
Executive Profile
Role: IT Senior Project Manager / Delivery Lead
Background:30+ years of experience delivering highly complex technology, business transformation, and infrastructure projects.
Core Skills: Cloud migration (hybrid), legacy ATM software modernisation, Point of Sale (POS) implementations, and software development lifecycles (SDLC).
Methodologies: Agile, Waterfall, PRINCE2 Practitioner, and ITIL certified.
Core Expertise & Competencies
HP NonStop & Legacy Integration: Deep technical roots in Tandem Computers/ HPE NonStop development, TAL programming, and high-volume transaction environments.
Global Delivery: Managed large-scale IT and system monitoring rollouts across the UK and international markets (e.g., Saudi Arabia).
Stakeholder Management: Experienced in bridging the gap between highly technical development teams and high-level business stakeholders.
For direct access to his official templates, articles, and full professional journey, you can visit the PROject Templates Website.
Microsoft Power Platform is an enterprise-grade, low-code platform that allows organizations to build applications, automate workflows, analyze data, and create AI-powered virtual agents. It natively connects to Microsoft 365, Azure, and Dynamics 365, serving as a core pillar of modern digital transformation.
Microsoft Power Platform Overview
Core Pillars
Power Apps: A low-code development environment for building custom, cross-platform business applications (Canvas or Model-driven) without writing traditional code.
Power Automate: An automation service enabling the creation of workflows, API-based integrations, and Robotic Process Automation (RPA) for legacy systems.
Power BI: A business analytics service that provides interactive visualizations and business intelligence capabilities with an interface simple enough for end users to create their own reports and dashboards.
Power Pages: A secure, enterprise-grade low-code software-as-a-service (SaaS) platform for designing, configuring, and publishing external-facing websites.
Microsoft Copilot: AI-assisted generative capabilities natively built across the platform, allowing users to build apps, write flows, or generate reports using natural language.
Foundational Technologies
Dataverse: A secure, cloud-based data storage and management layer featuring a standardized common data model, allowing disparate Microsoft tools to seamlessly share information.
Connectors: Over 1,000 pre-built wrappers that facilitate communication between the Power Platform and external services (like Salesforce, SQL databases, or REST APIs).
Power Fx: A low-code, strongly-typed functional programming language based on Excel formulas that serves as the logic layer across the platform.
Technical Evolution by Year
The Power Platform did not launch overnight; it evolved through the gradual introduction of several standalone tools before Microsoft formally unified them under one umbrella.
2013–2015: The Origins of Data Analysis & Logic
2013: Power BI is initially released as an add-in for Microsoft Excel, allowing users to build pivot tables and light analytics.
2015: Power BI transitions into a standalone cloud service. Concurrently, Power Apps enters public preview, introducing the low-code app paradigm.
2016–2017: Workflow Automation
2016: Microsoft Flow (the predecessor to Power Automate) is launched to handle cloud-based workflow automation.
2017: Common Data Service (now Dataverse) is introduced to provide a standardized, secure data layer.
2018–2019: The “Power Platform” Unification
2018: Microsoft officially unifies Power BI, Power Apps, and Microsoft Flow under the official name “Microsoft Power Platform”, introducing the formal concept of a connected, low-code business ecosystem.
2019: The Common Data Service gets deeper integration across Dynamics 365 and Microsoft 365, accelerating citizen development across large enterprises.
2020: AI and Robotic Process Automation (RPA)
2020: Microsoft launches AI Builder, allowing users to integrate pre-trained AI models (like form processing and object detection) directly into their apps and workflows.
2020: Softomotive is acquired, bringing RPA (desktop flows) into Power Automate.
2021–2022: New Additions and Expanded Web Presence
2021: The Common Data Service is officially rebranded as Microsoft Dataverse.
2021: Power Fx is introduced as the standard, open-source low-code language.
2022: Power Apps Portals is rebranded and expanded into Power Pages, creating a dedicated, robust tool for building external-facing websites.
2023–2024: The Generative AI Wave
2023: Microsoft embeds generative AI across the suite through Copilot. Users begin building data tables, applications, and automation flows entirely through conversational prompts.
2024: Power Platform deepens its integration with Microsoft Fabric and brings further enterprise-grade management, data governance, and AI agent orchestration features directly into Dataverse.
2025–2026: Agentic Computing and Modern Controls
2025: Power Platform evolves beyond standard applications and automations into “agentic computing.” Makers can build autonomous, AI-driven data agents directly within Dataverse using the Python SDK.
2026: Power Apps rolls out massive updates to its interface, deploying responsive layouts and modern controls as default settings. Advanced lifecycle management and process-mining features cement the platform’s role in modern fusion development.
My Recent MS Power Platform Involvement :
UK Gov : Cloud Migration (Hybrid) – In 2020, working as a Senior Project Manager on a client sponsored Agile proof-of-concept (POC) project to move 3 Client elected Apps (with MS Access, Oracle and SQL 2008 DBs), to the Cloud (Microsoft Azure and Dynamics365 Power Platform). The migration to the cloud was based on 3 primary app patterns namely; re-host, re-platform and re-factor. This project spanned approximately 3 months and started in early February 2020 with a budget of £375k.
The project was a pre-cursor and effort indicator for the larger piece of migration work to move 130 client estate apps to the cloud. This is a very complex app estate with many touch points and different technology stacks.
As the Capgemini Senior PM, responsible for the project planning, control, organisation, stakeholder communication, aligning with current GDPR directives and status reporting against delivery of Capgemini services to the client. As the PM, also the first escalation point for the project team and the client.
December 2022 – C&CA UK’s Communications & Engagement Award Winner – Cloud & Custom Applications – Capgemini UK
Project Management Office (PMO) models dictate the structure, control level, and strategic focus of a PMO within an organization. The most common frameworks break down into three primary operational types, alongside broader structural and strategic classifications that define how governance is applied.
Project Management Office (PMO) models overview
1. Operational Models (By Control Level)
These models define how the PMO interacts with project teams and enforces standards.
Supportive PMO: Acts as an advisory entity. It provides templates, best practices, training, and tools on demand, but has no direct control or authority over project execution. Best for: Organizations with a decentralized, highly autonomous culture.
Controlling PMO: Enforces strict governance, standardizes methodologies, and ensures compliance across all initiatives. It provides more than advice and actively verifies adherence, but typically relies on established escalation paths rather than direct authority. Best for: Organizations that need consistency and reduced risk.
Directive PMO: Assumes full control and direct ownership of projects. The PMO assigns project managers, directs resources, and takes total responsibility for execution, timelines, and outcomes. Best for: Complex or mission-critical projects requiring rigid governance.
2. Structural Models (By Scope & Placement)
These classifications indicate where the PMO sits and its organizational reach.
Enterprise PMO (EPMO): Operates at the highest organizational level, overseeing the entire project portfolio. It ensures all programs directly align with overarching corporate business objectives and strategy.
Departmental/Divisional PMO: Supports specific business units (such as IT, Marketing, or Engineering). It is highly tailored to the specialized needs of that function, though it runs the risk of creating siloed practices.
Embedded or Project-Specific PMO: A temporary model dedicated to one large, highly complex, or mission-critical project or program. It lasts for the duration of the project and then disbands or reallocates.
3. Advanced / Strategic Models (By Focus)
Modern organizations often adapt the PMO to focus on high-level value rather than just tracking timelines.
Center of Excellence (CoE): Focuses heavily on continuously elevating the organization’s project management maturity. It acts as an innovation hub for methodologies, technology evaluation, and skill-building.
Value Management Office (VMO): Focuses entirely on benefits realization and return on investment (ROI). Rather than just asking “are we on time?”, it asks “is this project generating the business value we wanted?”
A Project Management Office (PMO) is a centralized department within an organization tasked with standardizing project management processes, enforcing governance, and aligning projects with strategic business goals. Its primary mission is to optimize resource utilization, mitigate risks across the portfolio, and improve the overall success rate of projects.
The core responsibilities of a PMO vary based on its organizational maturity and type (Supportive, Controlling, or Directive), but generally span five major domains:
1. Governance and Standardisation
Developing Methodologies: Establishing uniform frameworks, processes, and project management methodologies (such as Agile, Waterfall, or hybrid models) across all departments.
Creating Templates: Developing standard documentation, templates, and tools to ensure consistency in project initiation, tracking, and reporting.
Conducting Audits: Monitoring compliance with established standards through health checks and project reviews to identify and correct process deviations.
2. Strategic Portfolio Management
Strategic Alignment: Ensuring every project investment directly supports the organization’s high-level strategy and long-term business goals.
Project Prioritization: Evaluating incoming project proposals and business cases to prioritize high-value initiatives while deferring or canceling low-priority options.
Benefits Realization: Tracking and measuring project outcomes to ensure that completed deliverables provide the expected economic or structural value to the company.
3. Monitoring, Tracking, and Reporting
Performance Reporting: Collecting and analyzing performance metrics via dashboards to provide regular progress updates to senior executives and stakeholders.
Dependency Management: Tracking cross-project dependencies, scheduling overlaps, and potential bottlenecks to prevent organizational conflicts.
Risk Management: Identifying systemic risks and early-warning signs of failing projects to trigger timely interventions or escalation protocols.
4. Resource and Capacity Management
Resource Optimization: Coordinating the allocation and utilization of personnel, skill sets, and budgets across the entire project portfolio.
Capacity Planning: Assisting line managers with strategic capacity planning to identify talent gaps, prevent team burnout, and support hiring decisions.
Effort Estimation Support: Providing historical data and expert insights to help project teams produce accurate cost and time estimates.
5. Training and Knowledge Management
Mentorship and Coaching: Providing regular guidance, professional coaching, and continuous support to project managers and their delivery teams.
Skills Development: Organizing training sessions and educational paths on core project management practices, specialized software, and new industry standards.
Lessons Learned Repository: Maintaining a centralized repository of project documentation, historical metrics, and post-project reviews to drive continuous organizational learning.
Scrum velocity and burndown charts are essential agile metrics used to measure team capacity and track progress. Velocity measures the average story points completed over past sprints to forecast future capacity. Burndown charts visually represent the remaining work daily, highlighting if the team is on track to meet sprint goals.
Scrum Velocity
Definition: The amount of work (usually in story points or hours) a team completes in a single sprint.
Purpose: Helps forecast team capacity for future sprints and promotes sustainable pace.
Calculation: Sum of story points for all “Done” items at the end of a sprint.
Best Practice: Average velocity over 3–5 sprints provides a more accurate, stable forecast.
Burndown Chart
Definition: A graph showing the amount of work remaining versus time (days) in a sprint.
Components:
Ideal Work Line: A straight line showing the projected pace to complete work.
Actual Work Line: A line plotting daily completed work against the ideal line.
Purpose: Provides daily visibility into progress and detects risks early (e.g., if the line is above the ideal, the team is behind).
Types: Sprint Burndown (short term) vs. Release/Product Burndown (long term).
Key Differences
Velocity is a planning metric looking at historical performance.
Burndown is a monitoring tool looking at current progress.
Common Pitfalls
Velocity: Treating velocity as a productivity metric (it is a capacity planning metric) or comparing it between teams.
Burndown: Using “manual updates” rather than automated tools, leading to inaccurate data.
Both: Neglecting to refine user stories, which makes velocity unpredictable and burndowns inaccurate.
Business analyst deliverables are essential documentation and artifacts produced throughout a project to define business needs, bridge gaps between stakeholders and technical teams, and ensure solutions deliver value. Key deliverables include the Business Case, Stakeholder List, Requirement Packages (BRD/User Stories), Process Models, and Transition Requirements.
Core Business Analyst Deliverables by Phase:
Initiation/Discovery:
Business Case: Outlines the justification for the project, including cost-benefit analysis and ROI.
Problem Statement/Project Scope: Defines the “why” and boundaries of the project.
Stakeholder Map/Matrix: Identifies key stakeholders and their influence.
Planning:
Business Analysis Plan: Outlines the approach, tasks, and techniques to be used.
Communication Plan: Defines how stakeholders will receive updates.
Elicitation & Analysis:
Current State Assessment (As-Is): Documents how processes work today.
Future State Modeling (To-Be): Visualizes the desired future processes.
Gap Analysis: Details what needs to change to get from current to future state.
Business Requirements Document (BRD): A formal document detailing what the business needs to achieve.
Solution Definition (Design & Implementation):
Functional/Non-Functional Requirements (SRS): Technical details on how the system should act.
Use Cases/User Stories: Detailed scenarios of user interactions with the system.
Prototypes/Wireframes: Visual representations of user interfaces.
Product Backlog (Agile): A prioritized list of user stories.
Evaluation & Closure:
Acceptance Criteria & Test Cases: Defines the criteria for a completed feature.
Solution Assessment/Validation Report: Evaluates if the delivered solution met the needs.
Lessons Learned/Closing Report: Documents successes and improvements for future projects.
Key Takeaways:
Formal vs. Informal: Plan-driven (Waterfall) projects use heavy formal documentation (BRD, SRS), while change-driven (Agile) projects focus on lighter tools like user stories, Jira tickets, and prototypes.
Value-Driven: Deliverables exist to facilitate communication, align stakeholders, and ensure project success.
Note: The specific deliverables required are usually determined in the initial project planning stage.
PROject Templates 