Agile So)ware Development (Scrum Framework) by Eduardo Ribeiro V 1.0
AgileSo)wareDevelopment(ScrumFramework)
byEduardoRibeiroV1.0
Again…Noooo!
Samejokes,uglydrawsandslides!
Overview• WhatisAgile?• AgileManifesto• 12PrinciplesbehindtheAgile
Manifesto• TradiQonalvs.Agile• AgileUmbrella• Whyweuse(orshoulduse)it?
• WhatisScrum?– Incremental!=IteraQve– ScrumPrinciplesandValues– ScrumTeam&Roles– ScrumCeremonies– ScrumFramework– ScrumArQfacts– UserStoriesContext– INVESTAcronym– WhyweesQmate?– PokerPlanning– DoDandDoR– VisibilityofProgress
WhatisAgile
“Agileisan“iteraQve”and“incremental”so)waredevelopmentmethodologywereitsmainfocusisonclientsaQsfacQonthrough
conQnuousdelivery.”
AgileManifesto
12PrinciplesbehindtheAgileManifesto
• Ourhighestpriorityistosa#sfythecustomerthroughearlyandcon#nuousdeliveryofvaluableso)ware.
• Welcomechangingrequirements,evenlateindevelopment.Agileprocessesharnesschangeforthecustomer'scompeQQveadvantage.
• Deliverworkingso)warefrequently,fromacoupleofweekstoacoupleofmonths,withapreferencetotheshorter#mescale.
• Businesspeopleanddevelopersmustworktogetherdailythroughouttheproject.
• Buildprojectsaroundmo#vatedindividuals.Givethemtheenvironmentandsupporttheyneed,andtrustthemtogetthejobdone.
• ThemostefficientandeffecQvemethodofconveyinginformaQontoandwithinadevelopmentteamisface-to-faceconversa#on.
• Workingso:wareistheprimarymeasureofprogress.
• Agileprocessespromotesustainabledevelopment.Thesponsors,developers,andusersshouldbeabletomaintainaconstantpaceindefinitely.
• ConQnuousa`enQontotechnicalexcellenceandgooddesignenhancesagility.
• SimplicitytheartofmaximizingtheamountofworknotdoneisessenQal.
• Thebestarchitectures,requirements,anddesignsemergefromself-organizingteams.
• Atregularintervals,theteamreflectsonhowtobecomemoreeffec#ve,thentunesandadjustsitsbehavioraccordingly.
TradiQonalvs.Agile
AgileUmbrella
CrystalClear
FeatureDrivenDevelopment(FDD)
DynamicSystemDevelopmentMethod(DSDM)
LeanSo:wareDevelopment
Kanban
Scrum
ExtremeProgramming(XP)
Adap#veSo:wareDevelopment(ASD)BehaviorDrivenDevelopment(BDD)
Whyweuse(orshoulduse)it?
• Reducedrisk
• EarlierROI/value
• Increasedvisibilityofprogress
• Increasedpredictability
• IncreasedproducQvity
• Reducedwaste
• MoreproducQve&happy
teams
WhatisScrum?
Incremental!=IteraQve
PRINCIPLESANDVALUESScrum
EmpiricalProcessControl
Transparency:
• TransparencyallowsallfacetsofanyScrumprocesstobeobservedby
anyone.
Inspec#on:
• UseofacommonScrumBoardandotherinformaQonradiators.
Adapta#on:
• AdaptaQonhappensastheScrumCoreTeamandStakeholderslearn
throughtransparencyandinspecQonandthenadaptbymaking
improvementsintheworktheyaredoing.
Self-OrganizaQon
CollaboraQon
ValueBase-PrioriQzaQon
Time-Boxing
IteraQveDevelopment
Values
• Focus-BecausewefocusononlyafewthingsataQme,weworkwelltogetherandproduce
excellentwork.Wedelivervaluableitemssooner.
• Courage-Becauseweworkasateam,wefeelsupportedandhavemoreresourcesatour
disposal.Thisgivesusthecouragetoundertakegreaterchallenges.
• Openness-Asweworktogether,weexpresshowwe'redoing,what'sinourway,andourconcernssotheycanbeaddressed.
• Commitment-BecausewehavegreatcontroloverourowndesQny,wearemore
commi`edtosuccess.
• Respect-Asweworktogether,sharingsuccessesandfailures,wecometorespecteachother
andtohelpeachotherbecomeworthyofrespect.
TEAM&ROLESScrum
ScrumTeam
ScrumMaster
ProductOwner
CEREMONIESScrum
GroomingtheProductBacklog
SprintPlanning
DailyStandUp
SprintRevieworDemo&RetrospecQve
PROCESSScrum
ScrumFramework
ARTIFACTSScrum
UserStoriesContext
Asa…(userofthesystem)
Iwant…(featureorproblemtobesolved)
Sothat…(benefitofstorybeing
completed)
The“sothat”partisincredibly
valuableasitfocusespeopleontherealreasonbehindthisstory.
INVESTAcronym
WhyweEsQmate?
PokerPlanning
DODANDDORScrum
DefiniQonofDoneakaDoD
• The teamagreeson, anddisplaysprominently somewhere in theteamroom,alistofcriteriawhichmust be met before a productincrement "o)en a user story" isconsidered"done".
• Onafeaturelevel,theacceptancecriteriashouldbeagreedupfrontBEFORE the User Story i ssubmi`edtoacceptance.
DefiniQonofReadyakaDoR
• Byanalogywiththe"DefiniQonofDone", the team makes explicitand visible the criteria (generallybasedon the INVESTmatrix) thata user story must meet prior tobeingacceptedintotheupcoming
iteraQon.
• Onafeaturelevel,theacceptancecriteriashouldbeagreedupfrontBEFOREcodeiswri`en.
VisibilityofProgress
• TeamhasadutytoradiateinformaQonoutwards!
• ItalsohelpsreduceinterrupQons!– ScrumandKanbanPhysicalBoards
– Bigvisiblecharts(Ex:CFS’s,BurnDown,Etc)
– On-lineTools(Ex:RallyDev)
– DailyreporQng
Examples
Thankyou!AnyquesQon?