ScrumMasterTraining

byEduardoRibeiroV2.0

Universidade doMinho- Departamento deInformática

edu.f.ribeiro@gmail.com@edu_f_ribeiro

WhatisAgile

“Agileisan“iterative”and“incremental”softwaredevelopmentmethodologywereitsmainfocusisonclientsatisfactionthrough

continuousdelivery.”

AgileManifesto

12PrinciplesbehindtheAgileManifesto

• Ourhighestpriorityistosatisfythecustomerthroughearlyandcontinuousdelivery ofvaluablesoftware.

• Welcomechangingrequirements,evenlateindevelopment.Agileprocessesharnesschangeforthecustomer'scompetitiveadvantage.

• Deliverworkingsoftwarefrequently,fromacoupleofweekstoacoupleofmonths,withapreferencetotheshortertimescale.

• Businesspeopleanddevelopersmustworktogetherdaily throughouttheproject.

• Buildprojectsaroundmotivatedindividuals.Givethemtheenvironmentandsupporttheyneed,andtrust themtogetthejobdone.

• Themostefficientandeffectivemethodofconveyinginformationtoandwithinadevelopmentteamisface-to-faceconversation.

• Workingsoftware istheprimarymeasureofprogress.

• Agileprocessespromotesustainabledevelopment.Thesponsors,developers,andusersshouldbeabletomaintainaconstantpaceindefinitely.

• Continuousattentiontotechnicalexcellence andgooddesign enhancesagility.

• Simplicity theartofmaximizingtheamountofworknotdone isessential.

• Thebestarchitectures,requirements,anddesignsemergefromself-organizingteams.

• Atregularintervals,theteamreflectsonhowtobecomemoreeffective,thentunesandadjustsitsbehavioraccordingly.

Traditionalvs.AgileDelivery

Traditionalvs.AgileFeedback

WhatisScrum?

Incremental!=Iterative

PRINCIPLESScrum

EmpiricalProcessControl

Transparency:

• TransparencyallowsallfacetsofanyScrumprocesstobeobservedby

anyone.

Inspection:

• UseofacommonScrumBoardandotherinformationradiators.

Adaptation:

• AdaptationhappensastheScrumCoreTeamandStakeholderslearn

throughtransparencyandinspectionandthenadaptbymaking

improvementsintheworktheyaredoing.

Self-Organization

Collaboration

ValueBase-Prioritization

Time-Boxing

IterativeDevelopment

TEAM&ROLESScrum

ScrumTeam&Roles

ScrumMaster

BallPointGame

BallPointGameobjective

TheobjectiveoftheBallPointgameistogetasmanyballsthroughtheteamaspossiblewithin

twominutes.

TheRules• Everyoneispartofonebigteam.• Eachballmusthaveair-time.• Eachballmustbetouchedatleastoncebyeveryteammember.

• Ballscannotbepassedtoyourdirectneighbortoyourimmediateleftorright.

• Eachballmustreturntothesamepersonwhointroduceditintothesystem.

• Thereareatotaloffiveiterations twominuteseach.

TimetoPlay

Anyconclusions?

ProductOwner

CEREMONIESScrum

GroomingtheProductBacklog

SprintPlanning

DailyStandUp

SprintRevieworDemo&Retrospective

ScrumFramework

UserStoriesContext

Asa…(userofthesystem)

Iwant…(featureorproblemtobesolved)

Sothat…(benefitofstorybeingcompleted)

The“sothat”partisincrediblyvaluableasitfocusespeopleontherealreasonbehindthisstory.

INVESTAcronym

Why?

UserStoryGame

WhyweEstimate?

PokerPlanning

EstimationTechniquesGames

GamesFormat

4 Exercises x10Min

TeamEstimation&Discussion

#1– AbsoluteEstimation

10 MIN

#1– AbsoluteEstimationBeagle 11

Labrador 32

GreatDane 91

Chihuahua 2

AppalachianMountainDog -

AmericanCocker Spaniel 14

BorderCollie 20

StaffordshireBullTerrier 17

Whatdidwelearn?

#2– RelativeEstimation

10 MIN

#2– RelativeEstimationImpala 13

Elephant 100

Giraffe 40

Elephant Shrew 1

Crocodile 20

Snake 3

Whatdidwelearn?

#3– PlanningPoker

10 MIN

#3– PlanningPokerSpain 5

China 100

Luxembourg 1

Denmark 2

SouthAfrica 13

Belize 2

Whatdidwelearn?

#4– AffinityEstimation

10 MIN

#4– AffinityEstimationConvertible S

Motorbike XS

Starship Enterprise XL

SUV S

MINIVAN S

BUS M

Whatdidwelearn?

DOD ANDDORScrum

DefinitionofDoneakaDoD

• The team agrees on, and displaysprominently somewhere in theteam room, a list of criteria whichmust be met before a productincrement "often a user story" isconsidered "done".

• On a feature level, the acceptancecriteria should be agreed up frontBEFORE the User Story issubmitted to acceptance.

DefinitionofReadyakaDoR

• By analogy with the "Definition ofDone", the team makes explicitand visible the criteria (generallybased on the INVEST matrix) thata user story must meet prior tobeing accepted into the upcomingiteration.

• On a feature level, the acceptancecriteria should be agreed up frontBEFORE code is written.

VisibilityofProgress

• Teamhasadutytoradiateinformationoutwards!

• Italsohelpsreduceinterruptions!

– ScrumandKanban PhysicalBoards

– Bigvisiblecharts(Ex:CFS’s,BurnDown,Etc)

– On-lineTools(Ex:RallyDev)

– Dailyreporting

Examples

Pre-Game

• Organizeteams– 5minutes• ProjectChattering– 5minutes• BuildingtheBacklog– 15minutes• Estimating– 20minutes– AffinityEstimation– PlanningPoker

Game• SprintPlanning– 5minutes• Sprint1– 7minutes• Sprint1ReviewandRetrospective- 5minutes

• SprintPlanning– 5minutes• Sprint2– 7minutes• Sprint2ReviewandRetrospective- 5minutes

• SprintPlanning– 5minutes• Sprint3– 7minutes• Sprint4ReviewandRetrospective- 5minutes

Game:SprintPlanning

POST-GAME:Debriefing• Whatdidyouobserve?• HowdiditfeelbeingonaScrum

team?• Howdidtheshortiterationsgo?• Howaccuratewerethe

estimations?• Whatwouldwehavedone

differentlyfromthebeginning,ifwehadanotherchancetoplaythegame?

• WhatwasthejoboftheProductOwner?

• Howdiditfeelafterthefirstsprintwhenalmostallitemsrequiredre-work?

• WhatdidtheScrumMastersdo?• Howwillyourstrategychange,if

youknowtheProductOwnerisunavailableduringsprints?

• Howdidinter-teamcommunicationgo?Werethereanydependencies?Howweretheyresolved?

• Whatdidyoulearn?

ScrumSmellsakaAnti-Patterns

• ScrumMasteroranyotherteammemberassigningwork.

• DailyScrumisfortheScrumMasteroranyotherspecifyperson.

• Sprintworkbeingcarriedover.

• Testsprints.

• Everything“In-progress”.

• SM/DM/POoranyoneelseprovidingestimatesfortheteam.