Nexus Learn

Lecture 5: Scrum

Lecture Notes SE-401 Software Engineering 14 min read Updated 8 Nov 2026

↓ Download notes (Word)

On this page
  1. §1 What is Scrum?
  2. §2 The Scrum framework at a glance
  3. §3 The Scrum team
  4. §4 Scrum artifacts
  5. §5 Scrum events
  6. §6 The sprint burndown chart
  7. §7 Scrum in practice
  8. §8 Worked activity: run your team on Scrum
  9. §9 Common mistakes
  10. Summary
  11. Word bank
  12. Self-check questions

How to use these notes: section numbers (§1.1, §1.2 ...) match the question bank. "Slide L05-S07" means slide 7 of this lecture. Difficult words are explained in "Word help" boxes and in the word bank at the end.

Learning outcomes

By the end of this lecture you should be able to:

SLO

Learning outcome

CLO

Bloom

Slides

SLO 5.1

Explain the three Scrum accountabilities (Product Owner, Scrum Master, Developers) and the three artifacts.

CLO1

C2 Understand

L05-S05 to S08

SLO 5.2

Describe the five Scrum events and their purpose and timeboxes.

CLO1

C2 Understand

L05-S09, S10

SLO 5.3

Read a sprint burndown chart and plan Scrum events for a student team project.

CLO4

C3 Apply

L05-S11, S12, S15

Lecture 4 gave us XP: practices for how programmers write code. Today we study Scrum, the most widely used agile framework. Scrum says how a team organises and manages its work: who decides what, how the work is planned in short sprints, and how the team checks its progress. You already have a Scrum board on Trello from Practical 2; today you learn the rules behind it.

§1 What is Scrum?

Slides L05-S02, L05-S05

§1.1 Recap: from XP to Scrum

Slide L05-S02

XP gave us user stories, test-first development, pair programming and continuous integration. These are engineering practices. Scrum adds the management side: roles, a fixed rhythm of meetings, and simple artifacts that make progress visible. Many real teams use Scrum for management and XP practices for engineering together.

Exit-ticket check: "As a student, I want a better app." has no clear goal, no benefit and cannot be tested. Better: "As a student, I want to see my order history so that I can repeat a meal I liked." Test: the last 10 orders are listed with date and total.

§1.2 Where Scrum came from

Slide L05-S05

The word comes from rugby: a scrum is when the whole team pushes forward together. In 1986 Takeuchi and Nonaka used it to describe fast product teams in Japan. Ken Schwaber and Jeff Sutherland presented Scrum for software in 1995. Today the official description is the short Scrum Guide (latest version 2020), free at scrumguides.org.

Scrum is a framework, not a full method: it gives a small set of rules and leaves the technical practices to the team. It is built on empiricism (learning from what actually happens), with three pillars:

Pillar

Meaning

Example

Transparency

The work and progress are visible to everyone.

The Trello board shows every story and where it is.

Inspection

The team checks its work and progress often.

A 15-minute daily meeting looks at the board.

Adaptation

When something is going wrong, the team changes its plan quickly.

A story is blocked, so the team moves another story forward.

Word help

framework = a basic structure with a few rules, which you fill with your own practices

empiricism = making decisions from what you observe and experience, not from guesses

§2 The Scrum framework at a glance

Slides L05-S06

§2.1 One sprint from start to finish

Slide L05-S06

1. The Product Owner keeps an ordered product backlog of everything the product might need.

2. In sprint planning, the team chooses a sprint goal and the backlog items to reach it. These form the sprint backlog.

3. During the sprint (one month or less; often two weeks) the Developers build the items. Every day they meet for a 15-minute daily scrum.

4. At the end, the team shows the finished increment to stakeholders in the sprint review.

5. Then the team holds a sprint retrospective to improve how it works. The next sprint starts at once.

Real-world example: a cricket season, one series at a time

The selectors keep a long list of players and plans for the season (product backlog).

