CHC5056 Innovative Product Development · Semester 1, Week 6

The Scrum
Framework and Roles

Who decides what in a Scrum Team?
Five classmates spent four weeks building a canteen app.Nobody outside the team saw it until the demo.
Session45 minutes
OpensThe delivery phase
Followed byWeek 7: Sprint Planning
Learning outcomes

Four Things You Will Be Able to Do

01
Explain, using one example, how short cycles of transparency, inspection and adaptation help a team find problems early.
Exit answer
02
State what the Product Owner, Scrum Master and Developers each decide, and what each should not do.
Individual Journal
03
Trace how one piece of work moves from Product Backlog to Sprint Backlog to Increment, and who is accountable at each step.
Seminar working agreement
04
Recommend a response to a mid-Sprint interruption that respects each accountability.
Main activity
Learning outcomes · 0 to 1 min
The case

A Canteen App, Five Classmates

Order canteen food in advance, pick it up at a chosen time, and skip the lunch queue.
ProductA mini-program
TeamFive Year 2 classmates
UsersStudents on campus
ClientThe canteen manager
Fictional teaching case
Story · 1 to 5 min
Before Scrum

The Plan, and Four Weeks of Silence

Week 1

One leader, five parts

Leo calls himself leader and assigns the parts.

Weeks 1 to 4

Everyone codes alone

Nobody asks the canteen for menu data.

Last days

Testing at the end

Nothing reaches a user until the demo.

Four weeks of work, no feedback from outside the team.

Silence
Story · 1 to 5 min
The demo

Three Things Went Wrong at the Demo

01

The canteen manager cannot see orders in time.

The client
02

Students ask where the pick-up time choice is.

The users
03

Two weeks went on a rating feature nobody requested.

The team
When could they have found out?
Hold this question
Story · 1 to 5 min
Why Scrum

Work in Short Sprints

Before
One delivery, at the end.
Four silent weeks, then a demo that surprises everyone.
With Scrum
A delivery every two weeks.
Each Sprint ends with something a user can try.
Scrum is a framework for working in short cycles called Sprints.
Why Scrum · 5 to 12 min
Why Scrum

Show It, Check It, Change the Plan

The three pillars of Scrum as a repeating cycle Show the work, then check it, then change the plan, and the cycle repeats every Sprint. Transparency is shown in week one, Inspection in week two, Adaptation in week three. 01 Show the work. The plan and the code are visible. TRANSPARENCY week 1 02 Check it. Someone outside the team tries it. INSPECTION week 2 03 Change the plan. The next Sprint is different. ADAPTATION week 3 NEXT SPRINT
AskWhich week would the missing menu data have surfaced?
Why Scrum · 5 to 12 min
Scrum values

Two Values That Would Have Changed This Story

Openness
Say "we have no menu data" in week one.
What Leo's team did not do
Courage
Tell Leo the rating feature is not wanted.
Two weeks that could have been saved
Also named today, not explained: commitment, focus, respect.
Why Scrum · 5 to 12 min
Accountability 1 of 3

Product Owner: Decides What and Why

In the case: Mei
Mei decides what to build, why it matters, and in what order.
Decides
What to build, why, and the order of the work.
In the case
Talks to students and to the canteen manager.
Does not
Assign tasks to Developers.
Accountabilities · 12 to 27 min
Accountability 2 of 3

Developers: Decide How

In the case: everyone who builds
The Developers decide how to build it, to an agreed quality.
Decides
How the work gets done, and to what quality.
In the case
Choose their own tasks each Sprint.
Does not
Wait for tasks. A UI designer is a Developer.
Accountabilities · 12 to 27 min
Accountability 3 of 3

Scrum Master: Helps, Does Not Boss

In the case: Sam
Sam helps the team use Scrum well, and removes what blocks them.
Does
Helps the team use Scrum well, and removes blockers.
In the case
Gets the menu data problem solved in week one.
Does not
Manage people, or assign work.
Accountabilities · 12 to 27 min
Comparison

Not a Project Manager, Not a Team Leader

Scrum MasterProject Manager
AuthorityNo authority to assign workAssigns work to people
FocusHow well the team uses Scrum, and removing blockersDeliverables, deadlines and budget
Success looks likeThe team solves its own problems more oftenThe plan was delivered on time
Leo assigned the parts. In Scrum, no role does that.
Accountabilities · 12 to 27 min
One Sprint

Follow One Item Through One Sprint

One item moving from Product Backlog to Sprint Backlog to Increment The item choose pick-up time sits in the Product Backlog, ordered by the Product Owner, then moves at Sprint Planning into the Sprint Backlog, planned by the Developers, then becomes an Increment the Developers finish and a student can try. ARTEFACT 01 Product Backlog Everything we might build. Choose pick-up time ACCOUNTABLE: PRODUCT OWNER Ordered by Mei ARTEFACT 02 Sprint Backlog Chosen for this Sprint. Choose pick-up time ACCOUNTABLE: DEVELOPERS Planned by the team ARTEFACT 03 Increment A student can try it. Choose pick-up time ACCOUNTABLE: DEVELOPERS Finished and usable SPRINT PLANNING who is accountable? DURING THE SPRINT who is accountable? THE SPRINT CONTAINS Sprint Planning  /  Daily Scrum  /  Sprint Review  /  Sprint Retrospective Week 7
Text version of the diagram

The item "choose pick-up time" sits in the Product Backlog, ordered by the Product Owner. At Sprint Planning it is pulled into the Sprint Backlog, planned by the Developers. During the Sprint the Developers build it, and it becomes an Increment that a student can try. The Sprint contains Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective.

One Sprint · 27 to 35 min
Activity

“Add a Banner by Friday”

Halfway through a two-week Sprint
The canteen manager meets one Developer and says: “Add a Today's Special banner by Friday. It's easy, right?”
Four days left in the Sprint, and nobody else knows.
Take one role
Product Owner
Scrum Master
Developer
What should this person do, and what should they avoid doing?
04 in pairs03 to collect
Activity · 35 to 42 min
Close

Three Things to Take Away

01

Short cycles surface problems early.

02

Three accountabilities, three different decisions.

03

Work flows from backlog to backlog to Increment.

Exit: in your own project team, who is the Product Owner, and what is one thing they should NOT do?
One sentence
on the way out

Seminar: confirm who holds each accountability, then draft a working agreement.

Next week: Sprint Planning and Daily Scrum.

Close · 42 to 45 min

Speaker notes