学习

课程笔记2026 年 9 月 28 日至 10 月 4 日

Week 9 Iteration 2 Go-Live, Quality Assurance & Innovation

本页目录· 18 条

Learning Objectives
Week Context & Goal
Iteration Stage
This Week's Tasks & Important Deadlines
Reuse from Earlier Weeks
Knowledge Base
Studio 1
Before class
In class agenda
Evidence to leave with
Seminar
Studio 2
Before class
In class agenda
Evidence to leave with
Wrap-up
End-of-week review
Carry forward to Week 10

Monday 28 September 2026 – Sunday 4 October 2026

Learning Objectives

By the end of this week, you'll be able to:

学习

课程笔记2026 年 9 月 28 日至 10 月 4 日

Week 9 Iteration 2 Go-Live, Quality Assurance & Innovation

本页目录· 18 条

Learning Objectives
Week Context & Goal
Iteration Stage
This Week's Tasks & Important Deadlines
Reuse from Earlier Weeks
Knowledge Base
Studio 1
Before class
In class agenda
Evidence to leave with
Seminar
Studio 2
Before class
In class agenda
Evidence to leave with
Wrap-up
End-of-week review
Carry forward to Week 10

Monday 28 September 2026 – Sunday 4 October 2026

Learning Objectives

By the end of this week, you'll be able to:

Develop a compelling product narrative.

Use quality practices that find defects earlier.

Turn Iteration 2 mentor feedback into an evidence-based Iteration 3 innovation hypothesis.

Learning Outcomes 8–12

Week Context & Goal

After the break, the team simultaneously closes the Iteration 2 learning loop and opens Iteration 3. Mentors will review the existing build; the team must respond to their evidence, identify a worthwhile innovation and communicate the next direction clearly.

Weekly goal: show the Iteration 2 build honestly, capture mentor evidence, then select an Iteration 3 idea that strengthens user value and can be delivered with visible quality controls.

Iteration Stage

Iteration 2 go-live/showcase → mentor feedback → Iteration 3 discovery & quality planning

Use pair programming, story kick-offs and desk checks to shift quality left.
Treat the Product Video as a sponsor narrative, not a feature catalogue.
Evaluate innovation against user value, feasibility, ethics, evidence and lifecycle risk.
Put the selected idea, tests and ownership into the Iteration 3 backlog.

This Week's Tasks & Important Deadlines

Mon 28 Sep, 11:55 PM AEST — Iteration 3 Discovery Presentation, including PGP — official resource; upload to the Project Governance folder.
Studio 2 — Industry Mentor Visit 4: Iteration 2 Build Showcase
End of Studio 2 — Iteration 3 Idea Collection form
Start the 2–3 minute Product Video now; it will be viewed with Industry Mentors in Week 11 Friday studio and submitted in the PGP/ePortfolio.

Reuse from Earlier Weeks

Week 5 — QA: extend the existing checklist/defect habits into an end-to-end shift-left evidence chain.
Week 7 — Desk Checks: apply them before final QA and record outcomes in governance.
Week 8 — Continuous Improvement: convert mentor and defect evidence into a specific next-iteration change.
Week 8 — Data Storytelling: use context → evidence → meaning → action to structure discovery and the Product Video.
Iteration 2 and Iteration 3 hubs: link build evidence, feedback, discovery decisions, risks and ownership.

Knowledge Base

Pair Programming & Collective Code Ownership

Shift-Left QA — Kick-offs, Desk Checks & Website Checklist

Product Narrative & 2–3 Minute Video Playbook

Responsible GenAI — Ethics, Environment & Participation

Mobile App Trends — Select with Evidence, Not Hype

Prompt Design for Human-Centred AI

Week 9 Seminar Capture

Studio 1

Before class

Read The Ultimate Guide to Effective Pair Programming.
Read The Ultimate Website QA Checklist.
Read Story Kick-offs and Desk Checks — 6 Ideas to Shift Left.
Watch Quality Assurance.
Work on the Iteration 3 Discovery Presentation.
Read the official Product Video Guidelines.
Attempt to view the sample Product Video; it currently returns access denied, so use the official PDF as the authoritative brief.
Complete the Week 9 Pre-reading Quiz.

In class agenda

Deliver the Iteration 3 Product Discovery Presentation.
Receive retrospective and ePortfolio feedback.
Use ACMI Storyboards to plan the sponsor narrative.

Evidence to leave with

Discovery decision and feedback captured in the PGP.
Iteration 3 idea linked to a user need, evidence and success measure.
QA approach identifies where each defect type should be found.
Pair-programming/desk-check protocol agreed.
Product Video purpose, busy-sponsor audience, message and first storyboard recorded.

Seminar

Guest lecturer: Moodle does not list a name; confirm in class.
Location: CL_25 Exhibition Walk, Room C1, Theatre (Building 63).
Zoom: webinar — passcode 302545.

Capture three insights, their supporting examples and one implication for Iteration 3.
Complete the Week 9 Seminar Quiz.

The linked historical recordings are catalogued in Week 9 Seminar Capture and currently return access denied; the page remains an in-class capture template.

Studio 2

Before class

Read Generative AI, Ethics & Its Impact on the Environment.
Read Mobile App Development Trends of 2024 critically as a vendor-authored, time-bound trend article.
Read Prompts Should Be Designed, Not Engineered.
Prepare a concise Iteration 2 build demonstration and known-limitations list.
Score candidate Iteration 3 ideas on user value, evidence, feasibility, ethics, risk and measurability.

In class agenda

Industry Mentor Visit 4 — Iteration 2 Build Showcase.
Collect feedback and distinguish request, observation, constraint and assumption.
Submit the Iteration 3 Idea Collection form by the end of class.

Evidence to leave with

Mentor feedback logged with source and interpretation.
Accepted / deferred / rejected decisions include rationale.
Selected Iteration 3 idea has an owner, success measure and first validation task.
Any GenAI feature has a human-centred prompt spec, risk controls and a non-AI alternative.
Quality evidence and known limitations are linked from the governance folder.

Wrap-up

End-of-week review

Did mentor feedback change the Iteration 3 direction? Record how and why.
Is the innovation grounded in a validated user outcome rather than a trend?
Can the team show where quality is checked before final testing?
Did pairing or desk checks reduce ambiguity, rework or single-person dependency?
Does the Product Video storyboard communicate problem, people, solution, benefit, evidence and ask within 2–3 minutes?
Are AI/environment claims treated critically and supported before reuse?

Carry forward to Week 10

Fri 9 Oct — Expo Info Collection Form — one submission per team.
Thu 8 Oct, 11:55 PM AEST — Iteration 3 Pre-deployment Readiness — continue building toward the readiness evidence.
Prepare Iteration 3 review evidence and start the software-handover artefact.
Bring the Product Video storyboard, licensed asset plan and contribution ownership into production.

课程目录