学习

课程笔记2026 年 9 月 14 日至 9 月 20 日

Week 8 Iteration 2 Continuous Improvement

本页目录· 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 9

Monday 14 September 2026 – Sunday 20 September 2026

Learning Objectives

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

学习

课程笔记2026 年 9 月 14 日至 9 月 20 日

Week 8 Iteration 2 Continuous Improvement

本页目录· 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 9

Monday 14 September 2026 – Sunday 20 September 2026

Learning Objectives

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

Champion a culture of continuous improvement.

Communicate insights through data storytelling.

Connect improvement evidence to Learning Outcomes 8–12.

Learning Outcomes 8–12

Week Context & Goal

Iteration 2 moves from building into readiness, submission and retrospective. The week combines two loops: improve the product through review, QA and data-informed communication, and improve the team system through small experiments, more realistic estimates and reflection.

Weekly goal: deliver an evidence-backed Iteration 2 build, explain its value clearly, then convert feedback and retrospective findings into specific Iteration 3 actions.

Iteration Stage

Iteration 2 — continuous improvement → pre-deployment readiness → build submission → retrospective

Use desk-check, mentor, usability and QA evidence to improve the build.
Make assumptions and hidden work visible before estimating.
Present data as a defensible narrative: context → evidence → meaning → action.
Carry one proven process improvement and one product improvement into the next backlog.

This Week's Tasks & Important Deadlines

Mon 14 Sep, 11:55 PM AEST — Iteration 2 Pre-deployment Readiness — iteration resource
Thu 17 Sep, 11:55 PM AEST — Iteration 2 Build — iteration resource
Fri 18 Sep, 11:55 PM AEST — Retrospective & ePortfolio — iteration resource
Sun 20 Sep, 11:55 PM AEST — Reflective Diary (Weeks 5–8) — submission page
- Opens Tue 15 Sep at 8:00 AM.
- Moodle states late submission receives zero.
- AI and Generative AI must not be used for this assessment.

Reuse from Earlier Weeks

Week 6 — Data Storytelling: extend the existing audience/message foundation with narrative structure, chart choice and action-oriented evidence.
Week 7 — Story Points & Relative Estimation: use assumption checks and task unpacking to improve calibration.
Week 7 — Desk Checks: treat desk-check findings as inputs to PDCA and pre-deployment readiness.
Iteration 2 hub: carry mentor feedback, open risks and Definition of Done evidence into this week.

Knowledge Base

Continuous Improvement & Sustainable Focus

Data Storytelling — From Evidence to Action

Better Sprint Task Estimates — Assumptions & Unpacking

Apple Product Development — Process, Roles & Critical Reading

Week 5–8 Reflective Diary — Rules & Submission Checklist

Week 8 Seminar Capture

Studio 1

Before class

Continue Iteration 2 development and resolve readiness gaps.
Read Continuous Improvement.
Read The Pomodoro Technique and optionally use Pomofocus.
Read Mastering the Art of Data Storytelling.
Watch Two Ways to Create Better Sprint Task Estimates.
Review the official Reflective Diary instructions independently; do not use AI for the assessment.
Complete the Week 8 Pre-reading Quiz.

In class agenda

Pre-deployment readiness check.
Iteration Development workshop.
Review the Iteration 2 build and outstanding risks.
Confirm the Reflective Diary requirements and personal submission plan.

Evidence to leave with

Readiness evidence mapped to the Definition of Done.
Assumptions, dependencies and hidden QA/deployment work added to estimates.
One data story prepared to explain an Iteration 2 insight or outcome.
One product and one process improvement recorded for the retrospective.

Seminar

Guest lecturer: Moodle currently displays only “W”; confirm the full name in class.
Location: CL_25 Exhibition Walk, Room C1, Theatre (Building 63).

Capture three insights, the evidence/examples behind them and one decision relevant to the project.
Complete the Week 8 Seminar Quiz.

Historical recordings are linked inside Week 8 Seminar Capture; all three currently return an access-denied message for this account, so the notes page remains an in-class capture template.

Studio 2

Before class

Continue working on Iteration 2.
Complete the Moodle FeedbackFruits activity.
Read Apple’s Product Development Process.
Watch Data storytelling with animated graphs and charts.
Watch Telling Data Stories.
Prepare build evidence: features, tests, known limitations, deployment state and stakeholder value.

In class agenda

Submit and demonstrate the Iteration 2 build; marking occurs in class.
Run the retrospective.
Complete the ePortfolio evidence.

Evidence to leave with

Submitted Iteration 2 build and demonstration evidence.
Retrospective findings grouped into continue / change / stop.
Improvement actions have an owner, due point and observable result.
ePortfolio records contribution and learning evidence—not only artefact links.

Wrap-up

End-of-week review

Did the build satisfy the Definition of Done and readiness evidence?
Which feedback changed the product, and what evidence supports that change?
Which estimate was wrong, and which assumption or hidden task caused the error?
Did the data story make one clear claim without overstating the evidence?
Which retrospective action is already present in the next backlog?
Is the Reflective Diary independently completed and submitted before Sunday 11:55 PM?

Carry forward to Week 9

Mon 28 Sep, 11:55 PM AEST — Iteration 3 Discovery Presentation, including PGP — upload to the Project Governance folder.
Prepare for Industry Mentor Visit 4 — Iteration 2 Build Showcase in Studio 2.
Bring Iteration 2 feedback, quality evidence and improvement actions into Iteration 3 discovery.

课程目录