Category: methodologies

Agile Scrum Story Point Estimation Simplified

Scrum Story Point Estimation Simplified
Agile Scrum Story Point
Estimation Simplified

Definition of Done DoD vs Definition of Ready DoR in Agile Scrum

1. Definition of Done DoD vs Definition of Ready DoR in Agile Scrum
2. Definition of Done DoD vs Definition of Ready DoR in Agile Scrum
Definition of Done DoD vs Definition
of Ready DoR in Agile Scrum

Capgemini Projects Managed from 2016 thru 2025, Summary

Mark Whitfield is an SC-cleared Senior IT Project Manager and Engagement Manager at Capgemini UK (Custom Bespoke Solutions).

Mark Whitfield’s IT project management and software engineering career spans over three decades
Mark Whitfield – Senior IT
Project Manager – SC cleared

Joining in January 2016, he has orchestrated enterprise-scale cloud migrations, middleware application refactoring, and API-led integration architectures across public sector and tier-one corporate clients.

Capgemini UK, Floor 7, Venus Building, Trafford Quays, Manchester. M41 7HA
Capgemini UK, Floor 7, Venus Building,
Trafford Quays

Below is the complete portfolio overview and highly detailed chronological breakdown by year of his project delivery history at Capgemini.

Project Portfolio Overview

  • Role Title: Certified Engagement Manager / Delivery Manager (A8 Core Level)
  • Methodologies: Agile Scrum ceremonies, Waterfall frameworks, and hybrid delivery patterns
  • Core Competencies: Hybrid cloud migrations, API lifecycle architectures, cross-data centre integration, multi-supplier governance, and financial forecasting
  • Key Clients Served: UK Government, MuleSoft / Salesforce, Jaguar Land Rover, Royal Mail Group, NATS, and Welsh Water

Detailed Capgemini Projects Timeline Breakdown by Year:

2016 – 2017: Aerospace & Defence Integration & Postal Infrastructure

  • Aerospace & Defence Mobile Apps: Managed an Agile Scrum delivery stream for a UK-wide Air Traffic organisation (NATS). He supervised the development of dual-layered Apple iOS applications rendering real-time airspace positioning data, separating sensitive internal military maps from public views.
  • Salesforce Portal Deployment: Led the enterprise integration and deployment of a Salesforce-driven Single Customer View (SCV) portal platform for defence stakeholders.
  • Postal Services Migration (May 2016 – Oct 2016): Appointed as PM for an award-winning £4.3 million Data Centre Migration project for a major postal client (Royal Mail Group). He directed 90 Capgemini engineers to shift 1,100+ critical interfaces—migrating file transmissions written in UNIX shell scripts and upgrading 150 interfaces processing through IBM ESB to safe software versions right before peak seasonal trading lockouts.

2017 – 2018: Automotive Supply Chain Middleware

  • Jaguar Land Rover iFAB Project: Directed the complex 12-month iFAB Middleware Project architecture development scheme. This cross-functional framework connected globally dispersed manufacturing supply components.
  • Supplier Governance: Coordinated on-site daily standups alongside integration engineering leads to accurately synchronize multiple software suppliers handling distinct tiers of middleware, messaging queues, and front-end architectures.

2018 – 2019: Enterprise API Platform Delivery (MuleSoft)

  • MuleSoft HQ Augmentation (October 2018 – June 2019): Embedded directly into MuleSoft’s London headquarters (Salesforce Tower) as a Senior Delivery Manager.
MuleSoft's London office is located within the Salesforce Tower (formerly known as Heron Tower) at 110 Bishopsgate.
MuleSoft’s London office is located within the Salesforce Tower at 110 Bishopsgate.
  • Anypoint Platform Deployments: Guided multinational corporate clients through API-led connectivity lifecycles. This encompassed configuring Anypoint Code Builder structures, validating hyper-automation runtime layers, and ensuring architectural compliance against regulatory framework rules.
Anypoint Platform Deployments: Guided multinational corporate clients through API-led connectivity lifecycles.
Anypoint Platform is the leading enterprise platform for building APIs, integrations & application networks

