You are on page 1of 26

Scrum in Practice

Scope
Sprint Planning
- how to commit user stories from the product backlog
- how to estimate user stories
- how to breakdown the user stories in to task in the sprint backlog
- how to estimate task
- how to understand the customer or product owner requirements
through the Definition of Done (DoD)
Daily Scrum Meeting
- how the daily stand up meeting is done

Scope
Sprint Reiew
- demonstration of the output of the sprint
- mapping of the completed task against the DoD
Sprint Retrospectie
- !dentification of best practices
- !dentification of problems encountered
- !dentification of how to improe

Scrum "ycle

Sprint Planning

Poker planning using #ibonacci

Poker planning using #ibonacci

$bsolute s% Relatie &stimation

$bsolute s% Relatie &stimation

Product 'acklog
No. User Stories Story
Points
Status
(% #eature ( ) Done
*% #eature * (+ ,ot Started
+% #eature + + Done
-% #eature - . ,ot Started

Sprint 'acklog
Feature User Stories Man
Hrs.
Status
#eature ( /ask ( - Done
/ask * 0 ,ot Started
%
%
%
%
%
%
/ask , . Done

Definition of Done
#eature(1 2ogin !nterface
- the user should be able to create a new account
- the user should be able to change password
- accounts with more than + consecutie wrong
password should be blocked
- the password should be case sensitie with
atleast ) characters

Daily Scrum Meeting

Daily Scrum Meeting
3hat hae you finished yesterday4
- updates the /eam about the status of your
committed task
3hat will you do today4
- sets an indiidual commitment and goal
3hat are your problems
encountered4
- proides insights how a problem can be
soled

Scrum /ask 'oard

'urnDown "hart
Day 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10
0
100
200
300
400
500
600
Ideal
Actual

Sprint Reiew

Sprint Reiew
- demonstration of the team5s
accomplishments for the sprint
- auditing of the team5s delierable
against the Definition of Done
(DoD) that was set at the start of
the sprint

Sprint Reiew

Sprint Retrospectie

Sprint Retrospectie
- !mproed Productiity
- !mproed "apability
- !mproed 6uality
- !ncreased "apacity

Sprint Retrospectie
Retrospectie Structure1
(% Set the Stage
*% 7ather Data
+% 7enerate !nsights
-% Decide what to do
)% "lose the retrospectie

!n Practice

Requirements
"hat "lient
- create a simple chat application that allow
users from different computers to communicate
through typewritten messages
$! Program
- create a program that can answer atleast -
questions gien by the end user% /he questions
can be decided by the team

DoD
"hat "lient
- atleast + computers should be able to broadcast
messages to other users
$! Program
- the $! program should be able to answer questions
through keyword matching and punctuation marks%
6uestions gien by end users should be alid and
assumed gramatically correct% /he program should
still respond in case an inalid question was gien%

Mechanics
- 8ou hae )hrs to complete the task using
S"R9M
- /he (
st
hour will be the sprint planning
- /he *
nd
: +
rd
: -
th
hour of the e;ercise will sere as
your Daily Scrum Meeting
- /he )
th
hour will be the sprint reiew and
retrospectie