Introduction to ScrumIntroduction to ScrumPresented at Agile NCR WorkshopPresented at Agile NCR Workshop

By, By, Mayank Gupta, GlobalLogicMayank Gupta, GlobalLogicDeepak Mittal, IntelliGrapeDeepak Mittal, IntelliGrape

AgendaAgenda

►Agile ManifestoAgile Manifesto►Scrum Alliance SurveyScrum Alliance Survey►What is ScrumWhat is Scrum►Scrum FrameworkScrum Framework►Scrum Roles and CeremoniesScrum Roles and Ceremonies►Why we might fail using ScrumWhy we might fail using Scrum►SummarySummary

Dilbert goes agileDilbert goes agile

Agile ManifestoAgile Manifesto

► Individuals and Interactions Individuals and Interactions over processes and toolsover processes and tools

► Working software Working software over comprehensive documentationover comprehensive documentation

► Customer collaboration Customer collaboration over contract negotiationover contract negotiation

► Responding to change Responding to change over following a plan.over following a plan.

That is, while there is value in the items on the right, we That is, while there is value in the items on the right, we

value the items on the left more. value the items on the left more.

Scrum Alliance Survey - 2007Scrum Alliance Survey - 2007

► Seventy-five percentSeventy-five percent of those who of those who responded report that Scrum is meeting or responded report that Scrum is meeting or exceeding their organizations’ needs.exceeding their organizations’ needs.

► Forty-five percentForty-five percent of respondents report of respondents report their organizations are either very pleased their organizations are either very pleased with Scrum or believe it exceeds their with Scrum or believe it exceeds their organizations’ expectations. organizations’ expectations.

►Nearly 90 percent (87%)Nearly 90 percent (87%) of respondents of respondents report personal satisfaction with Scrum.report personal satisfaction with Scrum.

What is Scrum?What is Scrum?

► Scrum is agile software development Scrum is agile software development framework. framework.

► A wrapper for engineering practicesA wrapper for engineering practices► A simple approach to effectively manage A simple approach to effectively manage

complex problemscomplex problems► A process to maximize and maintain A process to maximize and maintain

productivityproductivity► A process to improve collaboration, A process to improve collaboration,

meaningful communication and maximize meaningful communication and maximize cooperationcooperation

Scrum FrameworkScrum Framework

►RolesRoles: Product Owner, Scrum Master, Team: Product Owner, Scrum Master, Team

► CeremoniesCeremonies: Spring planning, Spring review, : Spring planning, Spring review,

Sprint retrospective, Daily Scrum MeetingSprint retrospective, Daily Scrum Meeting

►ArtifactsArtifacts: Product backlog, Spring backlog, : Product backlog, Spring backlog,

Burndown ChartBurndown Chart

Scrum FrameworkScrum Framework

Potentially Shippable Product

Product Owner

Review

Scrum Master

The Team

789101112

1234

56

13

No Changes(during sprint)

Commitment

Daily Stand-UpMeeting

Retrospective

789101112

123456

13

x-Week Sprint

Product OwnerProduct Owner

►Voice of actual customerVoice of actual customer►Owns the prioritized list of Owns the prioritized list of

requirements (Product Backlog)requirements (Product Backlog)►Available to the team at all timesAvailable to the team at all times►Participates in sprint planning Participates in sprint planning

and review meetingsand review meetings►Responsible for product vision, Responsible for product vision,

ROI and release managementROI and release management

Scrum TeamScrum Team

► Teams of 7 +/- 2 participants (max Teams of 7 +/- 2 participants (max -15)-15)

► Cross functionalCross functional► Best experts in the domain areaBest experts in the domain area► Self-organizingSelf-organizing

Team decides who shall do whatTeam decides who shall do what They They inspect and adapt inspect and adapt as the as the

sprint goes alongsprint goes along► Have most of the powers during a Have most of the powers during a

sprintsprint

Scrum MasterScrum Master► FacilitatorFacilitator

► Protects the teamProtects the team

► Removes impediments to the ability of the teamRemoves impediments to the ability of the team

► Not the leader of team (Team is self organizing)Not the leader of team (Team is self organizing)

► Ensures the Scrum process is used as intendedEnsures the Scrum process is used as intended