2019 – 2021: Large-Scale Public Sector Cloud Migration

  • UK Government Hybrid Cloud Transformation: Commanded a massive modernization program migrating a highly complex estate of legacy code.
  • 130 Applications Transformed: Acted as the primary client escalation point to refactor, re-host, and re-platform 130 public-sector software applications into hybrid cloud environments. His responsibilities included aligning the massive multi-stack migration with strict GDPR protection directives and managing offshore project delivery targets.

2022: Utility Infrastructure & Cloud Upgrades

  • Water Utility EQS Cloud Shift: Dual-managed a £0.5 million technical contract moving an legacy document management environment (EQS) onto Microsoft Azure cloud structures via Enablon for Welsh Water and Scottish Water.
  • MS Dynamics 365 Evolution: Supervised a £0.4 million discovery and blueprint phase to move 12 legacy Microsoft Dynamics 2016 instances operating on outdated shared 8.2 infrastructure onto the unified Microsoft Dynamics 365 Online ecosystem. This involved authoring precise Statements of Work (SoW), custom exit strategies, and foundational Microsoft Project (MPP) tracking models.
  • Accolades: Won the prestigious Capgemini C&CA UK Communications & Engagement Award in December 2022 for outstanding delivery inside the Cloud & Custom Applications business unit.
C&CA UK's Communications & Engagement Award Winner 2022 - Cloud & Custom Applications - Capgemini UK
C&CA UK’s Communications & Engagement Award Winner 2022 – Cloud & Custom Applications – Capgemini UK

Verified Sourcing & Portfolio Links

Capgemini Projects Managed from 2016 thru 2025, Summary

Agile Scrum Story Points Matrix

Story Points Matrix Agile Scrum
Scrum Story Points Matrix
Agile Scrum Story Points Matrix

Agile, Scrum and SAFe – How the Principles Connect

Agile, Scrum and SAFe - How the Principles Connect
2. Agile, Scrum and SAFe - How the Principles Connect
Agile, Scrum and SAFe –
How the Principles Connect

Comparison Between Load and Capacity in Agile Scrum

In Scrum, capacity represents the total amount of available work time a team has for an upcoming sprint, while load is the actual amount of work the team pulls into that sprint.

1 Comparison Between Load and Capacity in Agile Scrum
2 Comparison Between Load and Capacity in Agile Scrum
Comparison Between Load
& Capacity in Scrum

Understanding Capacity

Capacity acts as your ceiling. It is a forward-looking calculation performed right before sprint planning. It accounts for the reality of the upcoming calendar cycle.

  • To find a team’s capacity, you multiply total working days by the number of team members.
  • You then subtract non-productive time like public holidays, planned vacation days, and standard company meetings.
  • Finally, you apply a focus factor (typically around 70% to 80%) to account for daily distractions and context switching.

Understanding Load

Load represents the weight of the commitments made by the developers. It is the cumulative volume of user stories and tasks that the team intends to deliver during the sprint.

  • Load is entirely determined by how the team estimates the product backlog items pulled into the sprint.
  • Unlike capacity (which is restricted by time), load can theoretically be pushed to any level, though overloading creates major delivery risks.

Balancing the Relationship

The ultimate goal of a Scrum Master is to help the team balance load against capacity to maintain a sustainable pace.

  • The Safe Zone: Best practices dictate keeping your load at 10% to 20% below your absolute capacity. This visual buffer creates room for unexpected blockers or minor illness.
  • The Danger Zone (Overcommitment): An exact match where load equals capacity is considered an anti-pattern in Agile frameworks. It strips the team of flexibility, spikes burnout, encourages poor-quality code, and almost always leads to missed sprint goals.

Comparison Between Load & Capacity in Agile Scrum

POAP Plan On a Page Example Templates for Download

Available for download here.

Plan on a page POaP example 1
POaP example 1
Plan on a page POaP example 2
POaP example 2
Plan on a page POaP example 3
POaP example 3
Plan on a page POaP example 4
POaP example 4
Plan on a page POaP example 5
POaP example 5
Plan on a page POaP example 6
POaP example 6
Plan on a page POaP example 7
POaP example 7

Many more examples available in download pack.

A Plan on a Page (POaP) is a concise, high-level visual summary of a project used to communicate timelines, milestones, and strategic objectives to stakeholders and executives. It condenses detailed data into an easy-to-digest, single-page format.

