PROJECT-03 · 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 | Requirements, Scope and Systems Thinking
Playlist title reserved in the plan; no YouTube playlist or upload has been created yet.
Sign in to save this learning pathPractical outcome: Interview fictional customers and turn observations into requirements.
Explain problem interviews using a visual and one worked real-world example. Context: Interview fictional customers and turn observations into requirements. End with a prediction or check-for-understanding.
Explain observation techniques using a visual and one worked real-world example. Context: Interview fictional customers and turn observations into requirements. End with a prediction or check-for-understanding.
Explain stakeholder needs using a visual and one worked real-world example. Context: Interview fictional customers and turn observations into requirements. End with a prediction or check-for-understanding.
Explain functional requirements using a visual and one worked real-world example. Context: Interview fictional customers and turn observations into requirements. End with a prediction or check-for-understanding.
Use the first concepts from this section. Interview fictional customers and turn observations into requirements. 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 quality requirements using a visual and one worked real-world example. Context: Interview fictional customers and turn observations into requirements. End with a prediction or check-for-understanding.
Explain requirements prioritisation using a visual and one worked real-world example. Context: Interview fictional customers and turn observations into requirements. End with a prediction or check-for-understanding.
Explain acceptance criteria using a visual and one worked real-world example. Context: Interview fictional customers and turn observations into requirements. End with a prediction or check-for-understanding.
Explain requirements traceability using a visual and one worked real-world example. Context: Interview fictional customers and turn observations into requirements. End with a prediction or check-for-understanding.
Interview fictional customers and turn observations into requirements. Work without the example, compare two cases, record assumptions and limitations, then self-review correctness, reasoning and clarity.
6–12 questions covering Problem interviews, Observation techniques, Stakeholder needs and the remaining section concepts, with cumulative retrieval from earlier sections. Include a new transfer problem; 70% unlocks progression.
Practical outcome: Create a work breakdown structure for a small learning website.
Explain product scope using a visual and one worked real-world example. Context: Create a work breakdown structure for a small learning website. End with a prediction or check-for-understanding.
Explain project scope using a visual and one worked real-world example. Context: Create a work breakdown structure for a small learning website. End with a prediction or check-for-understanding.
Explain work breakdown structures using a visual and one worked real-world example. Context: Create a work breakdown structure for a small learning website. End with a prediction or check-for-understanding.
Explain work packages using a visual and one worked real-world example. Context: Create a work breakdown structure for a small learning website. End with a prediction or check-for-understanding.
Use the first concepts from this section. Create a work breakdown structure for a small learning website. 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 scope statements using a visual and one worked real-world example. Context: Create a work breakdown structure for a small learning website. End with a prediction or check-for-understanding.
Explain exclusions using a visual and one worked real-world example. Context: Create a work breakdown structure for a small learning website. End with a prediction or check-for-understanding.
Explain scope baselines using a visual and one worked real-world example. Context: Create a work breakdown structure for a small learning website. End with a prediction or check-for-understanding.
Explain scope creep using a visual and one worked real-world example. Context: Create a work breakdown structure for a small learning website. End with a prediction or check-for-understanding.
Create a work breakdown structure for a small learning website. Work without the example, compare two cases, record assumptions and limitations, then self-review correctness, reasoning and clarity.
6–12 questions covering Product scope, Project scope, Work breakdown structures and the remaining section concepts, with cumulative retrieval from earlier sections. Include a new transfer problem; 70% unlocks progression.
Practical outcome: Assess the schedule and value effects of a proposed requirement change.
Explain systems boundaries using a visual and one worked real-world example. Context: Assess the schedule and value effects of a proposed requirement change. End with a prediction or check-for-understanding.
Explain feedback loops using a visual and one worked real-world example. Context: Assess the schedule and value effects of a proposed requirement change. End with a prediction or check-for-understanding.
Explain dependency mapping using a visual and one worked real-world example. Context: Assess the schedule and value effects of a proposed requirement change. End with a prediction or check-for-understanding.
Explain change requests using a visual and one worked real-world example. Context: Assess the schedule and value effects of a proposed requirement change. End with a prediction or check-for-understanding.
Use the first concepts from this section. Assess the schedule and value effects of a proposed requirement change. 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 impact analysis using a visual and one worked real-world example. Context: Assess the schedule and value effects of a proposed requirement change. End with a prediction or check-for-understanding.
Explain change authority using a visual and one worked real-world example. Context: Assess the schedule and value effects of a proposed requirement change. End with a prediction or check-for-understanding.
Explain configuration records using a visual and one worked real-world example. Context: Assess the schedule and value effects of a proposed requirement change. End with a prediction or check-for-understanding.
Explain acceptance evidence using a visual and one worked real-world example. Context: Assess the schedule and value effects of a proposed requirement change. End with a prediction or check-for-understanding.
Assess the schedule and value effects of a proposed requirement change. Work without the example, compare two cases, record assumptions and limitations, then self-review correctness, reasoning and clarity.
6–12 questions covering Systems boundaries, Feedback loops, Dependency mapping and the remaining section concepts, with cumulative retrieval from earlier sections. Include a new transfer problem; 70% unlocks progression.
Combine all three sections: Assess the schedule and value effects of a proposed requirement change. 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 Requirements, Scope and Systems Thinking, 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 →