Before each series, the captain and team pick a goal ("win the series 2-1") and the players for it (sprint backlog).

Every morning the team meets briefly (daily scrum); after the series they review results with the board (review) and discuss what to change (retrospective).

Word help

sprint = a short fixed period (one month or less) in which the team makes a usable piece of the product

increment = the new, working, tested piece of the product made in a sprint

§3 The Scrum team

Slides L05-S07

§3.1 Three accountabilities

Slide L05-S07

A Scrum team is small: usually 10 people or fewer, with no sub-teams and no job titles inside the team. The 2020 Scrum Guide calls the roles accountabilities:

Accountability

Main job

In the cafeteria app team

Product Owner (one person)

Maximises the value of the product. Creates, explains and orders the product backlog. Decides what is built next.

The student who talks most with the canteen manager and decides story priority.

Scrum Master

Makes Scrum work: teaches it, removes impediments (blockers), protects the team, makes sure events happen and stay in their timebox. A leader who serves, not a boss.

The student who books the meetings, keeps the daily scrum to 15 minutes and chases a missing API key.

Developers

Everyone who builds the increment: programmers, testers, designers. They plan the sprint backlog, keep quality with the Definition of Done, and decide how to do the work.

The other three students, who code, test and design screens.

Exam tip

The Product Owner decides what and in which order; the Developers decide how; the Scrum Master makes sure Scrum itself works. Nobody in Scrum is called "project manager".

Word help

accountability = a responsibility you must answer for

impediment = anything that blocks the team's progress

§4 Scrum artifacts

Slides L05-S08

§4.1 Three artifacts, each with a commitment

Slide L05-S08

Artifact

What it is

Its commitment (the goal it serves)

Product backlog

The ordered list of everything that might be needed in the product. It is never "finished".

Product goal: the long-term aim, e.g. "students order lunch without queues".

Sprint backlog

The sprint goal, the chosen backlog items, and the Developers' plan (tasks) to deliver them.

Sprint goal: one clear aim for this sprint, e.g. "a student can order and the kitchen can see it".

Increment

The working, tested result of the sprint, added to all earlier increments.

Definition of Done: the quality checklist every item must pass to count as done.

Backlog refinement is not a meeting in Scrum, but an ongoing activity: the Product Owner and Developers split, clarify and estimate items so they are ready for future sprints. This is what you did in Practical 2.

Word help

artifact = something the team makes that shows work or value

commitment = a goal the team promises to work toward

§5 Scrum events

Slides L05-S09 to L05-S10

§5.1 Five events and their timeboxes

Slide L05-S09

Every event has a timebox: a maximum length that must not be exceeded. Times below are for a one-month sprint; shorter sprints use shorter events.

Event

Purpose

Timebox

Sprint

The container for all other events; produces a usable increment.

One month or less (often 2 weeks)

Sprint planning

Answer three questions: why is this sprint valuable (sprint goal), what can be done, how will it be done.

Up to 8 hours

Daily scrum

Developers inspect progress toward the sprint goal and adapt the plan for the next day.

15 minutes

Sprint review

Show the increment to stakeholders, get feedback, update the product backlog.

Up to 4 hours

Sprint retrospective

Inspect how the team worked (people, tools, process) and pick improvements.

Up to 3 hours

Word help

timebox = a fixed maximum time for an activity

stakeholder = a person affected by the product, such as a user or the client

§5.2 A daily scrum, in practice

Slide L05-S10

Many teams answer three questions (Pressman calls this the Scrum meeting): What did I do yesterday toward the sprint goal? What will I do today? Is anything blocking me? The 2020 Scrum Guide no longer requires these exact questions, but they are a good start.

Real-world example: the cafeteria team, day 4

Ali: "Yesterday I finished the menu screen. Today I start the order screen. No blockers."

Sana: "I'm still on the kitchen queue. I'm blocked: I need the order data format from Ali."

Scrum Master: "Ali and Sana, meet for ten minutes right after this to fix the format." (Problem-solving happens after the daily scrum, not during it.)

