Agile Software Development at UPT DEGI | 5th of Dec 2016

45
Agile So)ware Development (Framework, Systems and Evolu<on) by Eduardo Ribeiro V 2.0

Transcript of Agile Software Development at UPT DEGI | 5th of Dec 2016

AgileSo)wareDevelopment(Framework,SystemsandEvolu<on)

byEduardoRibeiroV2.0

Yes,theseareuglyslides!

EverythingstartswithanIdea

WhatisAgile

“Agileisan“itera<ve”and“incremental”so)waredevelopmentmethodologywereitsmainfocusisonclientsa<sfac<onthrough

con<nuousdelivery.”

AgileManifesto

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.

Tradi<onalvs.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

•  Increasedproduc<vity

•  Reducedwaste

•  Moreproduc<ve&happy

teams

WhatisScrum?

Incremental!=Itera<ve

PRINCIPLESANDVALUESScrum

EmpiricalProcessControl

Transparency:

•  TransparencyallowsallfacetsofanyScrumprocesstobeobservedby

anyone.

Inspec#on:

•  UseofacommonScrumBoardandotherinforma<onradiators.

Adapta#on:

•  Adapta<onhappensastheScrumCoreTeamandStakeholderslearn

throughtransparencyandinspec<onandthenadaptbymaking

improvementsintheworktheyaredoing.

Self-Organiza<on

Collabora<on

ValueBase-Priori<za<on

Time-Boxing

Itera<veDevelopment

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.

TEAM&ROLESScrum

ScrumTeam

ScrumMaster

ProductOwner

CEREMONIESScrum

GroomingtheProductBacklog

SprintPlanning

DailyStandUp

SprintRevieworDemo&Retrospec<ve

PROCESSScrum

ScrumFramework

ARTIFACTSScrum

UserStoriesContext

Asa…(userofthesystem)

Iwant…(featureorproblemtobesolved)

Sothat…(benefitofstorybeing

completed)

The“sothat”partisincredibly

valuableasitfocusespeopleontherealreasonbehindthisstory.

INVESTAcronym

WhyweEs<mate?

PokerPlanning

DODANDDORScrum

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

Examples

Kanban

WhyshouldwehaveaWIP?

Evolu<on-Scrumban

Thankyou!Anyques<on?