Agile Scrum Introduction

c Quc - ducquoc.vn@gmail.com ( Twitter & SlideShare: ducquoc_vn )

Outline

Software development processes Scrum benefits Scrum roles Scrum artifacts Scrum daily stand-up Scrum planning Scrum review & retrospective Q&A

Outline

Software development processes Scrum benefits Scrum roles Scrum artifacts Scrum daily stand-up Scrum planning Scrum review & retrospective Q&A

Processes
Theory + Experiments + Practices

Expericence (good practices & bad ones)

Theory to utilize & promote good practices (PROCESS)

Processes - Software Development

200 3 Waterfall UML 200 4 200 5 CMMi Unified Process Continuous Integration 200 6 TL9000 200 7 200 8 TDD

XP

Scrum

Lean Kanban Prince2

Processes - Waterfall
Requirement s Requirement s Analysis Architecture Design Detail Design Implementati on Testing Maintenance

Processes - Waterfall works?

The software factory

7

Processes - Waterfall with feedback

Requirement s Requirement s Analysis Architecture Design Detail Design Implementati on Testing Maintenance

Processes - Iterative & Incremental

Requirement s Quick Design Refine & Rework Evaluation & Update Implementati on

Final Testing

Release
9

Processes - Agile methodologies

10

Processes - Agile Scrum

200 3 Waterfall UML 200 4 200 5 CMMi Unified Process 200 6 TL9000 200 7 200 8 TDD

XP

Agile
Continuous Integration

Scru m

Lean Kanban Prince2

11

Outline

Software development processes Scrum benefits Scrum roles Scrum artifacts Scrum daily stand-up Scrum planning Scrum review & retrospective Q&A

12

Scrum benefits - project

Visibility Ability to Change

Business Value

Risk

13

Scrum benefits - company

Use Scrum? - Google - Facebook - Amazon - Twitter - IBM - DropBox - Salesforce - Intel - Yahoo - Nokia - Microsoft - GE - Time Warner - Lockheed Martin - Electronic Arts -
14

Scrum benefits - case study

2006: Sentinel project awarded to Lockheed Martin, 4 phases, $450m, 6 years. 2010, after four+ years, $421 spent and 1st phase and part of 2nd done. Mitre estimates another $351m and 6 years to complete.

FBI stops contract and brings in house. Scrum studio in Hoover building basement, reduce staff from 400 to 40. Project done in 1 year for $30m. (source: www.justice.gov Inspector General reports)

15

Scrum benefits - simple

Certifications: CSM (course price: 1795 EUR for 2 days), PSM (500 $ for 120 minutes) 16

Outline

Software development processes Scrum benefits Scrum roles Scrum artifacts Scrum daily stand-up Scrum planning Scrum review & retrospective Q&A

17

Scrum - overview

18

Scrum roles - Pig & Chicken

Pigs: who are committed to building software regularly

and frequently. (e.g. the Scrum team)

Chicken: who involved but not a pig. Usually they are informed of the progress. (e.g. stakeholders, managers)

19

Scrum roles - Scrum master

+

Scrum Master:

- Primary job is toremove impediments to the ability of the team to deliverthe sprint goal. - Not necessarily the leader of the team (as the team is self-organizing) but acts as a buffer between the team and any distracting influences. - Understands the benefits of the Scrum process to ensure that Scrum practices are used as intended.
20

Scrum roles - The Team

+

Product Owner:

- Customer representative -Prioritizesproduct requirements

The Team:

- Includes others in Scrum team, who have the responsibility to deliver the product. - Usually 5-9 people with cross-functional skills. - Self-organizing

21

Outline

Software development processes Scrum benefits Scrum roles Scrum artifacts Scrum daily stand-up Scrum planning Scrum review & retrospective Q&A

22

Scrum artifacts - overview

Taskboard, story, backlog, sprint, burndown, velocity, DoD, ...

23

Scrum artifacts - taskboard

User stories (with tasks) visible ona physical board.

24

Scrum artifacts - burndown chart

