Transcription
AbstractBasicScrumhandbookfortheb )aspirants.SudaRamakrishnaThiparthyCSM ,ITIL alliance.orgBASICSOFSCRUMINAGILE
ntBurn- icalSprintflowDiagram.9ScrumJargon.10
DefinitionofSCRUMScrumisoneoftheA singoneormorecross- ‐functional,self- ‐organizingteamsofabout7 /- ‐2peopleoneachteam.StandardsofScrum ions.Scrumusesfixed- fourweeks(or30dayslong).Scrumteamsshouldconsistof7 /- ‐2people.Sprintcannotexceedm ilyScrum/Stand- ‐upmeetingshouldbeonlyfor15m ,theirabilitytoestimatetheuserstoriesbecomesm ringplanningm eetingstom onT- etoswitchtoanon- ‐numericestimationtechnique.WithT- ortintermsofextra- ‐small,small,medium,large,extra- ‐large,ordoubleextra- einvolvedwiththismethod.Non- ptions,itm bovereason,theT- odideatom termsofsmall,m toChangeoverFollowingaPlan
Scrum Roles and ResponsibilitiesnerP ro duct ow Responsiblepersonforreleaseburn- ‐downchart. Responsiblefortheproductvision.Personwhom lyreprioritizetheproductbacklog.Scrum M ast er FacilitatoroftheScrumprocess. team. ions. Createsapositiveenvironmentfortheteamtobeself- ‐organizing. Enforcestimeboxes. Personwhom aintainssprintburn- ‐down/burn- ‐upcharts. Personwhofacilitatestherequiredmeetings. shecannotcommandtheteamtodoaspecifictask). Promotesimprovedpracticesofengineering. OnlyPOCforescalations. pmanagement.D evelo pment T eam Shouldbeaself- ‐organizingandcross- kills). Shouldself- ‐managethetasksamongtheteam. theteam’scontrol. klogitems. Consistsof7 /- ‐2members. Responsibletocompletethecommittedtaskforthesprint.
Typical Sprint Phases1. productbackloglieswiththeproductowner.3.Sprint artofthatparticularsprint.4. urthersprintsaccordingly.
ntBacklog- g4YES3SprintPlanning4Day2:SprintBacklog- g4YES3SprintPlanning4.
.Day3.SprintBacklog- g4YES3SprintPlanning4YES.Day5SprintBacklog- g4YES3SprintPlanning4YESSprint Burn- ‐down charts :Day1E10sg 8m6ag 4o 2nSprintVelocityDay- ‐1IdealLine0012345Days
EstimationDay310SprintVelocityDay- ‐386IdealLine420012345DaysEs 10t 8i 6m4at 2i 00onDay5SprintVelocityDay- rsprint1.ReleaseBurn- ‐downchart:EstimationWeek- ‐140SprintVelocityWeek- ‐130IdealLine2010001234Weeks
Week- ‐4Es 40t30im 20at 10io 00nSprintVelocityWeek- toriesandexecutethem.Inthisscenario,thesprintburn- int.
5 . D aily trictlytimeboxedmeetingof15m ssed/answeredbyeachteammember.a. WhatIdidyesterday.b. WhatIamgoingtodotodayc. ImpedimentsImayhave8.6 . M VP (Minim um V iable P dcanaddtoROI.Allteamm umMasterareexpectedtoattendthemeeting.7 . Sprint R oldsasprintreviewm issuediscussionandproblem- yScrumtoaddressanyissues.Sprint R etros pectiveNom Typical Sprint Flow DiagramInput from C ustomers,65B urndown / upchart sStakehol ders , etc.ScrumMasterD ai ly ScrumEvery24 hours1 – 4WeekSpri ntProduct ownerD ev el opment teamSpri ntPl anningMeeti ng7Sprint Backlog4Potentiall yShippabl e Product2319Spri ntretrospectiv e8Spri nt revi ew
Scrum onbelow( kenrolesinanAgile- mconsistsof7 /- orthefollowingreasons:a. rojectaccordingly.b. to3sprints. .Thankyou
BASICS!OF!SCRUM!IN!AGILE! Abstract(Basic!Scrum!handbookfor!the!beginners!in! the!Agile!world!and!CSM!(Certified!Scrum
