Agile Software Development at UPT DEGI | 5th of Dec 2016
-
Upload
eduardo-ribeiro -
Category
Technology
-
view
37 -
download
2
Transcript of Agile Software Development at UPT DEGI | 5th of Dec 2016
WhatisAgile
“Agileisan“itera<ve”and“incremental”so)waredevelopmentmethodologywereitsmainfocusisonclientsa<sfac<onthrough
con<nuousdelivery.”
12PrinciplesbehindtheAgileManifesto
• Ourhighestpriorityistosa#sfythecustomerthroughearlyandcon#nuousdeliveryofvaluableso)ware.
• Welcomechangingrequirements,evenlateindevelopment.Agileprocessesharnesschangeforthecustomer'scompe<<veadvantage.
• Deliverworkingso)warefrequently,fromacoupleofweekstoacoupleofmonths,withapreferencetotheshorter#mescale.
• Businesspeopleanddevelopersmustworktogetherdailythroughouttheproject.
• Buildprojectsaroundmo#vatedindividuals.Givethemtheenvironmentandsupporttheyneed,andtrustthemtogetthejobdone.
• Themostefficientandeffec<vemethodofconveyinginforma<ontoandwithinadevelopmentteamisface-to-faceconversa#on.
• Workingso:wareistheprimarymeasureofprogress.
• Agileprocessespromotesustainabledevelopment.Thesponsors,developers,andusersshouldbeabletomaintainaconstantpaceindefinitely.
• Con<nuousaZen<ontotechnicalexcellenceandgooddesignenhancesagility.
• Simplicitytheartofmaximizingtheamountofworknotdoneisessen<al.
• Thebestarchitectures,requirements,anddesignsemergefromself-organizingteams.
• Atregularintervals,theteamreflectsonhowtobecomemoreeffec#ve,thentunesandadjustsitsbehavioraccordingly.
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
• Increasedproduc<vity
• Reducedwaste
• Moreproduc<ve&happy
teams
EmpiricalProcessControl
Transparency:
• TransparencyallowsallfacetsofanyScrumprocesstobeobservedby
anyone.
Inspec#on:
• UseofacommonScrumBoardandotherinforma<onradiators.
Adapta#on:
• Adapta<onhappensastheScrumCoreTeamandStakeholderslearn
throughtransparencyandinspec<onandthenadaptbymaking
improvementsintheworktheyaredoing.
Values
• Focus-Becausewefocusononlyafewthingsata<me,weworkwelltogetherandproduce
excellentwork.Wedelivervaluableitemssooner.
• Courage-Becauseweworkasateam,wefeelsupportedandhavemoreresourcesatour
disposal.Thisgivesusthecouragetoundertakegreaterchallenges.
• Openness-Asweworktogether,weexpresshowwe'redoing,what'sinourway,andourconcernssotheycanbeaddressed.
• Commitment-Becausewehavegreatcontroloverourowndes<ny,wearemore
commiZedtosuccess.
• Respect-Asweworktogether,sharingsuccessesandfailures,wecometorespecteachother
andtohelpeachotherbecomeworthyofrespect.
UserStoriesContext
Asa…(userofthesystem)
Iwant…(featureorproblemtobesolved)
Sothat…(benefitofstorybeing
completed)
The“sothat”partisincredibly
valuableasitfocusespeopleontherealreasonbehindthisstory.
Defini<onofDoneakaDoD
• 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 ssubmiZedtoacceptance.
Defini<onofReadyakaDoR
• Byanalogywiththe"Defini<onofDone", the team makes explicitand visible the criteria (generallybasedon the INVESTmatrix) thata user story must meet prior tobeingacceptedintotheupcoming
itera<on.
• Onafeaturelevel,theacceptancecriteriashouldbeagreedupfrontBEFOREcodeiswriZen.
VisibilityofProgress
• Teamhasadutytoradiateinforma<onoutwards!
• Italsohelpsreduceinterrup<ons!– ScrumandKanbanPhysicalBoards
– Bigvisiblecharts(Ex:CFS’s,BurnDown,Etc)
– On-lineTools(Ex:RallyDev)
– Dailyrepor<ng