► Responsible for Daily ScrumResponsible for Daily Scrum

► Coaches the teamCoaches the team

Does everything to help the team achieve the Does everything to help the team achieve the

sprint deliverablessprint deliverables

Product BacklogProduct Backlog

► An ordered list of prioritized itemsAn ordered list of prioritized items

► Ittems: Stories, features, defects, Ittems: Stories, features, defects,

taskstasks

► Used for release planning and Used for release planning and

Iteration planningIteration planning

►Highest priority Items are picked Highest priority Items are picked

firstfirst

Sprint Planning MeetingSprint Planning Meeting

1. Product Owner, Team, and other 1. Product Owner, Team, and other Stakeholders talk through Product Stakeholders talk through Product Backlog Items and prioritization.Backlog Items and prioritization.

2. Team determines how much time it 2. Team determines how much time it has available to commit during the has available to commit during the SprintSprint

33. . Team selects as much of the Product Team selects as much of the Product Backlog as it can commit to deliver by Backlog as it can commit to deliver by the end of the Sprint, and turns it into the end of the Sprint, and turns it into a plana plan- Validates commitment by breaking down - Validates commitment by breaking down

into tasks with time estimatesinto tasks with time estimates- Team decides who will do what, when; - Team decides who will do what, when;

thinks through sequencing, dependencies, thinks through sequencing, dependencies, possible task trades, and so forth.possible task trades, and so forth.

Daily Scrum MeetingDaily Scrum Meeting

►Must not last more than 15 Must not last more than 15 minutesminutes

►Held same place, same time, Held same place, same time, every working dayevery working day

► Anybody can come, but only the Anybody can come, but only the team can speakteam can speak

► 3 questions3 questions►What did I do yesterday?What did I do yesterday?►What am I going to do What am I going to do

today?today?►What are my impediments?What are my impediments?

Review/Sprint DemoReview/Sprint Demo

► Team presents the working demo. Team presents the working demo.

What have we achieved?What have we achieved?

Should show finished Should show finished

functionality.functionality.

What is missing.What is missing.

Maximum of 2 hours for Maximum of 2 hours for

presentation. presentation.

RetrospectiveRetrospective

► Facilitated by Scrum MasterFacilitated by Scrum Master► To increase productivity and To increase productivity and

► Team reflects on sprint experience Team reflects on sprint experience

and comes up with suggestions.and comes up with suggestions.

What went well?What went well?

What did not go so well?What did not go so well?

How can we improve?How can we improve?

Burndown chartBurndown chart

► A graphical representation of work A graphical representation of work left to do vs. time left to do vs. time

► Work remaining is the Y axis and Work remaining is the Y axis and

time is the X axis.time is the X axis. ► Useful to predict when all of the work Useful to predict when all of the work

would completewould complete Release burndown chartRelease burndown chart Sprint burndown chartSprint burndown chart

Why we might fail using Why we might fail using scrum?scrum?

►Hard!Hard!►Scrum does not fix everything Scrum does not fix everything ►Scrum makes problems visible - earlyScrum makes problems visible - early►Ready for a change?Ready for a change?► It makes Products to be delivered It makes Products to be delivered

fasterfaster►Customized/partial ScrumCustomized/partial Scrum

SummarySummary

• Everything is time-boxed.Everything is time-boxed.• Inspect & Adapt.Inspect & Adapt.• You can-not plan everything. You can-not plan everything. • Fail early. Fail early. • Shippable product at the end of every Shippable product at the end of every

iteration/sprint.iteration/sprint.• Iterative incremental development. Iterative incremental development. • Cross-functional teams. Cross-functional teams. • Self-organizing teams.Self-organizing teams.• Team owns the sprint backlog. Team owns the sprint backlog.

Where Scrum is used?Where Scrum is used?

• Yahoo• Sun• Siemens• Nokia• Philips• BBC• IBM• Xebia

► US Federal Reserve US Federal Reserve ► SAPSAP► H PH P► MotorolaMotorola► TransUnionTransUnion► GoogleGoogle► MicrosoftMicrosoft► GlobalLogicGlobalLogic

Thank YouThank You

Questions?Questions?