Let’s talk Scrum

17
Let’s talk Scrum Stephen Forte @worksonmypc [email protected] Chief Strategy Officer Telerik www.telerik.com www.stephenforte.net

description

Let’s talk Scrum. Stephen Forte @ worksonmypc [email protected] Chief Strategy Officer Telerik www.telerik.com www.stephenforte.net. Session.About.ToString();. Would like to implement Agile at your organization or have done so and would like to get more out of it - PowerPoint PPT Presentation

Transcript of Let’s talk Scrum

Page 1: Let’s talk Scrum

Let’s talk Scrum

Stephen Forte @[email protected] Strategy Officer Telerik www.telerik.comwww.stephenforte.net

Page 2: Let’s talk Scrum

Session.About.ToString();Would like to implement Agile at your organization or have done so and would like to get more out of itAssume you know something about Agile, but a complete novice is ok“Agile Presenting” The goal is to be interactive

Success of the seminar depends on your questions!Ask a question at any time!

Page 3: Let’s talk Scrum

The Agile Manifesto–a statement of values

Process and toolsIndividuals and interactions over

Following a planResponding to change over

Source: www.agilemanifesto.org

Comprehensive documentationWorking software over

Contract negotiation

Customer collaboration over

Page 4: Let’s talk Scrum

We’re losing the relay race

Hirotaka Takeuchi and Ikujiro Nonaka, “The New Product Development Game”, Harvard Business Review, January 1986.

“The… ‘relay race’ approach to product development…may conflict with the goals of maximum speed and flexibility. Instead a holistic or ‘rugby’ approach—where a team tries to go the distance as a unit, passing the ball back and forth—may better serve today’s competitive requirements

Page 5: Let’s talk Scrum

Scrum

Page 6: Let’s talk Scrum

Product owner

Define the features of the productDecide on release date and contentBe responsible for the profitability of the product (ROI)Prioritize features according to market value Adjust features and priority every iteration, as needed Accept or reject work results

Page 7: Let’s talk Scrum

The ScrumMaster

Represents management to the projectResponsible for enacting Scrum values and practicesRemoves impediments Ensure that the team is fully functional and productiveEnable close cooperation across all roles and functionsShield the team from external interferences

Page 8: Let’s talk Scrum

The team

Typically 4-9 peopleCross-functional:

Programmers, testers, user experience designers, etc.

Members should be full-timeMay be exceptions (e.g., database administrator)

Teams are self-organizingIdeally, no titles but rarely a possibility

Membership should change only between sprints

Page 9: Let’s talk Scrum

A sample product backlog

Backlog item EstimateAllow a guest to make a reservation 3

As a guest, I want to cancel a reservation. 5

As a guest, I want to change the dates of a reservation. 3

As a hotel employee, I can run RevPAR reports (revenue-per-available-room) 8

Improve exception handling 8... 30... 50

Page 10: Let’s talk Scrum

Sprints

Scrum projects make progress in a series of “sprints”

Analogous to Extreme Programming iterationsTypical duration is 2–4 weeks or a calendar month at mostA constant duration leads to a better rhythmProduct is designed, coded, and tested during the sprint

Page 11: Let’s talk Scrum

Sprint planning

Team selects items from the product backlog they can commit to completingSprint backlog is created

Tasks are identified and each is estimated (1-16 hours)Collaboratively, not done alone by the ScrumMaster

High-level design is considered

Page 12: Let’s talk Scrum

A sprint backlog

TasksCode the UICode the middle tierTest the middle tierWrite online helpWrite the foo class

Mon8

168

128

Tues4

1216

8

Wed Thur

411

84

Fri

8

8Add error logging

81016

88

Page 13: Let’s talk Scrum

The Daily Scrum

ParametersDaily10-15 minutesStand-up

Not for problem solvingHelps avoid other unnecessary meetingsGreat way to manage remote teams

Prevents teams from wasting time

Page 14: Let’s talk Scrum

Everyone answers 3 Qs

These are not status for the ScrumMasterThey are commitments in front of peers

What did you do yesterday?1

What will you do today?2

Is anything in your way?3

Page 15: Let’s talk Scrum

The sprint reviewTeam presents what it accomplished during the sprintTypically takes the form of a demo of new features or underlying architectureInformal

2-hour prep time ruleNo slides

Whole team participatesInvite everyone

Page 16: Let’s talk Scrum

Sprint retrospective

Periodically take a look at what is and is not workingTypically 15–30 minutesDone after every sprintWhole team participates

ScrumMasterProduct ownerTeamPossibly customers and others

Page 17: Let’s talk Scrum

Questions?