Core Components of a POaP

An effective POaP cuts out the noise of day-to-day task lists and focuses purely on headline information. It typically includes:

  • Project Overview: Title, project manager, and the overarching business objective.
  • Timeline & Milestones: A horizontal, time-phased bar chart mapping the project’s key phases.
  • Key Deliverables: 4 to 6 major outputs or goals required for success.
  • Risks & Dependencies: Critical blockers that require executive attention.

Why and When to Use It

  • Steering Committees: Ideal for Steering Committee meetings (Steerco) where executives need to see progress at a glance.
  • Stakeholder Alignment: Keeps teams focused on strategic vision rather than getting “lost in the weeds” of daily operations.
  • Client Updates: Acts as an excellent executive summary for clients without overwhelming them with micro-details

POAP Plan On a Page Example Templates for Download

Daily Scrum format and step-by-step walkthrough

The Daily Scrum is a strictly time-boxed 15-minute daily planning event designed for the developers of a Scrum team to inspect progress toward the Sprint Goal and adapt their plan for the next 24 hours. It is not a management status report; it is a collaborative alignment ritual owned completely by the people doing the execution work.

Daily Scrum is a strictly time-boxed 15-minute daily planning event
Daily Scrum is a strictly time-boxed
15-minute daily planning event

Here is a step-by-step walkthrough of how to run an effective Daily Scrum, including modern formats and common pitfalls.

📋 The Event Overview

  • Time-box: Strictly 15 minutes max.
  • When & Where: Held at the exact same time and place every working day to minimize complexity.
  • Primary Audience: Developers. The Scrum Master and Product Owner can attend, but they only participate if they are actively working on Sprint Backlog items.

🚶‍♂️ Step-by-Step Walkthrough

1. Kickoff & Goal Review (Minutes 0 – 2)

  • Start on time: Never wait for latecomers; starting promptly builds professional respect and consistency.
  • Anchor to the Goal: The facilitator opens the session by clearly showing or reading aloud the Sprint Goal. Every update that follows must tie back to this shared objective.

2. Execution & Synchronization (Minutes 2 – 12)

The team syncs on current progress. Depending on your team’s preference, select one of these common execution formats:

Format A: “Walking the Board” (Highly Recommended)

Instead of focusing on individual people, focus on the work items themselves.

  • Start from the rightmost column of your Sprint Board (closest to “Done”) and work backward.
  • The team discusses the highest-priority item currently in progress.
  • The individuals contributing to it answer: What will it take to pull this specific card over the finish line today?
  • Repeat this for subsequent active tickets until you run out of items in progress.

Format B: The Classic Three Questions

Each developer takes turns speaking, keeping their personal update to under 60 seconds. They answer:

  • What did I do yesterday that helped the team meet the Sprint Goal?
  • What will I do today to help the team meet the Sprint Goal?
  • Do I see any impediments that prevent me or the team from meeting the Sprint Goal?

3. Parking Lot Identification & Wrap-up (Minutes 12 – 15)

  • Spotlight Impediments: If someone mentions a blocker, note it down on a visible impediment tracker. Do not try to solve the problem right now.
  • Form the After-Meeting: Identify which specific team members need to stay behind to solve the blocker.
  • Adjourn on time: Release everyone else exactly at or before the 15-minute mark to let them protect their deep-focus work time.

⚠️ Common Pitfalls to Avoid

  • Turning it into a status report: If developers look at the Scrum Master or Product Owner while talking, they are reporting status. Ensure team members look at each other or the sprint board.
  • Falling into deep problem-solving: The Daily Scrum is for identifying issues, not fixing them. Use the “ELMO” technique (Enough, Let’s Move On) if conversations drift into technical design.
  • Rambling or multi-tasking: Keep updates brief and focus exclusively on the current sprint. For remote teams, keeping video cameras turned on enhances presence and keeps attention sharp.

Daily Scrum format and step-by-step walkthrough

1. Agile Scrum Explained Simply - what it is and how it actually works
1. Agile Scrum Explained Simply –
what it is and how it actually works
2. Agile Scrum Explained Simply - what it is and how it actually works
2. Agile Scrum Explained Simply –
what it is and how it actually works