PROJECT-10 · Advanced · ENGLISH · PLANNED
Start with a delivery problem, build the project artifact, simulate a change and defend the decision.
Study time is an initial activity estimate, excluding extra reading, revision and extended laboratory or project work. Videos and question bodies have not been produced by adding this outline.
Complete these courses or demonstrate equivalent knowledge. These are recommended prerequisites, not enforced enrolment locks.
YouTube playlist: ARK Project Management | Programme, Portfolio and PMO Management
Playlist title reserved in the plan; no YouTube playlist or upload has been created yet.
Sign in to save this learning pathPractical outcome: Coordinate three linked projects around a shared customer outcome.
Explain programmes versus projects using a visual and one worked real-world example. Context: Coordinate three linked projects around a shared customer outcome. End with a prediction or check-for-understanding.
Explain programme vision using a visual and one worked real-world example. Context: Coordinate three linked projects around a shared customer outcome. End with a prediction or check-for-understanding.
Explain benefits maps using a visual and one worked real-world example. Context: Coordinate three linked projects around a shared customer outcome. End with a prediction or check-for-understanding.
Explain inter-project dependencies using a visual and one worked real-world example. Context: Coordinate three linked projects around a shared customer outcome. End with a prediction or check-for-understanding.
Use the first concepts from this section. Coordinate three linked projects around a shared customer outcome. Produce a labelled diagram, trace or calculation; explain each step and check one changed input.
3–6 questions on the preceding first-half concepts only: recall, visual interpretation, application and one plausible misconception. Explain each answer after submission.
Explain programme roadmaps using a visual and one worked real-world example. Context: Coordinate three linked projects around a shared customer outcome. End with a prediction or check-for-understanding.
Explain governance integration using a visual and one worked real-world example. Context: Coordinate three linked projects around a shared customer outcome. End with a prediction or check-for-understanding.
Explain benefits transitions using a visual and one worked real-world example. Context: Coordinate three linked projects around a shared customer outcome. End with a prediction or check-for-understanding.
Explain programme closure using a visual and one worked real-world example. Context: Coordinate three linked projects around a shared customer outcome. End with a prediction or check-for-understanding.
Coordinate three linked projects around a shared customer outcome. Work without the example, compare two cases, record assumptions and limitations, then self-review correctness, reasoning and clarity.
6–12 questions covering Programmes versus projects, Programme vision, Benefits maps and the remaining section concepts, with cumulative retrieval from earlier sections. Include a new transfer problem; 70% unlocks progression.
Practical outcome: Rebalance a fictional portfolio when available funding falls.
Explain portfolio objectives using a visual and one worked real-world example. Context: Rebalance a fictional portfolio when available funding falls. End with a prediction or check-for-understanding.
Explain portfolio inventories using a visual and one worked real-world example. Context: Rebalance a fictional portfolio when available funding falls. End with a prediction or check-for-understanding.
Explain prioritisation criteria using a visual and one worked real-world example. Context: Rebalance a fictional portfolio when available funding falls. End with a prediction or check-for-understanding.
Explain risk balance using a visual and one worked real-world example. Context: Rebalance a fictional portfolio when available funding falls. End with a prediction or check-for-understanding.
Use the first concepts from this section. Rebalance a fictional portfolio when available funding falls. Produce a labelled diagram, trace or calculation; explain each step and check one changed input.
3–6 questions on the preceding first-half concepts only: recall, visual interpretation, application and one plausible misconception. Explain each answer after submission.
Explain capacity allocation using a visual and one worked real-world example. Context: Rebalance a fictional portfolio when available funding falls. End with a prediction or check-for-understanding.
Explain scenario portfolios using a visual and one worked real-world example. Context: Rebalance a fictional portfolio when available funding falls. End with a prediction or check-for-understanding.
Explain portfolio reviews using a visual and one worked real-world example. Context: Rebalance a fictional portfolio when available funding falls. End with a prediction or check-for-understanding.
Explain termination decisions using a visual and one worked real-world example. Context: Rebalance a fictional portfolio when available funding falls. End with a prediction or check-for-understanding.
Rebalance a fictional portfolio when available funding falls. Work without the example, compare two cases, record assumptions and limitations, then self-review correctness, reasoning and clarity.
6–12 questions covering Portfolio objectives, Portfolio inventories, Prioritisation criteria and the remaining section concepts, with cumulative retrieval from earlier sections. Include a new transfer problem; 70% unlocks progression.
Practical outcome: Design a small PMO that solves measurable delivery problems.
Explain pmo purposes using a visual and one worked real-world example. Context: Design a small PMO that solves measurable delivery problems. End with a prediction or check-for-understanding.
Explain service catalogues using a visual and one worked real-world example. Context: Design a small PMO that solves measurable delivery problems. End with a prediction or check-for-understanding.
Explain delivery standards using a visual and one worked real-world example. Context: Design a small PMO that solves measurable delivery problems. End with a prediction or check-for-understanding.
Explain capability assessment using a visual and one worked real-world example. Context: Design a small PMO that solves measurable delivery problems. End with a prediction or check-for-understanding.
Use the first concepts from this section. Design a small PMO that solves measurable delivery problems. Produce a labelled diagram, trace or calculation; explain each step and check one changed input.
3–6 questions on the preceding first-half concepts only: recall, visual interpretation, application and one plausible misconception. Explain each answer after submission.
Explain coaching using a visual and one worked real-world example. Context: Design a small PMO that solves measurable delivery problems. End with a prediction or check-for-understanding.
Explain knowledge systems using a visual and one worked real-world example. Context: Design a small PMO that solves measurable delivery problems. End with a prediction or check-for-understanding.
Explain pmo metrics using a visual and one worked real-world example. Context: Design a small PMO that solves measurable delivery problems. End with a prediction or check-for-understanding.
Explain pmo improvement using a visual and one worked real-world example. Context: Design a small PMO that solves measurable delivery problems. End with a prediction or check-for-understanding.
Design a small PMO that solves measurable delivery problems. Work without the example, compare two cases, record assumptions and limitations, then self-review correctness, reasoning and clarity.
6–12 questions covering PMO purposes, Service catalogues, Delivery standards and the remaining section concepts, with cumulative retrieval from earlier sections. Include a new transfer problem; 70% unlocks progression.
Combine all three sections: Design a small PMO that solves measurable delivery problems. Submit an original worked artifact, evidence or tests, assumptions and a reflection. Rubric: correctness, method, practical usefulness, reproducibility and communication. Self-reviewed, not certified.
6–12 balanced questions sampling every section of Programme, Portfolio and PMO Management, including interpretation, calculation or reasoning, a misconception and a new application. Passing is 70%; review errors before retrying.
Project charters, schedules, risk registers, delivery simulations and benefits reviews. Guided work leads to an independent attempt, with a diagram, explanation, trace, calculation or tested artifact. Question bodies are generated when opened in your private learning path. Programming submissions are stored as text; the platform does not execute submitted code.
Use original or appropriately licensed datasets. Practical science activities use models or supplied data unless a qualified supervisor has reviewed a physical experiment.
Open the interactive practice sampler →