Download MS Project + Office Templates | Quick start Agile PRINCE2 & Waterfall Delivery + FREE Upgrades / Additions - SALE Buy 200+ Project Templates
Agile is a project management philosophy, while Scrum is the structured, real-world framework used to put that philosophy into action. Think of Agile as a commitment to healthy living, and Scrum as the specific daily workout routine you follow to stay fit. Instead of planning a massive project from start to finish upfront, Scrum breaks the work down into small, manageable pieces delivered in short cycles.
The easiest way to understand Scrum is through the 3-5-3 Rule: 3 Roles, 5 Events, and 3 Artifacts.
👥 The 3 Roles
A standard Scrum team is small, cross-functional, and self-managing, meaning they have all the skills needed to complete the work without relying on outsiders.
📦 The 3 Artifacts
Artifacts are simply the tangible items or lists used to maintain transparency across the project.
📅 The 5 Events (Ceremonies)
Scrum operates in time-boxed blocks called Sprints, which usually last 1 to 4 weeks. Each Sprint includes four distinct meetings:
🏗️ Why Does Scrum Work?
Scrum relies entirely on Empiricism, meaning making decisions based on real-world evidence rather than guesswork. It stands firmly on three pillars:
Mark Whitfield is an SC-cleared Senior IT Project and Engagement Manager with over 30 years of experience. His career spans from early mainframe programming to leading multi-million-pound cloud migrations and digital transformations for major financial, utility, and government clients.
The chronological breakdown of his professional project portfolio, structured by his definitive career eras, is detailed below:
1. The Technical Era (1990–1995)
During this foundational era, Mark worked as a Programmer and Lead Analyst for The Software Partnership (acquired by Deluxe Data in 1994). He focused strictly on the development, optimization, and deployment of the sp/ARCHITECT-BANK electronic banking solution on Tandem Mainframe Computers.
2. The Infrastructure & Monitoring Era (1995–2014)
Mark transitioned into a Product and Project Manager role at Insider Technologies Limited (and later a brief stint at Wincor Nixdorf). His focus shifted heavily toward platform diagnostics, high-availability transaction monitoring, and financial hardware software integrations.
3. The Digital and Cloud Era (2014–Present)
This era highlights Mark’s leadership of large-scale Agile and Waterfall digital delivery frameworks, moving from corporate gambling technology to complex, high-budget UK public sector programs.
Project: Middleware & MuleSoft Anypoint Integrations
Project: Multi-App Cloud Migration Proof-of-Concept
Project: Document Management Cloud Transformation
Project: Enterprise Dynamics 365 Online Cloud Migration
Project: Fish Export Service (FES) to CHIP Inspection Portal
Centiun is a UK-based Microsoft AI Cloud Partner and IT consultancy specializing in digital transformation, cloud migration, and AI integration for public and private sector organizations.
They help businesses modernize operations, leverage low/no-code platforms, and transition legacy infrastructure to secure cloud environments.
Core Services
Target Industries
Centiun tailors their technology solutions to several specialized sectors, offering domain expertise in:
Why They Stand Out
Explore their complete list of solutions and case studies directly on the Centiun Official Website.
Agile project management is an iterative, adaptive approach that breaks projects down into small, manageable cycles called sprints or iterations. Instead of planning the entire project upfront, teams continuously deliver functional increments, gather immediate feedback, and adapt to changing requirements. It prioritizes team collaboration, customer involvement, and rapid value delivery over rigid documentation and sequential phases.
Comprehensive Timeline Breakdown by Era and Year
Era 1: The Foundational Seeds (1950s – 1980s)
Before “Agile” existed as a formal term, engineers and researchers laid the groundwork through lean manufacturing and early iterative computing.
Era 2: The “Lightweight” Revolt (1990s)
Driven by frustration over the high failure rates and slow delivery of Waterfall, software pioneers independently build faster, more flexible frameworks.
Era 3: The Manifesto Moment (2000 – 2001)
The pivotal pivot point where separate iterative movements unite into a single, cohesive global movement.
Era 4: Mainstream Adoption & Scaling (2002 – 2019)
Agile shifts from a rebellious IT trend into a standard corporate expectation, requiring frameworks that can scale across massive enterprises.
Era 5: Modern Continuous Agility (2020s – Present)
Agile transcends IT entirely, cementing its place as an overarching organizational strategy for business survival in an uncertain world.
Agile Projects Overview and Timeline by year
SAFe (Scaled Agile Framework) events are structured, time-boxed ceremonies designed to drive synchronization, alignment, and continuous improvement across different levels of an enterprise.
These events are primarily categorized into Team-level events (which mirror standard Scrum practices) and Agile Release Train (ART) level events (which orchestrate multiple teams working toward a shared goal).
The core events within Essential SAFe are broken down below by organizational layer.
👥 Agile Team-Level Events
These recurrent ceremonies occur inside a short timebox called an Iteration (typically lasting 2 weeks) and focus on local execution.
🚊 Agile Release Train (ART) Level Events
These higher-level events drive the Planning Interval (PI), an 8 to 12-week timebox where an entire “train” of 5–12 teams delivers cross-functional value.
Summary of Differences
For a quick comparison, you can look at how responsibilities scale across the framework:
Mark Whitfield is an SC-cleared Senior IT Project Manager with over 30 years of experience delivering high-availability financial, cloud, and digital transformation projects. Over his career, he has transitioned from deep technical engineering on HPE NonStop (Tandem) mainframe systems to leading major corporate and public sector Agile and Waterfall software rollouts.
A comprehensive, year-by-year timeline breakdown of his project history and clients since 1990 is outlined below.
💻 The Technical Era (1990–1995)
During this period, Whitfield worked as a Programmer and Lead Analyst for The Software Partnership (acquired by Deluxe Data in 1994). He focused on electronic banking software (sp/ARCHITECT-BANK) on Tandem Mainframe Computers.
🛡️ Monitoring & Infrastructure Era (1995–2013)
Whitfield joined Insider Technologies Limited (ITL) in Salford Quays, specializing in platform diagnostics, transaction monitoring, and financial logging systems for mission-critical infrastructure.
MultiBatch scheduling architectures and file monitors.RTLX and Sentra) to audit automated teller machine (ATM) logs.🏦 Senior Project Management & Retail Banking (2013–2016)
This timeframe marked a total transition into senior contract project management, dealing directly with multi-million-pound programs.
🌐 Enterprise Consulting & Cloud Transformations (2016–Present)
In January 2016, Whitfield joined global consultancy firm Capgemini as a Senior client-facing Engagement/Delivery Manager.
Completing a stakeholder list using process analysis involves tracing the end-to-end lifecycle of a process to identify every individual, team, or organization that interacts with, influences, or is impacted by it. This ensures no hidden users, bottlenecks, or approvers are missed.
A four-step approach will ensure your list is thorough and actionable:
1. Map the Process Flow
Create a step-by-step flowchart of the current or future process. Break it down into key phases: Inputs, Activities, Outputs, and Outcomes. This visual map acts as a blueprint to spot every touchpoint where someone is involved.
2. Identify Stakeholders at Each Touchpoint
Go through each phase of your process map and ask the following dependency questions to pinpoint roles:
3. Classify and Prioritize
Once your comprehensive list is built, categorize stakeholders using the Power/Interest Matrix. This helps allocate your engagement efforts efficiently:
4. Document and Review
Log all identified stakeholders in a Stakeholder Register. Key details to capture include:
Completing the Stakeholder List using Process Analysis
Wincor Nixdorf was a premier global provider of IT solutions, hardware, software, and services tailored for retail banks and the retail industry.
Headquartered in Paderborn, Germany, the company historically commanded roughly 35% of the global automated teller machine (ATM) market and stood as a dominant force in electronic point-of-sale (EPOS) systems.
Its operations focused deeply on business process optimisation, automated cash handling, and retail self-checkout systems. In 2016, Wincor Nixdorf merged with its US rival Diebold, Inc., creating the modern consolidated market leader, Diebold Nixdorf.
Detailed Historical Timeline
The history of Wincor Nixdorf spans several distinct strategic eras, tracing its evolution from a post-war calculator workshop into a modern global fintech titan.
Era 1: The Founding & Decentralised Computing (1952–1989)
This era was defined by entrepreneur Heinz Nixdorf, who pioneered small-to-medium business computing and electronic banking terminals across Europe.
Era 2: The Siemens Integration & Corporate Carve-Out (1990–1998)
During this stage, corporate giant Siemens rescued and absorbed the distressed business, later reorganizing its retail and banking assets into a specialized standalone vehicle.
Era 3: Private Equity Buyout & The Rise of Wincor Nixdorf (1999–2015)
This period marked the official birth of the independent “Wincor Nixdorf” brand, characterized by aggressive global expansion, software-driven solutions, and public market listing.
Era 4: The Diebold Nixdorf Consolidation (2016–Present)
This current era represents the unification of American and European ATM powerhouses to navigate shifting brick-and-mortar financial landscapes.
A Capgemini Engagement Manager is a senior-level, client-facing role responsible for end-to-end delivery of complex business and technology transformation programs. They bridge strategy and execution, acting as a trusted advisor to clients while maintaining operational and financial control over projects.
Key Responsibilities
Ideal Candidate Profile
Explore current vacancies and learn more about the EM community through the Capgemini Careers Portal or their specific Engagement Management Careers overview.
Capgemini Engagement Manager, from 2016.
Mark Whitfield, an SC cleared Senior Project Manager based in the Manchester area, has over 30 years of experience transitioning from a software engineer to an IT program leader.
His extensive technical and project management training spans methodologies, cloud infrastructure, and software applications.
A detailed breakdown of his training, certifications, and academic background includes:
Project Management Methodologies
Technical & Cloud Training
Formal Education
You can review his detailed credential breakdown on the PROject Templates Professional Training Page.
Mark Whitfield invested many years in the HPE NonStop field from 1990. The HPE NonStop architecture (originally Tandem Computers) is a legendary fault-tolerant system known for 100% continuous availability. The platform’s hardware and software execution evolved across six distinct eras and processor transitions:
1. The Tandem Founding Era (1976–1981)
2. The Cyclone & Early RISC Era (1981–1996)
3. The Himalaya/ServerNet Era (1997–2004)
4. The Integrity Itanium Era (2005–2013)
5. The NonStop X (x86-64) Era (2014–Present)
6. The Virtualized NonStop Era (Present)
While all three roles fall under the “Business Analyst” umbrella, they differ in their primary focus: Functional BAs translate business needs into user requirements, Technical BAs focus on system architecture and integration, and Product BAs drive the product’s market value and long-term strategy.
1. Functional BA (The ‘Business’ Translator)
The Functional BA acts as the primary bridge between business stakeholders and the IT delivery team. They focus on what the business needs to achieve and how users will interact with the system.
2. Technical BA (The ‘System’ Architect)
The Technical BA bridges the gap between the functional requirements and the software development team. They focus on how the system will be built, ensuring the proposed solution is technically feasible, scalable, and secure.
3. Product BA (The ‘Value’ Strategist)
The Product BA merges business analysis with product management principles. Rather than just fulfilling requested requirements, they focus on why a product or feature should be built, ensuring it aligns with overarching company goals and delivers tangible ROI.
The PMBOK Guide 8th Edition is an integrated, value-driven framework that bridges the high-level principles of the 7th edition with the practical, process-oriented structure of older editions. It reintroduces 40 non-prescriptive processes alongside six core principles and seven performance domains.
📚 The Structure: Two Books in One
Similar to its predecessors, the printed volume of the 8th Edition includes two integrated publications:
🟢 The 6 Core Principles
The 8th Edition streamlines the 12 principles from the 7th edition into six actionable pillars designed to guide professional behavior and mindset:
🔵 The 7 Performance Domains
These represent key areas of practice, serving as the technical “what” of your project:
🟠 The 40 Evolved Processes & Focus Areas
A highly praised update in the 8th edition is the return of process guidance. To offer structured “how-to” guidance without becoming rigid, the processes are grouped into five Focus Areas (replacing the traditional Process Groups):
Across these five focus areas, there are 40 non-prescriptive processes that detail the typical inputs, tools, techniques, and outputs (ITTOs). The guide includes explicit tailoring advice on how to adapt these processes for predictive, hybrid, and agile environments.
💡 Key Modern Additions
Reflecting over 48,000 global practitioner data points, the 8th Edition expands coverage into modern project environments:
📝 PMP Exam Note
If you are planning to take the PMP exam, make sure to check the official PMI PMP Certification Overview for the most up-to-date Exam Content Outline (ECO). The exam relies heavily on the ECO, and the 8th Edition guide serves as foundational reference material.
Another example;
Business Analysis (BA) across an example project—like building a custom mobile app—follows a dynamic, week-to-week lifecycle. It shifts focus from initial high-level strategy and stakeholder alignment to granular requirements, testing support, and post-launch evaluation.
Here is how a typical BA lifecycle breaks down across an example 8-week project timeline:
Week 1: Project Kickoff & Discovery
Week 2: Stakeholder Engagement & Elicitation
Week 3: Analysis & Requirements Definition
Week 4: Prioritization & Scope Management
Week 5: Backlog Refinement & Solution Design
Week 6: Development Support & Clarification
Week 7: Testing & Validation
Week 8: Deployment & Post-Implementation Review
PROject Templates 