#
Scrum in a Nutshell
Product Owner
+ Owns the Product Backlog as he/she
has to maximize the ROI ofthe Product,
“Is responsibie to define the content
+ Discusses and agrees with the Stakeholder
what todo, an wry.
+ Discusses and agrees with the Development.
Team how to represent in the backlog what
reeds to be done,
+ The Product Backlog is an ordered lst of tems
(e.g: MMF, usor stories...)
+ Tha items in the Product Backlog include
features that dalver the Product Vision
+ Tha highest prioritized items need tobe better
+ Tha ist of tems is constantly evohing,
detailed and specified - the tear needs
to be abe to estimate and test these tems.
‘changing and updating, the Procuct
‘Owmeris responsible to make sure the
Produet Backlog reflects these changes.
+ The SM faciitats the Sprint Planning Meeting
+ Te PO presents the Product Backiog tothe
tear, inorder of priority.
+ Backlog tems are often writen as user stores
+ The team togethor withthe PO clarifies all
Questions around the user stories, as needed.
+ Te development team estimates the effort,
needed per user-story and decides which stories
can be committed for tho next sprit
+ This meeting is time-boxed fo a maximum of the
5% of the sprint lath,
(e.g: 1/2 day fora2 wooks sprint)
«Aecepis oj tne resus of Spr
Development Team
sieacresstunctonal team, gy @
mmecnng every seeds to Om
Crea potonaly shppable
product eremet ust bein
{hoteam ts normaly sized around 722
members
-[orenponabe for he Product Quaty
“Detne howto mplerent the fonetenates
iio te Product
-Propres the Spt Review meeting and
periorns Sprint Retospectives "0 prove
tirioney.
Seria
ete
+ The Sprint Backlog isa list of items whicn are
“Tha tems for the Sprint Backiog are taken out of
+The tems in the Sprint Backlog are broken down
+ Evary team member can modi the
Sprint Backiog, (ea faacro)
+ Works never assigned, but puted |] ea
‘ut of the backlog by the indivuals. [a]
“Items not completed ina sprint are [EN
Committed to be accomplished during the sprint
the Produ
Backiog
Into tasks by the toam members
rot moved tothe next spin, but
tare retumed into the Product Sacklog instead.
+The team mests daly forthe Daly Serum, or
aly stand-up meeting, where they coordinate
their work and communicate impaciments tothe
‘Serum Master.
+ Each team member tak to the three questions:
+ What dd you do (achieve) yesterday?
+ Wat impediments got on your way?
+ What are you going to do today?
+The Dally Scrum is also called Dally Stancup,
fas people stand rather than siting to keep the
fects, ts tme-boxed t0 15-20 mins,
+ The quality of the Burndown increases if the
+ Gathering point forthe Daly Scrum.
+ Updated any time during day and
‘The Burndown Charts an Informatio radiator,
it visualizes the estimated work remaining within
the Sprint. The remaining effort can be estimated
in ideal days/hours, or in story pont.
effort is bumed down when @ task or a story is
completes
right, not only during Daly Serum
+ The SM moderates the Sprint Review Meeting
+ The Development Team presen the working
software they bul tothe Product Owner and
any other stakeholders.
+The PO accepts or rejects work based on the
Aeceptance Criteria that was agreed former in
the Sprint Planning Meeting
+ Tho purpose of the Retrospective isto
Continuously improve tho way of working
+ Te Sorum Mastor faites the mating,
+The Development Team can decide if tis holful
‘or not for tho Product Owner to attend tho
retrospective.Scrum in a Nutshell