Scrum is a framework for project management that focuses on iterative development, self-organizing teams, and frequent inspection points. It involves roles like the product owner, scrum master, and development team. The team works in sprints of fixed duration to develop working software incrementally based on prioritized user stories in the product backlog. Daily stand-up meetings, sprint reviews, and retrospectives provide transparency and opportunities to inspect progress and improve the process.

1. How does work?SCRUM
SCRUM MASTER
ELEMENTS
1. ROLES
3. TOOLS2. ACTIVITIES
- planning releases
- refinement
- planning a sprint
- sprint
- daily meetings
- sprint review
- scrum retrospective
TEAM SCRUM MASTER PRODUCT OWNER
- backlog
- burndown charts
SCRUM is a set of rules concerning project management.
It’s clear It’s flexible Educates It’s effective Helps coping with
unpredicted factors
It’s Easy
STEADY W
ORK RHYTHM
TIMEFRAMES
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
PRODUCT OWNER
IDEA
PRODUCT PROCESS
SELF-ORGANIZATIONADAPTATION
(CONTINUOUS IMPROVEMENT)
INSPECTION
(FEEDBACK)
CLARITY
(COMMUNICATION)
TRUST
TEAM
WHAT IS
SCRUM?
TWICE AS MUCH,
TWICE AS FAST
or
PRODUCT
OWNER
PRODUCT
REGISTRY
SPRINT
USER STORY
SCRUM BOARD
USER STORY TASK
US1 T5
T5
T6
T4
T4
T4
T3
T3
T3
T2
T2
T2
T1
T1
T1
US2
US3
Scrum’s origins are dated to 1986, but its first formal documentation was created in 1995.
Scrum is named after a rugby tactic, and was designed to help manage projects with hard
to predict outcomes.
Meaning:
It helps with
Context User experience Priorities
Plot Understanding main character’s situation Understanding goals and needs
• The team identifies with the end user.
• The team engages in searching for the best solution.
TEMPLATE:
As a <user_name> I would like to
<action> to <reason>
EXAMPLE:
As a system administrator I want to login to
the admin panel to manage the site.
What’s what in scrum?
GLOSSARY
Release – pushing a finished fragment of the project. Preceded by sprint.
User story – the smallest measurable functionality, generating a business advantage.
Sprint (Iteration) – process which aims to produce a functioning fragment of the
product. During the sprint a team completes all the tasks necessary to achieve this goal.
To ensure good realization of a sprint the team must understand the user stories.
Refinement – a reflection before the next sprint. During refinement we explain the
user stories for a next sprint. Welcome, but not necessary.
Burndown – shows the work progress during a sprint. Visualized by burndown charts
which depict the amount of work left.
Sprint retrospective – a meeting at the end of iteration, dedicated to refining the
process. Any conclusions from the retrospective will be implemented during the next
sprint.
Definition of done – the quality metric for a delivered peace of code. It defines what
(apart from finishing the task) has to be done, to consider the functionality complete
(e.g. code review, performance testing).
Sources:
T. Włodarek, Pragmatic methods of software production,
http://www.slideshare.net/tomek_w/scrum-w-59-minut?from_action=save
What is Scrum?,
http://procognita.pl/nc/zasoby/artykuly/czytaj/artykul/co-to-jest-scrum-58/
Our own experience :)
SPRINT
BACKLOG
SPRINT PRODUCT
7 days
24 h
(ALL STORIES)