← All Certifications PMI & ITIL

PMI & ITIL Certification Prep

Domain guides, practice questions, and exam strategies for PMI credentials (PMP, PMI-ACP, PMI-RMP) and ITIL 4 (Foundation, Specialist, Strategist). Built for project managers, IT service managers, and governance professionals.

Use the selector below to pick a certification and choose how you want to study — guides, practice exams, games, or curated resources.

180 questions · 4 hours · experience required

PMP — Project Management Professional

The globally recognised standard for project management excellence. PMP is issued by the Project Management Institute (PMI) and is consistently ranked among the highest-earning certifications in IT and business. As of January 2021, the exam uses the Examination Content Outline (ECO) 2021, which balances predictive (waterfall), agile, and hybrid delivery approaches — approximately 50% of questions involve agile or hybrid methodologies. Requires 36 months (with a four-year degree) or 60 months (without) of project management experience, plus 35 contact hours of PM education.

Domain 1 · 42%

People

The largest domain — managing and leading project teams. Covers: building high-performing teams (Tuckman model: forming, storming, norming, performing, adjourning), conflict resolution techniques (collaborating, compromising, forcing, smoothing, withdrawing, avoiding), servant leadership vs authoritative leadership, emotional intelligence and situational leadership, stakeholder engagement and communication planning, virtual and distributed team management, diversity and inclusion in teams, and negotiation techniques. The ECO 2021 heavily emphasises servant leadership — the PM empowers the team rather than directing it.

Domain 2 · 50%

Process

The core PM methodology domain and the highest-weight. Covers: project initiation (business case, project charter, stakeholder register), scope management (requirements traceability matrix, WBS, scope creep vs gold-plating), schedule management (CPM, critical path, float/slack, network diagrams, PERT, resource levelling, crashing vs fast-tracking), cost management (earned value management: CV, SV, CPI, SPI, EAC, BAC, TCPI), quality management (cost of quality, quality audit vs quality control, Kaizen), procurement (contract types: FFP, FPIF, T&M, CPFF, CPPC), and risk management (risk register, qualitative vs quantitative analysis, Monte Carlo simulation, EMV, risk response strategies). Agile ceremonies: sprint planning, daily standup, sprint review, retrospective, backlog grooming.

Domain 3 · 8%

Business Environment

Connecting project work to organisational strategy and external environment. Covers: benefits realisation management, project selection methods (NPV, IRR, payback period, BCR), organisational structures (functional, matrix, projectised, composite), Enterprise Environmental Factors (EEF) vs Organisational Process Assets (OPA), compliance with laws and regulations, project governance frameworks, and supporting organisational change management. Smallest domain but tests conceptual understanding — know NPV calculation and when to select one project over another.

PMP exam mindset — predictive vs agile

The ECO 2021 exam tests your ability to select the RIGHT approach for the scenario context. Key heuristics:

PMP experience requirement — what counts

PMI requires verifiable, non-overlapping project management experience. "Leading projects" means having responsibility for decisions — not just participating as a team member. Applicants document 5 experience examples aligned to the three domains using PMI's online application system (free account required). PMI audits approximately 20% of applications — keep documentation evidence for 18 months.

120 questions · 3 hours

PMI-ACP — Agile Certified Practitioner

PMI's practitioner-level credential for agile methodologies — Scrum, Kanban, Lean, XP, SAFe, and hybrid approaches. The PMI-ACP demonstrates hands-on agile experience beyond the foundational theory. Requires 21 contact hours of agile training, 12 months of general project experience, and 8 months of agile project experience. The PMI-ACP distinguishes generalist PMs from practitioners who have actually run sprints.

Domain 1

Agile Principles and Mindset

The Agile Manifesto (4 values, 12 principles) and why they exist. The shift from output-focused to outcome-focused delivery. Empiricism: transparency, inspection, adaptation. Incremental vs iterative development. Agile mindset vs agile practices — teams can follow ceremonies without the mindset. When agile is appropriate vs when it is not (stable regulated environments).

Domain 2

Value-Driven Delivery