Burn chart is a graphical representation ofwork left to do versus time.

+ tracking the teams progress & predicting when tasks will be completed + how many story points the team can earn thevelocity. It helps predict delivery times based on number of story points.

25

Scrum artifacts - Definition of Done

26

Scrum - meetings

27

Outline

Software development processes Scrum benefits Scrum roles Scrum artifacts Scrum daily stand-up Scrum planning Scrum review & retrospective Q&A

28

Scrum - daily standup

Attendees: Anyone can attend, but only the pigs (Scrum team) may speak.

29

Scrum - daily meeting

Time: short (usually 5-15 minutes)!

It should start at the same time every working day (practically15-45 mins after start working time).

Venue: near the collaboration space,

i.e. near the Scrum taskboard enough to see the characters there.

Agenda: Everybody tells others about his tasks, in 3 points:

+ What has he done since the previous stand-up ?(DONEs yesterday) + What is he planning to do today ?(DOs today) + Is there any obstacle preventing him/her from 30 doing what

Outline

Software development processes Scrum benefits Scrum roles Scrum artifacts Scrum daily stand-up Scrum planning Scrum review & retrospective Q&A

31

Scrum - planning meeting

(time-boxed: 8 hours)

At the beginning of any Sprint (iteration 1-4 weeks), two half:

* BackLog selection (WHAT to do)

+ Some ofProduct Backlog(user stories) will be chosen to beSprint Backlog. +Business value: is set by the Product Owner (client representative).
-> represents PRIORITY:how Important the story is to the client.

+Development effort: is set by the Team.

-> represents COMPLEXITY:how Hard to implement the story according to the average developers experience.
User Story: As a [USER] , I want [Feature X] so that [Y satisfied]

32

Scrum - planning tasks

* Task estimation (HOW to do)

+ each user story is broken down intoconcretetasks, and for each
task every group votes a number as the estimated points for the task.

Planning poker cards: for displaying the

voted/estimated points. One task point is implicitly considered1
man hour, for simplicity. (note: some may use 1 man day for 1 story point).

33

Scrum - planning estimation

* Task estimation (HOW to do)

+

If the points from the groups for the task are unanimous,
or similarly (highest number is not higher than 1.5 the lowest number), the final estimated points is determined andmarked into the task.

If the points of the group are not similarly

(see above), the groups of highest number and lowest number will, in turn,tell the team why they think their number is suitable. After that all groups will reestimate that task again. (this step may be repeated several times until a compromise is reached) should not exceed a predefined certain amount (20-40 man hours), otherwise the story may either be labeled asepicto be broken into smaller stories so as to not violate that limitation.
34

Total estimated points for a story

Outline

Software development processes Scrum benefits Scrum roles Scrum artifacts Scrum daily stand-up Scrum planning Scrum review & retrospective Q&A

35

Scrum - review meeting

Review meeting (time-boxed: 3-4 hours)

+ internal showcase for whole team (including chickens) + demonstrate what is being done + direct feedback (incomplete features do not count)

36

Scrum - retrospective meeting

Retrospective meeting (time-boxed: 2-3 hours)

+ what we did well? + what did not go well? + which improvement should be applied right next Sprint?

(All Scrum team members raise their opinions about the Sprint, in 3 topics)

37

Questions & Answers

38

http://en.wikipedia.org/wiki/Scrum_(development) http://allaboutagile.com/how-to-implement-scrum-in-10-easy-steps/ http://www.scrumalliance.org/articles/119-unlearn-what-you-have-learned http://ducquoc.wordpress.com/2011/03/30/agile-scrum-summary/ ...

39

Bonus - Scrum origins

Jeff Sutherland
Initial scrums at Easel Corp in 1993 IDX and 500+ people doing Scrum

Ken Schwaber
Scrum presented at OOPSLA 96 with Sutherland ADM, Author of three books on Scrum

Mike Beedle
Scrum patterns in PLOPD4

Mike Cohn
Co-founded Scrum Alliance in 2002, initially within the Agile Alliance 40