Nexus Learn

Lecture 5: Scrum

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

↓ Download slides (PowerPoint)

Slide 2

Last lecture: XP, and your exit tickets

Weak: "As a student, I want a better app."

  • XP in one line
  • Five values (communication, simplicity, feedback, courage, respect) and engineering practices: user stories, test-first, pair programming, refactoring, continuous integration.

Better: "As a student, I want to see my order history so that I can repeat a meal I liked." Test: last 10 orders listed with date and total.

Today: XP tells programmers how to code. Scrum tells the team how to organise and manage the work. Many teams use both.

Word help

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

SE Lecture 5

Recap

Sheet 02 of 19

Slide 3

Learning outcomes

SLO 5.1

Explain the three Scrum accountabilities and the three artifacts

→ CLO1 · C2 Understand

SLO 5.2

Describe the five Scrum events, their purpose and timeboxes

→ CLO1 · C2 Understand

SLO 5.3

Read a sprint burndown chart and plan Scrum events for your team

→ CLO4 · C3 Apply

  • CLO1: Explain application of software engineering processes and techniques to various types of software.
  • CLO4: Explain basic concept of project management.

SE Lecture 5

Outcomes

Sheet 03 of 19

Slide 4

Today's plan: 50 minutes

0-5 min

Recap and exit tickets

This week

5-8 min

Outcomes and plan

  • Lecture 06: Kanban and other agile models
  • Practical 05: run a sprint, draw a burndown
  • Practical 06: Kanban board

8-21 min

What Scrum is; the team; the artifacts

21-32 min

Events, daily scrum, burndown chart

32-35 min

Scrum with XP; Scrum in Pakistan

35-43 min

Activity: run your team on Scrum

43-48 min

Common mistakes and recap quiz

48-50 min

Homework and exit ticket

SE Lecture 5

Plan

Sheet 04 of 19

Slide 5

What is Scrum?

  • Scrum is an agile framework for organising a small team's work in short, fixed periods called sprints.
  • Ken Schwaber and Jeff Sutherland, 1995. Official rules: the Scrum Guide (2020), 13 free pages.

Three pillars

Transparency

Everyone can see the work: the board shows every story.

Inspection

Check progress often: a 15-minute daily meeting.

Named after rugby: the whole team pushes forward together.

Adaptation

Change the plan quickly when something goes wrong.

Word help

empiricism = deciding from what you actually see

Scrum is a framework: it gives a few rules, not coding practices.

SE Lecture 5

What is Scrum

Sheet 05 of 19

Slide 6

One sprint, from start to finish

→

→

→

→

Product backlog

Sprint planning

Sprint backlog

Sprint (≤ 1 month)

Increment

Ordered list of everything (PO)

Pick a sprint goal and items

Goal + items + plan

Daily scrum every day

Working, tested result

Sprint review (show it) → Retrospective (improve) → next sprint

Real-world example: a cricket series

Selectors keep a season plan (product backlog). Before a series the team picks a goal and players (sprint planning). Short team talk every morning (daily scrum). After the series: results to the board (review), then what to change (retrospective).

SE Lecture 5

Framework

Sheet 06 of 19

Slide 7

The Scrum team: three accountabilities

Product Owner

Scrum Master

Developers

ONE person. Orders the product backlog and decides WHAT is built next.

Makes Scrum work: teaches it, removes impediments, keeps timeboxes. Serves the team; NOT a boss.

Everyone who builds: code, test, design. They decide HOW and plan the sprint backlog.

Hira: talks to the canteen manager

Bilal: books meetings, chases a missing API key

Ali, Sana, Usman: build and test screens

Team size: usually 10 people or fewer. No "project manager" in Scrum.

Word help

accountability = a duty you must answer for impediment = anything that blocks the team

SE Lecture 5

Scrum team

Sheet 07 of 19

Slide 8

Three artifacts, each with a commitment

Product backlog

Ordered list of everything the product might need. Never finished.

→

  • Product goal
  • "Students order lunch without queues"

Sprint backlog

Sprint goal + chosen items + the Developers' task plan.

→

  • Sprint goal
  • "A student can order; the kitchen sees it"

Increment

The working, tested result of the sprint.

→

  • Definition of Done
  • Tested, reviewed, shown to the PO

On your Trello board: Product Backlog list = product backlog; Sprint 1 - To Do = sprint backlog; Done list (passing the Definition of Done card) = increment.

SE Lecture 5

Artifacts

Sheet 08 of 19

Slide 9

Five events, each with a timebox