Prioritisation techniques: MoSCoW (Must, Should, Could, Won't), weighted shortest job first (WSJF), Kano model (basic, performance, delight features). Minimum Viable Product (MVP) and Minimum Marketable Feature (MMF). Timeboxing and delivering working product at each iteration. Agile metrics: velocity, burndown/burnup charts, cumulative flow diagrams, cycle time.

Domain 3

Stakeholder Engagement

Building a collaborative team culture. Product Owner role (owns the backlog, represents the customer). Customer collaboration over contract negotiation. Active stakeholder participation in reviews and demos. Managing stakeholder expectations in a continuous-delivery model. Wireframes, story mapping, and lightweight documentation that supports stakeholder understanding.

Domain 4

Team Performance

Self-organising and cross-functional teams. Osmotic communication and co-location benefits. Velocity tracking and sustainable pace (avoiding hero culture). Team norms and working agreements. Retrospectives as the engine of continuous improvement — remember the four retrospective questions: What went well? What didn't go well? What puzzles us? What do we commit to changing? Servant leadership, Scrum Master role vs manager role.

Domain 5

Adaptive Planning

Progressive elaboration of project scope and plan. Rolling wave planning vs detailed upfront planning. Release planning vs iteration planning vs daily planning. Velocity-based forecasting (when will backlog be done?). Cone of uncertainty — estimates improve as work progresses. Risk-adjusted backlog: identify and reduce technical risk early by prioritising risky items first.

Domain 6

Problem Detection and Resolution

Impediment tracking and removal (Scrum Master's primary job). Information radiators: task boards, burndown charts, risk boards — visible and accessible to all. Definition of Done vs Definition of Ready. Escaped defects metric. Technical debt management. Root cause analysis: 5 Whys, fishbone/Ishikawa diagram, pareto analysis for defect types.

Domain 7

Continuous Improvement

Kaizen philosophy — continuous small improvements rather than large periodic transformation. Process tailoring: choosing and adapting agile practices for context. Communities of Practice (CoP) within Agile at Scale (SAFe, LeSS, Nexus). Inspect and adapt events at programme and portfolio level. Knowledge sharing and cross-team learning. Building quality in vs inspecting quality out.

115 questions · 2.5 hours

PMI-RMP — Risk Management Professional

The specialist credential for risk identification, assessment, and response. PMI-RMP validates advanced risk management skills beyond what PMP covers. Valuable for large programme managers, PMO leads, and consultants managing complex risk landscapes. Requires 30 hours of risk management education and 3,000+ hours of risk management experience (with a degree) or 4,500 hours (without).

Domain 1

Risk Strategy and Planning

Establishing the risk management approach. Risk management plan components: risk categories (RBS — Risk Breakdown Structure), probability and impact scales, risk thresholds, reporting format, and timing. Risk appetite vs risk tolerance vs risk threshold. Stakeholder risk attitudes: risk-averse, risk-neutral, risk-seeker. Tailoring the risk approach to project size, complexity, and strategic importance.

Domain 2

Risk Identification

Techniques: brainstorming, Delphi technique (anonymous expert consensus rounds), expert interviews, root cause analysis, assumption/constraint analysis, SWOT analysis, documentation review, checklist analysis, prompt lists (PESTLE, TECOP), and diagramming (cause-and-effect, system dynamics). Risk register fields: risk ID, risk description, risk owner, probability, impact, risk score, planned response, and contingency. The risk register is the primary output of risk identification.

Domain 3

Risk Analysis

Qualitative: probability-impact matrix (P×I grid), risk urgency assessment, risk categorisation by RBS, and risk data quality assessment. Quantitative: Expected Monetary Value (EMV = probability × impact), Monte Carlo simulation (most realistic — shows probability distribution of outcomes), decision tree analysis, and sensitivity analysis (tornado diagram — which risk has the largest impact on outcome). Know the difference: qualitative prioritises; quantitative quantifies financial exposure.

Domain 4

Risk Response

Threat responses: avoid (eliminate), transfer (shift impact — insurance, contracts), mitigate (reduce probability/impact), accept (active: contingency reserve; passive: no action). Opportunity responses: exploit (ensure it happens), share (partner to capture), enhance (increase probability/impact), accept. Residual risk: risk remaining after response. Secondary risk: new risk created by the response itself. Contingency reserve (known unknowns) vs management reserve (unknown unknowns).

Domain 5

Monitor and Close Risks

Risk audits: examine effectiveness of risk responses. Risk reassessment: periodically re-evaluate risk register as project evolves. Trigger conditions and risk triggers. Workarounds: unplanned responses to previously unidentified or accepted risks. Reserve analysis: comparing remaining reserves to remaining risks. Lessons learned: documenting risk outcomes for organisational process assets. Risk closure at project end — confirm responses were effective.

ITIL 4 Foundation · 40 questions · 60 minutes

ITIL 4 — IT Service Management

ITIL 4 (Information Technology Infrastructure Library) is the globally adopted framework for IT service management (ITSM). ITIL 4 Foundation is the entry-level certification — required or preferred for service desk managers, IT support professionals, change managers, and ITSM consultants. Pass mark: 26/40 (65%). No experience prerequisite. The exam tests concept recognition, not scenario depth — learn every definition precisely. Published by Axelos and PeopleCert.

Core concept

Service Value System (SVS)

The ITIL 4 SVS describes how all components of an IT organisation work together to create value. Components: Guiding Principles (7 principles), Governance, Service Value Chain (6 activities), Practices (34 practices), and Continual Improvement. The SVS takes opportunity/demand as input and produces value as output. This is the central model — understand the relationship between all five components.

7 Guiding Principles

Focus on Value · Start Where You Are

1) Focus on value — every activity must link to value for stakeholders. 2) Start where you are — don't start from scratch; assess and reuse existing capabilities. 3) Progress iteratively with feedback — small steps, learn and improve. 4) Collaborate and promote visibility — break silos. 5) Think and work holistically — the whole is more than the parts. 6) Keep it simple and practical — eliminate what doesn't add value. 7) Optimise and automate — use technology to maximise efficiency. Memorise all 7 exactly — the exam quotes them directly.