§6 The sprint burndown chart

Slides L05-S11 to L05-S12

§6.1 Reading a burndown chart

Slide L05-S11

A burndown chart shows the work left in the sprint (story points) on the y-axis against the days of the sprint on the x-axis. The ideal line goes straight from the total on day 0 to zero on the last day. The actual line shows what really happened. It is not one of the three official Scrum artifacts, but most teams use it to make progress transparent.

Figure 6.1 Sprint burndown for the cafeteria team (20 points, 10 working days). Data checked in Python.

What you see

What it means

Actual line above the ideal line

The team is behind plan.

Actual line below the ideal line

The team is ahead of plan.

A flat segment

No story was finished that day: look for a blocker or a story that is too big.

Line does not reach 0

Some work is unfinished; it goes back to the product backlog.

§6.2 Worked example

Slide L05-S12

Question

Answer

On which days did the team finish nothing?

Days 1, 3 and 5 (the line is flat: 20→20, 18→18, 15→15).

On day 5, ahead or behind?

Ideal = 20 - 2 × 5 = 10 points left; actual = 15. Behind by 5 points.

What does 2 on day 10 mean?

A 2-point story was not finished. It is not counted as done; it goes back to the product backlog and is discussed in the review and retrospective.

What could the Scrum Master do on day 3?

Ask in the daily scrum what is blocking progress and help remove it (e.g. split a large story).

§7 Scrum in practice

Slides L05-S13 to L05-S14

§7.1 Scrum and XP together; the Scrum values

Slide L05-S13

Scrum

XP

Focus

Organising and managing the work

Engineering practices for writing code

Iteration

Sprint (one month or less)

Iteration of 1-3 weeks inside a release

Roles

Product Owner, Scrum Master, Developers

Customer (on-site), programmers, coach

Key practices

Planning, daily scrum, review, retrospective

Test-first, pair programming, refactoring, CI

The Scrum Guide lists five values: commitment, focus, openness, respect, courage. Notice the overlap with XP's values (respect, courage).

Word help

openness = being honest about the work and its problems

§7.2 Real-world example: a Pakistani software house

Slide L05-S14

Many software houses in Lahore, Islamabad, Karachi and Faisalabad build products for clients in the USA, UK or the Gulf. A typical set-up:

  • Two-week sprints planned on Jira; the client's representative acts as (or works closely with) the Product Owner.
  • Daily scrum at 10 a.m. Pakistan time, 15 minutes, on video for remote team members.
  • Sprint review over Zoom or Teams in the evening, because of the time difference with the client.
  • Retrospective inside the team every second Friday, with one improvement picked for the next sprint.

When a job advert asks for "experience in Agile/Scrum", this is what it means.

§8 Worked activity: run your team on Scrum

Slides L05-S15

§8.1 The task and a model answer

Slide L05-S15

In project teams (8 minutes): (1) choose your Product Owner, Scrum Master and Developers and give one reason for each choice; (2) write your Sprint 1 goal in one sentence; (3) place the Scrum events on a two-week calendar with realistic lengths for a student team; (4) name one impediment you expect.

Part

Model answer (cafeteria team of 5)

Roles

PO: Hira, who visits the canteen and knows the users. SM: Bilal, organised and good at keeping time (not the strongest coder, so he is not the "boss"). Developers: the other three; Hira and Bilal also develop.

Sprint goal

"A student can see the menu and place an order, and the kitchen can see it."

Calendar

Week 1 Monday: sprint planning (45 min). Every working day: daily scrum (10 min, after class or a WhatsApp call). Week 2 Friday: sprint review with the teacher as stakeholder (20 min), then retrospective (20 min).

Impediment

Members' class timetables clash; lab internet is slow; one member has no laptop. The SM plans around these.

Accept other choices with good reasons. The most important check: the Scrum Master is not a manager who gives orders, and the Product Owner is one person.

§9 Common mistakes

Slides L05-S16

§9.1 Five mistakes teams make