*for a one-month sprint; shorter sprints use shorter events. The sprint goal does not change during the sprint.

Word help

timebox = a fixed maximum time stakeholder = anyone affected by the product, e.g. users, the client

SE Lecture 5

Events

Sheet 09 of 19

Slide 10

A daily scrum: 15 minutes, standing up

Ali

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

  • Three common questions
  • What did I do yesterday?
  • What will I do today?
  • Is anything blocking me?

Sana

"Still on the kitchen queue. 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."

Rule: the daily scrum is for planning the day, not for solving problems or reporting to a boss. Problems are solved right after it, by the people involved.

SE Lecture 5

Events

Sheet 10 of 19

Slide 11

The sprint burndown chart

  • Actual above ideal
  • Behind plan
  • Actual below ideal
  • Ahead of plan
  • Flat segment
  • Nothing finished that day: look for a blocker
  • Does not reach 0
  • Unfinished work returns to the product backlog

Cafeteria team, Sprint 1: 20 points, 10 working days.

SE Lecture 5

Burndown

Sheet 11 of 19

Slide 12

Quick check: read the chart

A

On which days did the team finish nothing?

Days 1, 3 and 5 (flat: 20→20, 18→18, 15→15)

B

On day 5, ahead or behind? By how much?

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

C

What does 2 on day 10 mean?

A 2-point story is not done; it goes back to the product backlog

D

What should the Scrum Master do on day 3?

Ask about blockers in the daily scrum; help split a big story

Answer each question before your teacher reveals it.

SE Lecture 5

Burndown

Sheet 12 of 19

Slide 13

Scrum and XP work together

  • Five Scrum values
  • Commitment
  • Focus
  • Openness
  • Respect
  • Courage

In industry: "Scrum + XP" is a very common mix. Scrum runs the sprints; XP practices keep the code clean and tested.

SE Lecture 5

Scrum and XP

Sheet 13 of 19

Slide 14

Scrum in a Pakistani software house

Job adverts say "experience in Agile/Scrum". This is what they mean: you know the roles, events and artifacts, and you have worked in sprints.

Real-world example: Lahore team, UK client

  • Two-week sprints planned on Jira.
  • Daily scrum at 10 a.m., 15 minutes, on video for remote members.
  • Sprint review with the client on Zoom in the evening, because of the time difference.
  • Retrospective every second Friday: one improvement for the next sprint.

Your semester project will run the same way: two-week sprints, your teacher as a stakeholder at each sprint review.

SE Lecture 5

Real world

Sheet 14 of 19

Slide 15

Activity: run your team on Scrum

In your project teams:

Choose your PO, Scrum Master and Developers. One reason each.

Write your Sprint 1 goal in one sentence.

Put the five events on a 2-week calendar, with real lengths.

minutes

Name one impediment you expect.

  • 6 min in teams
  • 2 min to share

SE Lecture 5

Activity

Sheet 15 of 19

Slide 16

Common mistakes

"The Scrum Master is the boss."

✗

SM serves the team and removes blockers

"Daily scrum = report to the manager."

✗

15-minute planning for the Developers

"Add new work to the sprint any time."

✗

Sprint goal is fixed; new work → product backlog

"Skip the retrospective when busy."

✗

It is how the team improves

"Half-finished story = half done."

✗

Only items meeting the Definition of Done count

SE Lecture 5

Mistakes

Sheet 16 of 19

Slide 17

Recap quiz: hands up

Who orders the product backlog?

How long is the daily scrum?

Which event shows the increment to stakeholders?

Which commitment belongs to the sprint backlog?

On a burndown chart, what does a flat line mean?

SE Lecture 5

Recap quiz

Sheet 17 of 19

Slide 18

Before the next lecture

Read

Team task

Pressman 5.5.1 (Scrum) and Sommerville 3.3. Skim Pressman 5.5.2-5.5.4 for Lecture 06.

  • Add a "Scrum Team" card: PO, SM, Developers
  • Write the Sprint 1 goal on the board
  • Hold your first daily scrum (WhatsApp call is fine)
  • Practical 05 uses your board to draw a burndown

Quiz 1 next week

Covers Lectures 1-6: process models, agile, XP, Scrum, other agile models.

SE Lecture 5

Homework

Sheet 18 of 19

Slide 19

Exit ticket

On a small piece of paper, with your name and roll number:

Which Scrum role will you take in your team, and what is ONE thing that role must NOT do?

One question you still have.

Questions?

SE Lecture 5

Exit ticket

Sheet 19 of 19

← All SE-401 material