Service Value Chain

Plan · Improve · Engage · Design & Transition · Obtain/Build · Deliver & Support

Six interconnected activities that represent how value flows through an IT organisation. Every service value stream is a specific combination of these activities. Key: the value chain is not a linear process — activities are interconnected and can be combined in multiple sequences depending on the scenario. "Deliver and Support" is often tested as the activity that supports ongoing service delivery and resolves incidents.

4 Dimensions

ITIL 4 Four Dimensions Model

All services and service management must consider 4 dimensions: 1) Organisations and People — culture, roles, structure. 2) Information and Technology — data, knowledge, tools. 3) Partners and Suppliers — external relationships. 4) Value Streams and Processes — how activities create value. Surrounding and constraining all four: External Factors (PESTLE: Political, Economic, Social, Technological, Legal, Environmental). If the exam asks why a service improvement failed, always check if a dimension was overlooked.

Key practices — tested heavily

Incident Management · Problem Management · Change Enablement

Incident Management: restore normal service as quickly as possible; classified by impact and urgency (priority matrix). Problem Management: identify root cause of incidents to prevent recurrence; workaround vs permanent fix; known error database (KEDB). Change Enablement: three change types — standard (pre-approved, low risk), normal (requires approval via change authority), emergency (expedited process, post-implementation review). Know the difference: an incident is unplanned interruption; a problem is the root cause; a known error is a documented problem with a workaround.

Key practices — continued

Service Desk · SLM · Configuration Management · Release Management

Service Desk: single point of contact (SPOC) for users; manages incidents and service requests; channels: phone, chat, email, self-service portal. Service Level Management (SLM): sets, monitors, and reports on SLAs (Service Level Agreements); manages OLAs (Operational Level Agreements with internal teams) and UCs (Underpinning Contracts with suppliers). Service Configuration Management: maintains the CMDB (Configuration Management Database) — records CIs and their relationships. Release Management: makes new/changed services available for use.

ITIL 4 Specialist modules (post-Foundation)

ITIL 4 Specialist

Create, Deliver and Support (CDS)

The most commonly taken Specialist module. Covers: designing service value streams, building service relationships, workforce planning and culture, service performance reporting, the use of automation in ITSM, and coordinating DevOps practices with ITIL processes. Required for the ITIL 4 Managing Professional (MP) designation.

ITIL 4 Specialist

Drive Stakeholder Value (DSV)

Customer experience (CX) and user experience (UX) in service management. Customer journey mapping. Service relationship management — managing the full lifecycle from customer identification to service termination. SLA and OLA design. Onboarding and offboarding services. Co-creating value with customers.

ITIL 4 Strategist

Direct, Plan and Improve (DPI)

