PROJECT-08 · Undergraduate · 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 | Agile, Scrum, Kanban and Hybrid Delivery
Playlist title reserved in the plan; no YouTube playlist or upload has been created yet.
Sign in to save this learning pathPractical outcome: Compare predictive and adaptive plans for an uncertain product.
Explain empiricism using a visual and one worked real-world example. Context: Compare predictive and adaptive plans for an uncertain product. End with a prediction or check-for-understanding.
Explain iterative delivery using a visual and one worked real-world example. Context: Compare predictive and adaptive plans for an uncertain product. End with a prediction or check-for-understanding.
Explain incremental delivery using a visual and one worked real-world example. Context: Compare predictive and adaptive plans for an uncertain product. End with a prediction or check-for-understanding.
Explain agile values using a visual and one worked real-world example. Context: Compare predictive and adaptive plans for an uncertain product. End with a prediction or check-for-understanding.
Use the first concepts from this section. Compare predictive and adaptive plans for an uncertain product. 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 customer feedback using a visual and one worked real-world example. Context: Compare predictive and adaptive plans for an uncertain product. End with a prediction or check-for-understanding.
Explain small batches using a visual and one worked real-world example. Context: Compare predictive and adaptive plans for an uncertain product. End with a prediction or check-for-understanding.
Explain sustainable pace using a visual and one worked real-world example. Context: Compare predictive and adaptive plans for an uncertain product. End with a prediction or check-for-understanding.
Explain tailoring approaches using a visual and one worked real-world example. Context: Compare predictive and adaptive plans for an uncertain product. End with a prediction or check-for-understanding.
Compare predictive and adaptive plans for an uncertain product. Work without the example, compare two cases, record assumptions and limitations, then self-review correctness, reasoning and clarity.
6–12 questions covering Empiricism, Iterative delivery, Incremental delivery and the remaining section concepts, with cumulative retrieval from earlier sections. Include a new transfer problem; 70% unlocks progression.
Practical outcome: Plan and review a fictional sprint without presenting role-play as certification.
Explain product goals using a visual and one worked real-world example. Context: Plan and review a fictional sprint without presenting role-play as certification. End with a prediction or check-for-understanding.
Explain product ownership using a visual and one worked real-world example. Context: Plan and review a fictional sprint without presenting role-play as certification. End with a prediction or check-for-understanding.
Explain scrum teams using a visual and one worked real-world example. Context: Plan and review a fictional sprint without presenting role-play as certification. End with a prediction or check-for-understanding.
Explain product backlogs using a visual and one worked real-world example. Context: Plan and review a fictional sprint without presenting role-play as certification. End with a prediction or check-for-understanding.
Use the first concepts from this section. Plan and review a fictional sprint without presenting role-play as certification. 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 sprint planning using a visual and one worked real-world example. Context: Plan and review a fictional sprint without presenting role-play as certification. End with a prediction or check-for-understanding.
Explain daily inspection using a visual and one worked real-world example. Context: Plan and review a fictional sprint without presenting role-play as certification. End with a prediction or check-for-understanding.
Explain sprint reviews using a visual and one worked real-world example. Context: Plan and review a fictional sprint without presenting role-play as certification. End with a prediction or check-for-understanding.
Explain retrospectives using a visual and one worked real-world example. Context: Plan and review a fictional sprint without presenting role-play as certification. End with a prediction or check-for-understanding.
Plan and review a fictional sprint without presenting role-play as certification. Work without the example, compare two cases, record assumptions and limitations, then self-review correctness, reasoning and clarity.
6–12 questions covering Product goals, Product ownership, Scrum teams and the remaining section concepts, with cumulative retrieval from earlier sections. Include a new transfer problem; 70% unlocks progression.
Practical outcome: Use a paper Kanban board to diagnose delays and improve flow.
Explain visualising work using a visual and one worked real-world example. Context: Use a paper Kanban board to diagnose delays and improve flow. End with a prediction or check-for-understanding.
Explain work-in-progress limits using a visual and one worked real-world example. Context: Use a paper Kanban board to diagnose delays and improve flow. End with a prediction or check-for-understanding.
Explain cycle time using a visual and one worked real-world example. Context: Use a paper Kanban board to diagnose delays and improve flow. End with a prediction or check-for-understanding.
Explain throughput using a visual and one worked real-world example. Context: Use a paper Kanban board to diagnose delays and improve flow. End with a prediction or check-for-understanding.
Use the first concepts from this section. Use a paper Kanban board to diagnose delays and improve flow. 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 cumulative flow using a visual and one worked real-world example. Context: Use a paper Kanban board to diagnose delays and improve flow. End with a prediction or check-for-understanding.
Explain flow policies using a visual and one worked real-world example. Context: Use a paper Kanban board to diagnose delays and improve flow. End with a prediction or check-for-understanding.
Explain hybrid governance using a visual and one worked real-world example. Context: Use a paper Kanban board to diagnose delays and improve flow. End with a prediction or check-for-understanding.
Explain scaling limitations using a visual and one worked real-world example. Context: Use a paper Kanban board to diagnose delays and improve flow. End with a prediction or check-for-understanding.
Use a paper Kanban board to diagnose delays and improve flow. Work without the example, compare two cases, record assumptions and limitations, then self-review correctness, reasoning and clarity.
6–12 questions covering Visualising work, Work-in-progress limits, Cycle time and the remaining section concepts, with cumulative retrieval from earlier sections. Include a new transfer problem; 70% unlocks progression.
Combine all three sections: Use a paper Kanban board to diagnose delays and improve flow. 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 Agile, Scrum, Kanban and Hybrid Delivery, 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 →