You are on page 1of 25

Agile software development with Scrum

Przemysaw Bielicki June 2008

What is Scrum?

What is Scrum?

Scrum and XP from Trenches Scrum Primer Scrum on Wikipedia Scrum and XP in Atlassian Agile RSS and Scrum Alliance RSS

Scrum roles

Product Owner

Proxy etween customer and the team PO can customer or !arketing rep

"e#elopment Team Scrum !aster

Scrum Team

Self$managing and self$organi%ing &p to '( people )ross functional *d admin+ we designer+ tester+ etc,.igger pro/ect 0 more Scrum teams )ollocated team *couple of teams can work in different locations-

Scrum guidelines

1stimation Planning .acklogs 2teration *sprint- from 3 to 4 weeks

"aily Scrum *standup meeting-

"emo 2teration re#iew

Scrum guidelines

Self$management

There is no imposed leader 1#ery ody is responsi le for the success of the pro/ect "eli#er early and often "emo at the end of each iteration

On$site client proxy is possi le


Scrum guidelines

Iteration / Sprint

1stimating and Planning *4h 5 4h

"efine goal of the iteration


What have you done on this project since the last Daily Scrum meeting? What do you plan on doing between now and the next DS meeting? What impediments stand in the way of you meeting your commitments to this Sprint and the whole project?

"aily Scrums

"emo *4hRetrospection post$mortem *4h-

Estimation

10

Estimation

&ser stories

6As a user 2 want to 7 in order to 78 Acceptance criteria 9 how to demo it: A stract si%e *not time re;uired to complete the tasks(+ '+ 3+ <+ =+ '>+ 3'+ '(( 6<8 is twice as complex as 638

Story points

11

Planning

Planning poker Release planning *user stories le#el2teration planning *task le#el

Time9effort estimation in days !inimum unit is (,< day !aximum unit is 3 > days

12

Backlogs

Product acklog

&ser stories 1pics &ser stories Tasks .ugs

2teration acklog

13

Iteration Burndown

14

Team elocit!

?ow to measure: )an we include stories @(A done: )an we increase it: )an we work o#ertime: What #elocity will we ha#e in the next iteration:

15

Team "esponsi#ilit!

6We are all in this together8 A#oid 6hit$ y$the$truck8 factor A#oid 6itBs his9her fault8 situation )onfront pro lems and 6smelly8 decisions foster constructi#e conflict Support other team mem ers

16

Scrum vs$ Waterfall


2terati#e and incremental process )an stop at any time if there is a pro lem "ocumentation: definition of 6done8 .etter prepared for changes .etter react on changes

17

Scrum and %P

O#erlapping concepts Work good together )ommunication+ Simplicity+ Ceed ack+ )ourage+ Respect #s, Scrum

18

&anager vs$ Scrum &aster


!anager dri#es the team Deader ser#es the team Scrum !aster can e de#eloper at the same time Scrum !aster is the Deader

19

'eadership

!anager has to ecome leader Deader ser#es team mem ers Deader has to co#er up the team Deader is a role model

20

Introducing Scrum (pros)


.etter communication Caster de#elopment .etter team relations .etter producti#ity

21

Introducing Scrum (cons)


Eot e#ery ody likes that way of working !anagers sometimes donBt like the change Eot e#ery manager is a Deader ser#ant mode ?ard to con#ince that the change will pay off

22

Scrum is a#out*

7 accepting uncertainty 7 working as a team 7 deli#ering early and often 7 constant estimating and planning 7 keeping sustaina le work pace 7 self managing work en#ironment 7 ha#ing fun working

23

Scrum is a#out*

24

+ontact me

p ielickiFgmail,com httpG99/a#a3/ee, logspot,com

25

You might also like