The Strategist module applicable to both Managing Professional and Strategic Leader paths. Covers: governance, risk, and compliance in ITSM; cascading strategic direction through the organisation; measurement and reporting design; portfolio and programme management in ITSM; and leading improvement at an organisational level. Required for both ITIL 4 MP and SL designations.

Interactive · Timed · Fully explained

Interactive Practice Exam — PMP, PMI-ACP, PMI-RMP & ITIL 4

A 20-question, 30-minute scenario-based practice test covering PMP process groups, Earned Value Management, Agile/Scrum, risk management, and ITIL 4 service management. PMI exams test professional judgement — each answer includes a full explanation of why the correct choice is best in context. Progress auto-saves; you can pause and resume later.

Loading the interactive practice exam… If it does not load, ensure JavaScript is enabled.

Additional practice · PMI & ITIL

Additional Practice Questions — PMP, PMI-ACP, PMI-RMP & ITIL 4

PMI and ITIL exams test professional judgement — rarely is one answer technically wrong; the question is which approach is most appropriate in context. Practise selecting between situationally better and situationally worse answers, not just memorising definitions.

1. (PMP) A project is 60% complete. The sponsor informs you that an additional feature is critical to stakeholder satisfaction and must be added. The feature was not in the original scope. What should a project manager do FIRST?

  • A) Add the feature immediately to keep the sponsor satisfied
  • B) Submit a change request and follow the integrated change control process
  • C) Refuse the change because the project is already 60% complete
  • D) Update the WBS and schedule without formal change control since the sponsor approved it verbally
Answer: B Scope changes — regardless of who requests them or how critical they seem — must go through integrated change control. This means: 1) Submit a formal change request. 2) Assess the impact on scope, schedule, cost, quality, risk, and resources. 3) Obtain approval from the change control board (or equivalent authority). 4) Update the relevant baseline documents. Verbal sponsor approval (D) is not sufficient because baselines are formal documents. Adding without analysis (A) risks budget and schedule overruns. Refusing outright (C) is not the PM's decision to make alone — it must go to the change authority. This scenario tests the PMP principle that change is expected and managed, not avoided.

2. (PMP — Earned Value) Your project has a BAC of $200,000, an EV of $80,000, an AC of $100,000, and a PV of $90,000. Which statement BEST describes the project status?

  • A) The project is over budget and behind schedule
  • B) The project is under budget and ahead of schedule
  • C) The project is over budget and ahead of schedule
  • D) The project is on budget and behind schedule
Answer: A Calculate: CV (Cost Variance) = EV − AC = 80,000 − 100,000 = −$20,000 (negative = over budget). SV (Schedule Variance) = EV − PV = 80,000 − 90,000 = −$10,000 (negative = behind schedule). Confirm with indices: CPI = EV/AC = 80,000/100,000 = 0.8 (below 1.0 = over budget). SPI = EV/PV = 80,000/90,000 = 0.89 (below 1.0 = behind schedule). Memorise the rule: negative variance = bad; index below 1.0 = bad. EAC = BAC / CPI = 200,000 / 0.8 = $250,000 — the project will cost $50,000 more than planned if current performance continues.

3. (PMP — Agile) You are a product owner on a Scrum team. Halfway through the sprint, a major customer calls with an urgent requirement that will take 3 days to implement. The sprint is 2 weeks long and has 8 days remaining. What should you do?

  • A) Cancel the current sprint and start a new one that includes the urgent requirement at the top of the backlog
  • B) Add the requirement to the product backlog for prioritisation in the next sprint planning session
  • C) Ask the Scrum Master to approve the change and add it to the current sprint
  • D) Negotiate with the customer that the requirement will be delivered in the next sprint (next 2 weeks)
Answer: B In Scrum, the sprint backlog is fixed once the sprint starts — the team commits to the sprint goal. The correct response is to add the new requirement to the product backlog (the Product Owner's responsibility) and bring it into sprint planning at the start of the next sprint, where it can be prioritised appropriately. Sprint cancellation (A) is a drastic measure reserved for when the sprint goal becomes completely invalid — not for one urgent item. Only the Product Owner can cancel a sprint. The Scrum Master (C) does not approve backlog changes. Option D is correct if framed as "the PM should communicate timeline expectations to the customer and add to the backlog" — but B is cleaner. Key: protect the sprint from mid-sprint scope changes.

4. (PMP — Risk) During a risk workshop, the team identifies a risk: a key vendor may become insolvent before delivering a critical component. The team decides to create a formal contractual clause requiring the vendor to escrow source code and to identify an alternative supplier as a backup. Which risk response strategy does this represent?

  • A) Avoid — restructuring the project to eliminate the risk
  • B) Transfer — shifting risk ownership to the vendor
  • C) Mitigate — reducing the probability and impact of the risk
  • D) Accept — acknowledging the risk without action