Slide L05-S16

Mistake

Correct idea

"The Scrum Master is the team's boss."

The Scrum Master serves the team and removes blockers; nobody gives orders in Scrum.

"The daily scrum is a status report to the manager."

It is a 15-minute planning meeting for the Developers, to adapt the plan for the day.

"We can add new work to the sprint any time."

The sprint goal does not change during the sprint; new work goes to the product backlog.

"The retrospective is optional when we are busy."

It is the main way the team improves; skipping it repeats the same problems.

"A half-finished story counts as half done."

Only items that meet the Definition of Done count. Unfinished work returns to the product backlog.

Summary

  • Scrum is an agile framework (Schwaber and Sutherland, 1995; Scrum Guide 2020) based on transparency, inspection and adaptation.
  • Three accountabilities: Product Owner (what and in which order), Scrum Master (makes Scrum work, removes impediments), Developers (how; build the increment).
  • Three artifacts with commitments: product backlog (product goal), sprint backlog (sprint goal), increment (Definition of Done).
  • Five events: sprint (≤ 1 month), sprint planning (≤ 8 h), daily scrum (15 min), sprint review (≤ 4 h), retrospective (≤ 3 h).
  • A burndown chart shows points left per day; above the ideal line = behind; flat = nothing finished.
  • Scrum manages the work; XP gives engineering practices. Many teams use both.
  • Before Lecture 06: read Pressman 5.5.2-5.5.4 (DSDM, Agile Modeling, AUP); in your team, assign Scrum roles on the Trello board and hold your first daily scrum. Quiz 1 next week covers Lectures 1-6.

Word bank

Word

Simple meaning

Example

Scrum

an agile framework for organising team work in short sprints

two-week sprints planned on Jira

framework

a basic structure with a few rules

Scrum gives roles, events and artifacts, not coding rules

empiricism

deciding from what you observe

changing the plan after seeing the burndown

Product Owner

the one person who orders the product backlog

decides payment comes in Sprint 2

Scrum Master

the person who makes Scrum work and removes blockers

chases a missing API key

Developers

everyone who builds the increment

programmers, testers, designers

impediment

anything that blocks progress

no internet in the lab

product backlog

ordered list of everything the product may need

all stories on the Trello Product Backlog list

sprint backlog

sprint goal + chosen items + plan

the Sprint 1 - To Do list with task checklists

increment

the working, tested result of a sprint

menu and ordering screens that work

Definition of Done

quality checklist for "done"

tested, reviewed, shown to the PO

timebox

fixed maximum time

daily scrum: 15 minutes

sprint review

event to show the increment to stakeholders

demo to the canteen manager

retrospective

event to improve how the team works

"next sprint we test earlier"

burndown chart

chart of work left per day

20 points on day 0, 2 left on day 10

Self-check questions

Try each question without looking. Then check your answer in the section shown.

#

Question

See

1

What are the three pillars of Scrum? Give an example of each.

§1.2

2

Describe the flow of one sprint in five steps.

§2.1

3

Who decides WHAT is built, and who decides HOW? What does the Scrum Master do?

§3.1

4

Name the three Scrum artifacts and the commitment of each.

§4.1

5

List the five Scrum events with their timeboxes for a one-month sprint.

§5.1

6

What three questions do many teams answer in the daily scrum?

§5.2

7

On a burndown chart, what does a flat line mean? What does a line above the ideal line mean?

§6.1

8

A sprint of 30 points over 10 days has 21 points left on day 5. Ahead or behind, and by how much?

§6.2 (ideal 15; behind by 6)

9

Give two differences between Scrum and XP.

§7.1

10

Why is "the Scrum Master is the boss" wrong?

§9.1

Further reading

  • Pressman & Maxim, 8th ed., section 5.5.1 (Scrum).
  • Sommerville, 10th ed., section 3.3 (Agile project management).
  • The Scrum Guide (2020), scrumguides.org: 13 pages, free.

← All SE-401 material