Getting Agile with Scrum
Upcoming SlideShare
Loading in...5

Getting Agile with Scrum






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Getting Agile with Scrum Getting Agile with Scrum Presentation Transcript

  • Getting Agile with Scrum6 June 2012Mike Cohn1
  • ® © 2003–2012 Mountain Goat Software®We’re losing the relay raceHirotaka Takeuchi and Ikujiro Nonaka,“TheNew New Product Development Game”,Harvard Business Review, January 1986.“The… ‘relay race’ approach to producttries to go the distance as a unit, passing thecompetitive requirements.”2
  • ® © 2003–2012 Mountain Goat Software®Source: “How Apple Does It,” Time Magazine,October 24, 2005 by Lev Grossman“Apple employees talk incessantly about whatthey call ‘deep collaboration’ or ‘cross-pollination’ or ‘concurrent engineering.’“Essentially it means that products don’t passfrom team to team. There aren’t discrete,sequential development stages. Instead, it’ssimultaneous and organic.“Products get worked on in parallel by alldepartments at once—design, hardware,software—in endless rounds of interdisciplinarydesign reviews.”3
  • ® © 2003–2009 Mountain Goat Software®YahooGoogleElectronic ArtsIBMLockheed MartinPhilipsSiemensNokiaCapital OneBBCIntuitAppleNielsen MediaFirst American CorelogicQualcommTexas InstrumentsJohn DeereLexis NexisTime WarnerTurner BroadcastingOce4
  • ® © 2003–2009 Mountain Goat Software®In-house developmentContract developmentFixed-price projectsFinancial applicationsapplications24x7 systems with 99.999%uptime requirementsthe Joint Strike FighterVideo game developmentsystemsNetwork switchingapplicationsISV applicationsapplications in use5
  • ® © 2003–2009 Mountain Goat Software®Characteristics“sprints”Uses generative rules to create an agile6
  • ® © 2003–2012 Mountain Goat Software®Project noise levelSimpleComplexAnarchyComplicatedTechnologyRequirementsAgreementClose toAgreementClosetoCertaintyCertaintyStrategic Management andOrganizational DynamicsAgile Software Development with Scrum® © 2003–2009 Mountain Goat Software®7
  • ® © 2003–2012 Mountain Goat Software®ScrumCancelReturnSprint1-4 weeksReturnSprint goalSprintproduct incrementProductVouchersVouchersCancel24 hours8
  • ® © 2003–2009 Mountain Goat Software®Sprints“sprints”Typical duration is 2–4 weeks or a calendarmonth at mostProduct is designed, coded, and tested duringthe sprint9
  • ® © 2003–2009 Mountain Goat Software®Sequential vs. overlappingdevelopmentand Nonaka. Harvard Business Review, January thing at a time......Scrum teams do a littleRequirements Design Code Test10
  • ® © 2003–2009 Mountain Goat Software®No changes during a sprintPlan sprint durations around how long you canChange11
  • ® © 2003–2012 Mountain Goat Software®Product ownerScrumMasterTeamRolesSprint planningSprint reviewSprint retrospectiveDaily scrum meetingCeremoniesBurndown charts12
  • ® © 2003–2012 Mountain Goat Software®Sprint planningSprint reviewSprint retrospectiveDaily scrum meetingCeremoniesBurndown chartsProduct ownerScrumMasterTeamRoles13
  • ® © 2003–2009 Mountain Goat Software®Product ownerMakes scope vs. schedule decisionsprojectAdjust needed Accept or reject work results14
  • ® © 2003–2009 Mountain Goat Software®The ScrumMasterand practicesRemoves impediments15
  • ® © 2003–2009 Mountain Goat Software®The teamTypically 5-9 peopleProgrammers, testers, user experience designers, etc.M16
  • ® © 2003–2012 Mountain Goat Software®Product ownerScrumMasterTeamRolesBurndown chartsSprint planningSprint reviewSprint retrospectiveDaily scrum meetingCeremonies17
  • ® © 2003–2012 Mountain Goat Software®Sprint planning meetingSprintbacklogSprintgoalWho• Team, ScrumMaster, & ProductOwnerAgenda• Discuss top priority productbacklog items• Team selects which to doWhy• Know what will be worked on• Understand it enough to do it18
  • ® © 2003–2009 Mountain Goat Software®Sprint planningcommit to completingHigh-level design is consideredAs a vacationplanner, I want tosee photos of thehotels.19
  • ® © 2003–2009 Mountain Goat Software®The daily scrumParametersDaily15-minutesStand-upWhole world is invitedowner, can talkHelps avoid other unnecessary meetings20
  • ® © 2003–2009 Mountain Goat Software®Everyone answers 3 questionsThese are notWhat did you do yesterday?1What will you do today?2Is anything in your way?321
  • ® © 2003–2009 Mountain Goat Software®The sprint reviewTeam presents what it accomplished duringthe sprint2-hour prep time ruleNo slidesWhole team participatesInvite the world22
  • ® © 2003–2009 Mountain Goat Software®Sprint retrospectivePeriodically take a look at what is and is notworkingTypically around 30 minutesWhole team participatesScrumMasterProduct ownerTeam23
  • ® © 2003–2009 Mountain Goat Software®Start / Stop / ContinueWhole team gathers and discusses what they’dStart doingStop doingContinue doingThis is just oneof many waysto do a sprintretrospective.24
  • ® © 2003–2012 Mountain Goat Software®Product ownerScrumMasterTeamRolesSprint planningSprint reviewSprint retrospectiveDaily scrum meetingCeremoniesBurndown charts25
  • ® © 2003–2009 Mountain Goat Software®The requirementsthe projectIdeally expressed such thateach item has value to theproductownereach sprintThis is the26
  • ® © 2003–2012 Mountain Goat Software®Backlog item EstimateAllow a guest to make a reservation 3As a guest, I want to cancel a reservation. 5reservation.3As a hotel employee, I can run RevPAR8Improve exception handling 8... 30... 5027
  • ® © 2003–2009 Mountain Goat Software®Sprint goalA short statementof what the workwill be focused onduring the sprintSprint 8The checkout process—payfor an order, pick shipping,order gift wrapping, etc.Sprint 7Implement basic shoppingcart functionality includingadd, remove, and update.28
  • ® © 2003–2009 Mountain Goat Software®Work is never assignedEstimated work remaining is updated daily29
  • ® © 2003–2012 Mountain Goat Software®TasksCode the middle tierTest the middle tierWrite online helpMon8168128Tues412168Wed Thur41184Fri88Add error logging810168830
  • ® © 2003–2012 Mountain Goat Software®02004006008001,000 4/29/025/6/025/13/025/20/025/24/02Hours31
  • ® © 2003–2012 Mountain Goat Software®Hours403020100Mon Tue Wed Thu FriTasksCode the middle tierTest the middle tierWrite online helpMon816812Tues Wed Thur Fri4121671181016 85032
  • ® © 2003–2009 Mountain Goat Software®Typical individual team is 7 ± 2 peopleFactors in scalingTeam dispersionProject durationpeople33
  • ® © 2003–2012 Mountain Goat Software®Scaling through the Scrum34
  • ® © 2003–2012 Mountain Goat Software®ProgrammersScrumMastersUI DesignersTestersDBAsCommunities ofPractice help scaleand cut acrossScrum teams35
  • ® © 2003–2009 Mountain Goat Software®A Scrum reading listAgile Estimating and PlanningAgile Game Development with ScrumAgile Product OwnershipAgile RetrospectivesAgileTesting:A Practical Guide forTesters and AgileTeamsCrispin and Janet GregoryCoaching AgileTeamsEssential ScrumSucceeding with Agile: Software Development using ScrumCohnUser Stories Applied for Agile Software Development36
  • ® © 2003–2009 Mountain Goat Software®37
  • ® © 2003–2012 Mountain Goat Software®mike@mountaingoatsoftware.comwww.mountaingoatsoftware.comtwitter: mikewcohnMike Cohn38