Answer: C — Mitigate The team is taking two actions that reduce both probability (escrow reduces the impact of insolvency — code is recoverable) and impact (alternate supplier reduces the consequence of the primary vendor failing). This is mitigation — reducing the risk without eliminating or transferring it. Transfer would mean making the vendor contractually bear the financial consequence of the risk (e.g., performance bonds, insurance). Avoid would mean changing the project plan to not use an external vendor at all. Accept means taking no specific action. Identifying an alternative supplier could also be framed as a contingency plan within active acceptance — but the escrow clause specifically reduces impact, making mitigation the primary classification.

5. (PMI-ACP) During a retrospective, a team member raises a consistent concern that the team's velocity has declined over the last three sprints due to accumulating technical debt. What is the BEST way for the team to address this?

  • A) Ignore technical debt — the Product Owner controls the backlog and will prioritise it when ready
  • B) Add a technical debt backlog item, agree to dedicate a percentage of each sprint's capacity to resolving it, and track it on the information radiator
  • C) Tell the team to work faster to compensate for the technical debt overhead
  • D) Stop all feature development until the technical debt is fully resolved
Answer: B Technical debt reduces velocity and quality if left unaddressed. The agile approach is to make it visible (backlog item, information radiator), negotiate dedicated capacity (commonly 10–20% of sprint velocity), and address it incrementally — the same iterative approach applied to features. The Product Owner should be involved because technical debt affects the team's ability to deliver value (A ignores the team's input). Asking the team to work faster (C) ignores root cause and risks burnout. Stopping all feature delivery (D) is rarely acceptable to stakeholders and is not proportionate for most technical debt scenarios. The retrospective is exactly the right forum to surface and commit to addressing this — this is the inspect-and-adapt cycle in action.

6. (ITIL 4 Foundation) A user reports that their laptop cannot connect to the corporate Wi-Fi. After investigation, the service desk determines the issue is caused by a defect in the authentication service affecting all users with laptops updated to firmware version 3.1. What are the CORRECT definitions for the incident and the problem?

  • A) The Wi-Fi outage is the incident; the defect in the authentication service is the problem
  • B) The defect is the incident; the authentication service failure is the problem
  • C) Both are incidents — problems are raised only after incidents are closed
  • D) The firmware update is the incident; the user's laptop is the problem
Answer: A ITIL 4 definitions: Incident — an unplanned interruption to a service or reduction in quality of a service. The Wi-Fi connectivity failure is the incident — it is what the user experiences. Problem — a cause, or potential cause, of one or more incidents. The authentication service defect triggered by firmware 3.1 is the problem. The service desk's goal with the incident is to restore service as quickly as possible (possibly via a workaround — e.g., rollback the firmware). The problem management team's goal is to identify and resolve the root cause permanently. These processes run in parallel: incidents can be resolved without the underlying problem being fixed (using a workaround), and the problem is logged in the Known Error Database (KEDB).

7. (ITIL 4 Foundation) An organisation wants to deploy a major new version of its ERP system that will require downtime of 4 hours on a weekend. The change has been extensively tested and approved by the CAB. Under ITIL 4, which change type is this?

  • A) Standard change — it has been pre-approved as routine
  • B) Normal change — it requires assessment and authorisation through the change authority process
  • C) Emergency change — it requires rapid implementation with a streamlined approval process
  • D) Operational change — it is handled by the operations team without change control
Answer: B — Normal change ITIL 4 defines three change types. Standard change: pre-approved, well-understood, low risk, frequently implemented (e.g., adding a new user, replacing a standard component). Normal change: must be assessed for risk and authorised by the appropriate change authority (Change Advisory Board for high-risk changes, or a delegated authority for medium-risk). A major ERP upgrade with planned downtime is high-risk, high-impact, and requires full CAB review — even though it has been tested, the planned downtime and organisational impact require formal authorisation. Emergency change: must be implemented as quickly as possible to resolve or prevent a major incident — expedited process with full post-implementation review. The CAB has already reviewed this, confirming it is a normal change proceeding through standard authorisation.

