4.2Scrum: roles, events & artifacts
The essentials in 30 seconds
- Sprints of 1 to 4 weeks, each delivering a usable increment.
- 3 roles: Product Owner (value), Scrum Master (facilitates), team (delivers).
- Reflex: 5 events + 3 artifacts = a continuous improvement cycle.
Running case — Bilal launches his first sprint
After his shift (4.1), Bilal structures his team: Amine becomes Product Owner (he prioritizes), Bilal facilitates as Scrum Master, and the team delivers in 2-week sprints. First goal: a usable increment at the review, then a retro with one concrete improvement.
Sequel to case 4.1 — Bilal moves from mindset to a paced framework.
1. Sprints that deliver
Scrum is the most used agile framework. It organizes work in sprints — short, regular iterations (1 to 4 weeks) — at the end of which the team delivers a usable product increment.
Its strength: a simple, paced framework — 3 roles, 5 events, 3 artifacts — structuring collaboration without weighing it down.
2. Roles, events, artifacts
Roles: Product Owner (carries value, prioritizes the backlog), Scrum Master (facilitates, removes obstacles), development team (delivers).
Events: sprint, planning, daily, review, retrospective. Artifacts: product backlog, sprint backlog, increment. Together, a continuous improvement cycle.
🔎 Concrete example — 🔎 Concrete example — Scrum Master is NOT the boss
A servant-leader.
The Scrum Master has NO hierarchical authority.
They facilitate, remove obstacles, protect the team, foster self-organization.
→ “servant-leader”, not a manager handing out tasks.Outcome: a self-organized, paced team.
Reflex: one concrete improvement at each retrospective.
Section vocabulary
- Scrum
- An agile framework organizing work in sprints, with 3 roles, 5 events and 3 artifacts.
Simple example: Bilal runs his team in 2-week sprints with review and retro.
What it is not: a method removing all meetings and tracking.
Reflex: count: 3 roles, 5 events, 3 artifacts — if one is missing, it is no longer Scrum.
- Sprint
- A fixed-duration iteration (1-4 weeks) ending with a usable increment delivered.
Simple example: Bilal's sprint ends with a usable demo in front of the client.
What it is not: a variable-length period extended when late.
Reflex: fixed duration, never extended: adjust content, not time.
- Product Owner / Scrum Master
- PO: carries value, prioritizes the backlog. SM: facilitates, protects the team, removes obstacles.
Simple example: Amine rules on priorities; Bilal unblocks access to the client.
What it is not: two bosses sharing task distribution.
Reflex: PO = the what (value); SM = the how of the framework.
- Daily / Review / Retrospective
- Daily: the daily sync point. Review: the increment demo. Retro: team improvement.
Simple example: Bilal holds the review (what is delivered) then the retro (how to work better).
What it is not: three reporting meetings to hierarchy.
Reflex: review = product; retro = team; daily = today's blockers.
- Backlog / increment
- Product backlog: the prioritized work list. Increment: the finished, usable product part per sprint.
Simple example: Bilal's backlog is prioritized; his increment runs at the client.
What it is not: a progress report or forecast schedule.
Reflex: no usable increment = missed sprint, even with hours done.
In practice — In practice — Simulating a Scrum cycle
- Assign the 3 roles on a fictional project: who is PO (prioritizes), Scrum Master (facilitates), team (delivers)?
- Build a prioritized product backlog, then select what fits in a first sprint (sprint backlog).
- Pace the sprint: planning at the start, daily each day (done / to do / blockers), review and retrospective at the end.
- At the review, identify the deliverable increment; at the retro, note one concrete improvement for the next sprint.
Ready-to-say script — framing first-sprint roles (1 min)
"For this 2-week sprint: Amine is Product Owner, he rules on backlog priorities. I am Scrum Master: I facilitate, I remove blockers, I do not hand out tasks. The team self-organizes to deliver a usable increment at the review. At the retro, we decide on a single improvement for the next sprint."
To say at kick-off: naming the 3 roles stops the Scrum Master being taken for the boss.
Copy-paste template — Scrum sprint sheet
SPRINT No.__ — DURATION: __ weeks (fixed)
PO (prioritizes): _______________ | SM (facilitates): _______________
SPRINT BACKLOG (content): _______________
TARGET INCREMENT (usable): _______________
REVIEW (date + demo to whom): _______________
RETRO (1 decided improvement): _______________Very small business / tight budget
3 people are enough: a part-time PO, a facilitator, a 2-week sprint with a client demo.
Remote team
A short daily video call at a fixed hour, shared online backlog: pace offsets distance.
SME in Algeria
Bilal protects the client review from hazards (travel, outages) by scheduling it on sprint day 1.
Continuous flow (support)
If requests flood in with no possible sprint goal, prefer Kanban (4.3) over forcing Scrum.
✓ Best practices
- Deliver a truly usable increment at each sprint.
- Hold the retrospective: one concrete improvement per cycle.
- Let the Scrum Master facilitate, not command.
✗ Common pitfalls
- Taking the Scrum Master for the hierarchical boss.
- Ending a sprint with no usable increment.
- Applying rituals without the self-organization spirit.
Key takeaways
- Scrum organizes work in sprints delivering a usable increment.
- 3 roles: Product Owner, Scrum Master, development team.
- 5 events: sprint, planning, daily, review, retrospective.
- 3 artifacts: product backlog, sprint backlog, increment.
48h challenge — apply tomorrow
Assign the 3 roles on your project (PO, Scrum Master, team) and launch a 2-week sprint with a dated review (template above).
- I can cite the 3 roles and their mission without hesitating.
- I know what a sprint delivers (a usable increment).
- I assigned the 3 roles and dated a review.
Frequently asked questions
What is the difference between the Product Owner and the project manager?
The Product Owner focuses on VALUE: they define and prioritize the what (the backlog) to maximize product benefit. The traditional project manager role (scheduling, coordination, control) is partly redistributed in Scrum (to the SM, to the self-organized team). In practice, many organizations keep a project manager coordinating several teams or the link with predictive. So roles do not exactly overlap.
Is the Scrum Master the team boss?
No, it is a common mistake: the Scrum Master has no hierarchical authority. They are a facilitator serving the team — helping it apply Scrum, removing obstacles, shielding it from disruption and fostering self-organization. It is a “servant-leader” role, not a manager handing out tasks. Confusing both recreates a boss where Scrum wants a self-organized team.
What does a Scrum team deliver at a sprint's end?