ITIL 4 PM PDF study materials
ITIL 4 PM PDF study resources

ITIL 4 PM PDF study plan

ITIL 4 PM PDF · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Project management concepts

  • Define each core project management concept in your own words: project, programme, portfolio, product, and work package, and state one boundary example for each

  • Map the ITIL 4 key concepts (value, value co-creation, organisation, outcome, output, cost, risk, utility, warranty) onto a simple project you have worked on

  • Distinguish project lifecycle models (predictive, iterative, incremental, agile, hybrid) and justify which fits two contrasting scenarios

  • Explain how project management relates to the ITIL 4 service value chain and where a project typically enters and exits it

  • Build a one-page glossary of 25 terms with a personal example beside each

Your checkpoint

A 25-term personal glossary with one original worked example per term and a 300-word note on choosing a lifecycle model

Week 2

Project management concepts & Value streams and processes for project management

  • Describe the purpose and minimum viable content of a project charter, business case, and benefits management plan

  • Decompose a value stream into stages, inputs, outputs, and value-add versus non-value-add steps for a realistic project scenario

  • Identify the processes and activities in the ITIL 4 service value chain that a project manager most often touches

  • Practise selecting and sequencing practices (not processes) to support a project from initiation to handover

  • Articulate how value stream mapping exposes waste in a project's approval and handover steps

Your checkpoint

A value stream map for one end-to-end project scenario, annotated with the ITIL practices involved at each stage

Week 3

Project management practices and ITIL practices

  • State the purpose, key inputs, key outputs, and one common failure mode for each of: project management, portfolio management, risk management, and change enablement

  • Compare how the practices of relationship management, supplier management, and service level management interact on a single project

  • Explain how continual improvement and measurement and reporting keep a project aligned to outcomes

  • Match ten realistic project situations to the ITIL practice that most directly addresses them, with a one-line justification each

  • Draft the practice-level content of a project's governance and reporting pack

Your checkpoint

A practice-to-situation matrix covering at least 12 ITIL practices, each with purpose, key outputs, and one failure mode

Week 4

Project management practices and ITIL practices & Value streams and processes for project management

  • Integrate the practices from week 3 into a single end-to-end process flow with clear entry and exit criteria

  • Define roles, responsibilities, and decision rights for each step using a RACI-style view

  • Specify the information items and records a project must create, keep, and retire, and where they live

  • Test the flow against two failure scenarios (late supplier delivery, unplanned scope change) and note where it breaks

  • Produce a process narrative a new team member could follow without further explanation

Your checkpoint

A documented end-to-end project process flow with RACI, entry and exit criteria, and a written walkthrough of two failure scenarios

Week 5

Organizations and people in project management

  • Explain the ITIL 4 organisational components (culture, roles, competencies, authority, communication) and give a project example of each

  • Design an operating model for a project team covering structure, decision rights, and escalation paths

  • Describe how organisational culture and change resistance affect project delivery, and name three concrete countermeasures

  • Map the key project roles and explain how each contributes to value co-creation

  • Outline a stakeholder communication and engagement approach for a mixed internal and external audience

Your checkpoint

A one-page project operating model plus a stakeholder engagement and communication plan

Week 6

Information and technology for project management

  • Classify the information and technology components a project needs: tooling, data, knowledge, and automation

  • Define the information model for a project, including data ownership, quality criteria, and retention

  • Explain how collaboration and workflow tooling changes the project's process flow, and identify two trade-offs

  • Identify the risks of poor data quality and automation overreach in project reporting

  • Specify the minimum reporting dashboard for a project sponsor, with metrics and their sources

Your checkpoint

An information and technology plan for the project, including a data ownership table and a sponsor dashboard specification

Week 7

Partners and suppliers in project management

  • Explain how internal and external partners and suppliers contribute to a project's value streams

  • Define selection criteria and due diligence steps for a supplier on a project with service dependencies

  • Draft the service level and reporting expectations that belong in a supplier agreement for a project

  • Describe how to manage multi-supplier integration risk and shared responsibility boundaries

  • Plan an exit or transition approach for a supplier relationship at project closure

Your checkpoint

A supplier engagement pack containing selection criteria, a service level outline, a responsibility matrix, and an exit plan

Week 8

Project management concepts & Project management practices and ITIL practices & Value streams and processes for project management & Organizations and people in project management & Information and technology for project management & Partners and suppliers in project management

  • Reconstruct each domain's core content from memory using a blank-page recall exercise, then compare against your notes

  • Complete timed practice questions across all six domains and log every error with its root cause

  • Re-teach the three weakest topics aloud in five minutes each without notes

  • Consolidate the eight weekly deliverables into a single revision summary of no more than six pages

  • Build a final-week checklist of facts, definitions, and distinctions you must be able to state cold

Your checkpoint

A six-page consolidated revision summary plus an error log with root causes and a pre-exam checklist

Milestones

Week 2: You can explain the difference between output and outcome, and between utility and warranty, using your own examples, and your value stream map shows clear entry and exit points

Week 4: Your end-to-end process flow survives both failure scenarios with no undefined decision rights, and you can name the purpose and one failure mode for at least 12 ITIL practices

Week 6: You can describe the five organisational components and the information and technology components of your project without notes, and your dashboard metrics each trace to a named data owner

Week 8: Timed practice across all six domains shows at least 75 percent correct, your error log has no repeated root cause, and you can state every checklist item cold in under 30 minutes