8. (PMI-RMP) A project team uses Monte Carlo simulation to model schedule risk. The simulation result shows there is a 30% probability of completing by the target date. Senior management finds this unacceptable. Which action is MOST appropriate?

  • A) Remove the highest-impact risks from the simulation to improve the probability
  • B) Extend the target date to achieve a probability of 80% or above, or implement risk responses to reduce the impact of the highest-variance tasks
  • C) Report the 30% probability as acceptable since the project cannot be changed
  • D) Switch to a simpler qualitative analysis to avoid showing unfavourable results
Answer: B A 30% probability of meeting the target date means a 70% probability of missing it — this is not a viable project position. The correct response is to use the simulation results constructively: identify which tasks have the highest duration variance (the tornado diagram from the simulation shows this), develop risk responses to reduce that variance (mitigate — e.g., add resources, remove dependencies), or adjust the target date to align with the probability the stakeholders are willing to accept (typically 80% for most organisations). Removing risks from the model (A) produces misleading analysis — this is a data integrity issue. Switching methods (D) is not a risk response. A risk manager's value is delivering actionable analysis, not suppressing unfavourable findings.

9. (ITIL 4 Foundation) Which ITIL 4 guiding principle recommends that a service management team assessing existing processes should first evaluate what is already working before designing new processes?

  • A) Focus on value
  • B) Start where you are
  • C) Keep it simple and practical
  • D) Optimise and automate
Answer: B — Start where you are Start where you are means: do not start from scratch without first assessing what already exists. The principle recommends observing directly what is happening today (not relying on reports or assumptions), identifying existing capabilities that can be built upon, and reusing and improving current processes, services, and tools rather than discarding them. This avoids wasted effort recreating what already works. Focus on value asks "does this create value for the stakeholder?" Keep it simple removes unnecessary complexity. Optimise and automate increases efficiency through technology. The exam frequently tests which guiding principle applies to a described organisational scenario — memorise all 7 and their key heuristic.

10. (PMP — Contract types) You are managing a construction project and the design is not yet finalised. The project requires specialised labour and the final cost cannot be estimated reliably. Which contract type BEST protects the buyer while providing flexibility?

  • A) Fixed Price Firm (FFP) — the total price is agreed upfront and bears no financial risk for the buyer
  • B) Time & Materials (T&M) — billed at negotiated labour rates and materials cost; buyer controls scope and has audit rights
  • C) Cost Plus Fixed Fee (CPFF) — seller is reimbursed actual costs plus a fixed profit
  • D) Fixed Price Incentive Fee (FPIF) — provides a target price and ceiling price with incentives for performance
Answer: B — T&M When scope is undefined and work requirements are evolving, T&M contracts provide the flexibility the buyer needs. The buyer only pays for actual hours and materials used, which is appropriate for exploratory or design-phase work. Protection mechanisms: audit rights, not-to-exceed (NTE) clauses, and requiring pre-approval for significant expenditure. FFP (A) requires well-defined scope — an undefined-scope FFP transfers risk to the seller, who compensates by inflating the price. CPFF (C) reimburses all costs plus profit regardless of performance — it provides the least cost control. FPIF (D) requires a target cost estimate, which doesn't exist here. Know contract risk allocation on the PMP exam: the more defined the scope, the more risk transfers to the seller via fixed-price contracts.
Case study · Apply PMP & ITIL concepts

Real-World Walkthrough: The UK NHS IT Programme Failure (NPfIT)

The National Programme for IT (NPfIT) was a UK government initiative launched in 2003 to create a centralised electronic patient records system for the National Health Service. It became one of the most documented IT project management failures in history — abandoned in 2011 after spending £10+ billion (~$12 billion) of the £12.7 billion budget. Every PMP and ITIL exam topic is illustrated by what went wrong.

