Scrum-Introduction(敏捷开发介绍)

ANINTRODUCTIONTOSCRUMSchoolofSoftwareEngineering,TongjiUniversityAgendaIntroductionScrumframeworkScrumMasterandproductownerScrumteamEstimatingandplanningIntroduction•Agileisawayofthinkingandasystematicapproachfortherapiddeliveryofcomplexproductsandservices.Agileminimizesriskbyincrementaldelivery,emphasizesrealtimecollaboration,andusesbusinessvalueastheprimarymeasureofprogress.Agile•ScrumisastyleofAgilethatprovidesaprojectmanagementwrapperforincrementaldeliveryofprojects,independentoftechnologyused.Scrumcanbeusedwithnon-ITprojectsaswell.ScrumScrumhasbeenused:CommercialsoftwareIn-housedevelopmentContractdevelopmentFixed-priceprojectsFinancialapplicationsISO9001-certifiedapplicationsEmbeddedsystems24x7systemswith99.999%uptimerequirementstheJointStrikeFighter(F-35)VideogamedevelopmentFDA-approved,life-criticalsystemsSatellite-controlsoftwareWebsitesHandheldsoftwareMobilephonesNetworkswitchingapplicationsISVapplicationsSomeofthelargestapplicationsinuseKeyAgilePrinciples:Satisfythecustomerthroughearlyandcontinuousdeliveryofvaluablesoftware.Welcomechangingrequirements,evenlateindevelopment.Businesspeopleanddevelopersmustworktogetherconstantly.Workingsoftwareistheprimarymeasureofprogress.LessonlearnedScrumcharacteristics:Self-organizingteamsProductprogressesinaseriesofmonth-long“sprints”Requirementsarecapturedasitemsinalistof“productbacklog”NospecificengineeringpracticesprescribedOneofthe“agileprocesses”WhyAgile?ProcessandtoolsIndividualsandinteractionsoverFollowingaplanRespondingtochangeoverComprehensivedocumentationWorkingsoftwareoverContractnegotiationCustomercollaborationoverAgileManifestoScrumFrameworkOurwishes:ThecustomerknowswhathewantsThedevelopersknowhowtobuilditNothingwillchangealongthewayRealitytolivewith:ThecustomerdiscoverswhathewantsThedevelopersdiscoverhowtobuilditManythingschangealongthewayFeasibilityAnalyzeDesignCodingTest/ReleaseWaterfallmodelAgile(Scrum)modelPrioritizeFeasibilityAnalysisDesignCodingTest/releaseAgileWaterfallModelScrumstartswithto-dolistwithpriorities:Productbacklog:•projectartifacts(outcomes)Sprint:•iterativeprocessoftheprojectSprintbacklog:•artifacts(outcomes)forasprintDefinitionsPutitalltogether:Scrumboard:Sprintindetail:Scrumprojectsmakeprogressinaseriesof“sprints”Typicaldurationis2–4weeksoracalendarmonthatmostAconstantdurationleadstoabetterrhythmProductisdesigned,coded,andtestedduringthesprintSequentialvs.OverlappingDevelopmentRatherthandoingallofonethingatatime......ScrumteamsdoalittleofeverythingallthetimeAnalysisDesignCodeTestIterativeandIncrementalDevelopmentMoreimportantlyChangeFrameworkoverview•Productowner•ScrumMaster•TeamRoles•Sprintplanning•Sprintreview•Sprintretrospective•DailyscrummeetingCeremonies•Productbacklog•Sprintbacklog•BurndownchartsArtifactsProductOwner&ScrumMasterProductownerroleDefinethefeaturesoftheproductDecideonreleasedateandcontentBeresponsiblefortheprofitabilityoftheproduct(ROI)PrioritizefeaturesaccordingtomarketvalueAdjustfeaturesandpriorityeveryiteration,asneededAcceptorrejectworkresultsProductownerresponsibilitiesindetailsManageprofitabilityandreturnoninvestment(ROI)EstablishesbaselinetargetROIPrioritizesproductbacklogtomaximizeROIMeasuresBusinessvaluedeliveredProductownerresponsibilitiesindetails(cont.)CallforreleasesDecideswhentocallforanofficialreleaseofapotentiallyshippableproductorupdateCanshiftareleasedateforwardorbackwardtomaximizeROIbasedonnewknowledgeProductownerresponsibilitiesindetails(cont.)GuidesproductdevelopmentEstablishes,communicatesandenrichesthevisionKnowswhattobuildandinwhatsequenceTunesthevisionwiththeteamastheylearnhowtobuildtheproductEnsuringwhatgetdeliversvalues!FocusingonfastfeedbackDiscussion:Whoistheproductownerforthefollowingproducts:iPhoneCustomizedapplicationsystemAsystemhostedinacloudenvironmentScrumMasterroleRepresentsmanagementtotheprojectResponsibleforenactingScrumvaluesandpracticesRemovesimpediments(obstacles)EnsurethattheteamisfullyfunctionalandproductiveEnableclosecooperationacrossallrolesandfunctionsShieldtheteamfromexternalinterferencesScrumMasterresponsibilitiesindetailsProtectingtheTeamOvercommittingUndercommittingSustainablepaceOutsideinterferenceMultitaskingAllowfailureandselforganizationScrumMasterresponsibilitiesindetailsResponsibleforScrumProcessRemoveImpediments(VisibleandNon-visible)QualityTeamHealthContinuousImprovement(Team/ImmediateEnvironment)OrganizationalChangeScrumTeamTeamScrumTeamTypically5-9people(7plus/minus2)Cross-functional:Programmers,testers,userexperiencedesigners,etc.Membersshouldbefull-timeMayhaveexceptions(e.g.,databaseadministrator)ScrumTeamAttributesSelf-organizingCross-functionalwithnorolesResponsibleforcommittingtoworkAuthoritytodowhateverisneededtomeetcommitmentOpen,collocatedspaceResolutionofconflictsAnAgileEco-systemScrumTeamBillofRightsYouhavetherightto:Knowwhatisneeded,withcleardeclarationsofpriority.Producequalityworkatalltimes.Askforandreceivehelpfrompeers,supervisors,andcustomers.Make,an