Course Map¶
Instructor material
This page is for instructors and teaching assistants. Students should not need it.
How modules, outcomes, labs, case studies, and assessments align. Use it to plan delivery, construct a syllabus for accreditation, or identify gaps. The full session plan with objectives and activities is in the Curriculum Roadmap.
Session allocation (16 weeks, 32 sessions)¶
| Week | Session 1 | Session 2 |
|---|---|---|
| 1 | S1 · Topic 1 — Introduction to software project management (M01) | S2 · Topic 2 — Software projects versus other projects (M01) |
| 2 | S3 · Topic 3 — Life cycles and development approaches (M01) | S4 · Topic 4 — Stakeholders and governance (M02) |
| 3 | S5 · Topic 5 — Initiation and business cases (M02) | S6 · Topic 6 — Feasibility and project selection (M02) |
| 4 | S7 · Integrated planning and baselines (M03) | S8 · Topic 11 — Agile and predictive approaches (M04) |
| 5 | S9 · Topic 12 — Scrum (M04) | S10 · Topic 13 — Kanban and WIP limits (M04) |
| 6 | S11 · Topic 7 — Requirements and scope (M05) | S12 · Topic 8 — WBS (M05) |
| 7 | S13 · Topic 9 — Scheduling (M06) | S14 · Topic 10 — Gantt charts and dependencies (M06) |
| 8 | S15 · Topic 14 — Effort and cost estimation (M07) | S16 · Topic 15 — Function points and other estimation (M07) |
| 9 | S17 · Mid-course consolidation and capstone checkpoint | S18 · Topic 16 — Risk (M08) |
| 10 | S19 · Topic 17 — Quality management (M09) | S20 · Topic 18 — Teams and resources (M10) |
| 11 | S21 · Topic 19 — Communication and stakeholders (M10) | S22 · Topic 20 — Metrics (M11) |
| 12 | S23 · Topic 21 — Monitoring and control (M11) | S24 · Topic 22 — Change and configuration management (M11) |
| 13 | S25 · Topic 23 — Procurement and vendors (M12) | S26 · Topics 24 & 27 — Documentation, closure, lessons learned (M12) |
| 14 | S27 · Topic 25 — Distributed and remote teams (M12) | S28 · Topic 26 — Ethical and responsible practice (M12) |
| 15 | S29 · Topic 28 — Advanced management and governance (M12) | S30 · Capstone: plan review and risk clinic (M13) |
| 16 | S31 · Capstone: build, control, and reporting (M13) | S32 · Capstone: presentations, closure, retrospective (M13) |
One session per required topic statement, with two exceptions: session 7 (Module 03) is an integrative session with no single numbered topic, and session 26 pairs documentation with closure and lessons learned because they support the same handover outcome. Session 17 is a consolidation checkpoint rather than new content.
Module → outcome → assessment¶
All 25 labs are available. Lab numbers are programme-wide, not per module, so a module maps to whichever labs exercise it.
| Module | Primary outcome | Labs | Case study | Assessment |
|---|---|---|---|---|
| 01 Foundations | Define projects, life cycles, roles, success | 01, 03 | Campus Event Portal | Foundations quiz |
| 02 Initiation | Write a charter; analyse stakeholders | 01, 02, 03, 04, 05 | Campus Event Portal | Foundations quiz |
| 03 Planning | Integrate plan components; control change | 19, 23 | Campus Event Portal | Quiz 03 (planned) |
| 04 Agile & Scrum | Choose and justify a delivery approach | 14, 15, 23 | Campus Event Portal | Quiz 04 (planned) |
| 05 Scope | Elicit requirements; build and baseline a WBS | 06, 07 | Campus Event Portal | Quiz 05 (planned) |
| 06 Schedule | Sequence work; find the critical path | 08, 09, 10, 16 | Campus Event Portal | Quiz 06 (planned) |
| 07 Cost & Estimation | Estimate effort and cost with uncertainty | 13 | Campus Event Portal | Quiz 07 (planned) |
| 08 Risk | Identify, assess, and respond to risk | 11, 17 | Campus Event Portal | Quiz 08 (planned) |
| 09 Quality | Plan and control quality; manage technical debt | 20 | Campus Event Portal | Quiz 09 (planned) |
| 10 Resources | Plan teams, communication, and responsibility | 05, 12, 21 | Campus Event Portal | Quiz 10 (planned) |
| 11 Metrics | Monitor progress and take corrective action | 18, 19, 22 | Campus Event Portal | Quiz 11 (planned) |
| 12 Advanced | Design coordination for scale and distribution | 24, 25 | Campus Event Portal | Quiz 12 (planned) |
| 13 Capstone | Integrate the full toolset on a real project | The capstone itself, drawing on labs 01–25 | — | Capstone rubric (planned) |
Coverage of course-level outcomes¶
| Course outcome (from the Syllabus) | Taught in | Practised in | Assessed in |
|---|---|---|---|
| 1. Projects, programmes, portfolios | 01 | Labs 01, 03 | Foundations quiz |
| 2. Initiate a project | 02 | Labs 01–05 | Foundations quiz |
| 3. Plan across knowledge areas | 03, 05–10 | Labs 06–13, 16, 17 | Quizzes 03, 05–10 (planned) |
| 4. Choose predictive vs. adaptive | 04, 12 | Labs 14, 15, 23 | Quiz 04 (planned) |
| 5. Build core artefacts | 02–11 | Labs 01–22 | Capstone |
| 6. Apply measurement | 11 | Labs 18, 19, 22 | Quiz 11 (planned) |
| 7. Work in a team | 10 | Labs 12, 21, 24 | Quiz 10 (planned) |
| 8. Deliver a capstone | 13 | Lab 25 and the capstone | Capstone rubric (planned) |
Delivery checkpoint template¶
A one-page weekly plan:
Week: [N]
Module: [NN — name]
Pre-work: [Lesson(s) to read before contact time]
Contact: [Lab / case discussion / Q&A]
Deliverable: [What students submit or keep]
Assessment: [Quiz or rubric]
Watch for: [The common difficulty from the Teaching Guide relevant here]
Gaps and dependencies¶
- Labs 02–12, quizzes 03–12, and most case studies are not yet written. They are listed as (planned) and prioritised in the Implementation Plan.
- Until a lab for a module exists, students can use the corresponding template to practise the same skill.
- The capstone rubric must exist before the capstone is used for credit.
Mapping to an accreditation syllabus¶
Outcomes are written in observable terms so they can be mapped directly to programme outcomes. When mapping, note that the course intentionally covers both predictive and adaptive practice; a mapping that recognises only one will understate its coverage.