What happened

  • 2003: NPfIT launched with an estimated budget of £6.2 billion over 10 years. Scope: national electronic health records, electronic prescriptions, a national broadband network (N3), Choose and Book appointment systems, and PACS (Picture Archiving and Communication Systems). Four regional IT contractors selected.
  • 2003–2006: Scope creep accumulates as clinical requirements change. The centralised architecture — a single national "spine" — proves technically difficult. NHS trusts resist standardisation. Contractors (BT, CSC, Fujitsu, Accenture) begin experiencing significant cost overruns.
  • 2006: Accenture exits the programme after writing off £450m in losses. Fujitsu contract terminated in 2008.
  • 2006–2011: The National Audit Office (UK government auditor) publishes critical reports each year showing delays, budget overruns, and clinical adoption failure. Clinicians refuse to use systems delivered because they were designed without adequate user engagement.
  • September 2011: UK government announces NPfIT will be dismantled. Remaining elements transferred to regional programmes. Total spent: over £10 billion. Delivered: the N3 network, Choose and Book, PACS — not the central patient records system.

Map to PMP & ITIL exam domains

Five lessons PMI/ITIL candidates must internalise

  1. Define scope before contracting. Fixed-price contracts with undefined scope are invitations to disputes. The NPfIT selected fixed-price contracts before clinical requirements were agreed — the opposite of procurement best practice.
  2. Engage end users throughout, not just at sign-off. Clinicians who would use the system were consulted but not empowered. Requirements gathering requires collaboration, not presentation.
  3. Large programmes need incremental delivery. The "big bang" delivery approach meant five years of spending before any clinical user could evaluate the system. Agile and iterative delivery would have identified adoption issues far earlier at far lower cost.
  4. Independent audit should trigger corrective action. The National Audit Office published damning reports from 2006 onwards. Programme governance failed to act on these findings — the project continued for five more years. PMP governance expects corrective action in response to performance reports.
  5. Change is expensive at scale. The cost of change increases exponentially with project scale and maturity. The NPfIT demonstrates that scope changes in a £10 billion programme cost far more than they would have in a controlled, incremental delivery model.
Free & reputable only · Verified links

Helpful Materials — PMP, PMI-ACP, PMI-RMP & ITIL 4

Every resource below is free or free-tier. The PMI exam body publishes a large amount of free preparation material — always start with official sources before supplementing with community resources.

PMI — official free resources

Free PMP practice questions

Free PMP video

ITIL 4 — official free resources

Free ITIL 4 practice and learning

35-hour PMP education requirement — free options

Communities (free)

Quick reference · Memorise before exam day

PMP & ITIL 4 Cheatsheet

High-frequency formulas, definitions, and answer-pattern heuristics. The PMP exam rewards instant recognition of EVM formulas and risk vocabulary — drill these until automatic.

Earned Value formulas (must memorise all)

Risk vocabulary

Contract types — risk allocation

ITIL 4 — all 7 guiding principles

  1. Focus on value
  2. Start where you are
  3. Progress iteratively with feedback
  4. Collaborate and promote visibility
  5. Think and work holistically
  6. Keep it simple and practical
  7. Optimise and automate

ITIL 4 — change types

ITIL 4 — key definitions

PMP exam answer heuristics

Study tools · Active recall · PMP / PMI-ACP / CAPM

Flashcards & Term-Matching Game

Active recall beats passive reading for long-term retention. Use the flashcards to drill definitions and the matching game to reinforce connections between concepts. Shuffle to mix domains and reset to start fresh. Keyboard navigation supported on flashcards.

Flashcard Deck — Key Terms

Loading flashcards… ensure JavaScript is enabled.

Term-Matching Game

Click a term on the left, then click its matching definition on the right. Correct pairs lock in green; wrong pairs flash red. Complete all pairs to advance to the next round.

Loading matching game… ensure JavaScript is enabled.

Speed Round — True or False

You have 10 seconds per statement. Answer TRUE or FALSE before the timer runs out. Build a combo multiplier for consecutive correct answers and beat your session high score.

Loading speed round… ensure JavaScript is enabled.

Fill in the Blank

Read the clue and type the missing term. One typo is forgiven for longer answers. Use the hint button if you're stuck — but it costs half the question's points.

Loading fill-in-the-blank… ensure JavaScript is enabled.

Domain Sprint — Categorise the Term

A term appears — click the correct exam domain it belongs to. Correct selections score 100 pts; wrong selections deduct 25 pts. Master domain knowledge before exam day.

Loading domain sprint… ensure JavaScript is enabled.