Scrum Glossary

Scrum Guide™: the definition of Scrum, written and provided by Ken Schwaber and Jeff Sutherland, co-creators of Scrum. This definition consists of Scrum's ... Skiptomaincontent X Back X Login Emailaddress Password ForgotPassword NotRegistered? Ifyoudon'talreadyhaveaScrum.orgaccount,youcansignupinjustafewseconds. RegisterHere DuetotheRussianinvasionofUkraine,wehavepausedallpurchasesandtraininginandfromRussia.  ReadStatement ScrumGlossary GlossaryofScrumTerms ThisglossaryismeanttorepresentanoverviewofScrum-relatedterms. SomeofthementionedtermsarenotmandatoryinScrum,buthavebeenaddedbecausetheyarecommonlyusedinScrum. TolearnmoreabouttheScrumframework,toidentifywhichofthesetermsarerequiredelementsofScrumandtounderstandhowthementionedelementsareconnected,wehighlyrecommendthatyoureferencethe ScrumGuide™. TolearnmoreabouttermsspecifictosoftwaredevelopmentteamsusingScrumandagilesoftwaredevelopmenttechniques,referencethe ProfessionalScrumDeveloperglossary. B Burn-downChart: achartwhichshowstheamountofworkwhichisthoughttoremaininabacklog.Timeisshownonthehorizontalaxisandworkremainingontheverticalaxis.Astimeprogressesanditemsaredrawnfromthebacklogandcompleted,aplotlineshowingworkremainingmaybeexpectedtofall.Theamountofworkmaybeassessedinanyofseveralwayssuchasuserstorypointsortaskhours.WorkremaininginSprintBacklogsandProductBacklogsmaybecommunicatedbymeansofaburn-downchart.Seealso:BurnupChart Burn-upChart: achartwhichshowstheamountofworkwhichhasbeencompleted.Timeisshownonthehorizontalaxisandworkcompletedontheverticalaxis.Astimeprogressesanditemsaredrawnfromthebacklogandcompleted,aplotlineshowingtheworkdonemaybeexpectedtorise.Theamountofworkmaybeassessedinanyofseveralwayssuchasuserstorypointsortaskhours.Theamountofworkconsideredtobein-scopemayalsobeplottedasaline;theburn-upcanbeexpectedtoapproachthislineasworkiscompleted. C Coherent/Coherence: ThequalityoftherelationshipbetweencertainProductBacklogitemswhichmaymakethemworthyofconsiderationasawhole.Seealso:SprintGoal. D DailyScrum: ScrumEventthatisa15-minutetime-boxedeventheldeachdayfortheDevelopers.TheDailyScrumisheldeverydayoftheSprint.Atit,theDevelopersplansworkforthenext24hours.ThisoptimizesteamcollaborationandperformancebyinspectingtheworksincethelastDailyScrumandforecastingupcomingSprintwork.TheDailyScrumisheldatthesametimeandplaceeachdaytoreducecomplexity. DefinitionofDone: isaformaldescriptionofthestateoftheIncrementwhenitmeetsthequalitymeasuresrequiredfortheproduct.ThemomentaProductBacklogitemmeetstheDefinitionofDone,anIncrementisborn.TheDefinitionofDonecreatestransparencybyprovidingeveryoneasharedunderstandingofwhatworkwascompletedaspartoftheIncrement.IfaProductBacklogitemdoesnotmeettheDefinitionofDone,itcannotbereleasedorevenpresentedattheSprintReview. Developer:  anymemberofaScrumTeam,thatiscommittedtocreatinganyaspectofausableIncrementeachSprintregardlessoftechnical,functionalorotherspecialty. E Emergence: theprocessofthecomingintoexistenceorprominenceofnewfactsornewknowledgeofafact,orknowledgeofafactbecomingvisibleunexpectedly. Empiricism: processcontroltypeinwhichonlythepastisacceptedascertainandinwhichdecisionsarebasedonobservation,experienceandexperimentation.Empiricismhasthreepillars:transparency,inspectionandadaptation. Engineeringstandards: asharedsetofdevelopmentandtechnologystandardsthatDevelopers applytocreatereleasableIncrementsofsoftware. F Forecast(offunctionality): theselectionofitemsfromtheProductBacklogDevelopersdeemsfeasibleforimplementationinaSprint. I Increment: ScrumArtifactthatdefinesthecomplete andvaluableworkproducedbytheDevelopersduringaSprint.ThesumofallIncrementsformaproduct. P ProductBacklog: AScrumArtifactthatconsistsofanorderedlistoftheworktobedoneinordertocreate,maintainandsustainaproduct.ManagedbytheProductOwner. ProductBacklogrefinement: theactivityinaSprintthroughwhichtheProductOwnerandtheDevelopersaddgranularitytotheProductBacklog. ProductOwner: RoleinScrumaccountableformaximizingthevalueofaproduct,primarilybyincrementallymanagingandexpressingbusinessandfunctionalexpectationsforaproducttotheDevelopers. ProductGoal: TheProductGoaldescribesafuturestateoftheproductwhichcanserveasatargetfortheScrumTeamtoplanagainst.TheProductGoalisintheProductBacklog.TherestoftheProductBacklogemergestodefine“what”willfulfilltheProductGoal. R Ready: asharedunderstandingbytheProductOwnerandtheDevelopersregardingthepreferredlevelofdescriptionofProductBacklogitemsintroducedatSprintPlanning. Refinement: seeProductBacklogRefinement S Scrum: Scrumisalightweightframeworkthathelpspeople,teamsandorganizationsgeneratevaluethroughadaptivesolutionsforcomplexproblemsasdefinedintheScrumGuideTM. ScrumBoard: aphysicalboardtovisualizeinformationforandbytheScrumTeam,oftenusedtomanageSprintBacklog.ScrumboardsareanoptionalimplementationwithinScrumtomakeinformationvisible. ScrumGuide™: thedefinitionofScrum,writtenandprovidedbyKenSchwaberandJeffSutherland,co-creatorsofScrum.ThisdefinitionconsistsofScrum’saccountabilities,events,artifacts,andtherulesthatbindthemtogether. ScrumMaster: RolewithinaScrumTeamaccountableforguiding,coaching,teachingandassistingaScrumTeamanditsenvironmentsinaproperunderstandinganduseofScrum. ScrumTeam: aself-managing teamconsistingofoneScrumMaster,oneProductOwner,andDevelopers. ScrumValues: asetoffundamentalvaluesandqualitiesunderpinningtheScrumframework;commitment,focus,openness,respectandcourage. Self-Managing: ScrumTeamsarecross-functional,meaningthemembershavealltheskillsnecessarytocreatevalueeachSprint.Theyarealsoself-managing,meaningtheyinternallydecidewhodoeswhat,when,andhow.  Sprint: ScrumEventthatistime-boxedtoone month orless,thatservesasacontainerfortheotherScrumeventsandactivities.Sprintsaredoneconsecutively,withoutintermediategaps. SprintBacklog: ScrumArtifactthatprovidesanoverviewofthedevelopmentworktorealizeaSprint’sgoal,typicallyaforecastoffunctionalityandtheworkneededtodeliverthatfunctionality.ManagedbytheDevelopers. SprintGoal: ashortexpressionofthepurposeofaSprint,oftenabusinessproblemthatisaddressed.FunctionalitymightbeadjustedduringtheSprintinordertoachievetheSprintGoal. SprintPlanning: ScrumEventthatistime-boxedto8hours,orless,tostartaSprint.ItservesfortheScrumTeamtoinspecttheworkfromtheProductBacklogthat’smostvaluabletobedonenextanddesignthatworkintoSprintbacklog. SprintRetrospective: ScrumEventthatissettoatime-box of 3hours,orless,toendaSprint.ItservesfortheScrumTeamtoinspectthepastSprintandplanforimprovementstobeenactedduringfuture Sprints. SprintReview: ScrumEventthatissettoatime-boxedof4hours,orless,toconcludethedevelopmentworkofaSprint.ItservesfortheScrumTeamandthestakeholderstoinspecttheIncrementofproductresultingfromtheSprint,assesstheimpactoftheworkperformedonoverallprogresstowardtheProductGoalandupdatetheProductbackloginordertomaximizethevalueofthenextperiod. Stakeholder: apersonexternaltotheScrumTeamwithaspecificinterestinandknowledgeofaproductthatisrequiredforincrementaldiscovery.RepresentedbytheProductOwnerandactivelyengagedwiththeScrumTeamatSprintReview. T TechnicalDebt: thetypicallyunpredictableoverheadofmaintainingtheproduct,oftencausedbylessthanidealdesigndecisions,contributingtothetotalcostofownership.MayexistunintentionallyintheIncrementorintroducedpurposefullytorealizevalueearlier. V Values: Whenthevaluesofcommitment,courage,focus,opennessandrespectareembodiedandlivedbytheScrumTeam,the*Scrumpillars*oftransparency,inspection,andadaptation*cometolife*and*buildtrust*foreveryone.TheScrumTeammemberslearnandexplorethosevaluesastheyworkwiththeScrumevents,rolesandartifacts. Download theScrumValuesPoster Velocity: anoptional,butoftenused,indicationoftheamountofProductBacklogturnedintoanIncrementofproductduringaSprintbyaScrumTeam,trackedbytheDevelopersforusewithintheScrumTeam. Sharethisarticle Email Facebook Twitter LinkedIn Reddit Pocket ByusingthissiteyouareagreeingtothePrivacyPolicyandTermsofService.X