An Introduction to Scrum · 2018-08-01 · An Introduction to Scrum Powering Transformation....
Transcript of An Introduction to Scrum · 2018-08-01 · An Introduction to Scrum Powering Transformation....
AgileSoftwareDevelopment
AnIntroductiontoScrum
PoweringTransformation.Together.
What’sInside:
Agile Software Development1
Scrum as an Implementation2
Visual Studio Team Services (VSTS)3
Scrum with VSTS4
AgileSoftwareDevelopment
PrinciplesandManifesto
Ourhighestpriority istosatisfythe
customer through earlyandcontinuous
deliveryofvaluablesoftware.
AgilePrinciples
Welcomechangingrequirements,evenlateindevelopment.Agileprocesses
harnesschangeforthecustomer's
competitiveadvantage.
Deliverworkingsoftwarefrequently,froma coupleofweekstoacoupleofmonths,
witha preferencetotheshorter
timescale.
Businesspeopleanddevelopersmustwork
together dailythroughout theproject.
Buildprojectsaroundmotivatedindividuals.Givethemtheenvironment
andsupporttheyneed,
andtrustthemtogetthejobdone.
Themostefficientandeffectivemethodofconveyinginformationtoandwithina
developmentteamisface-to-face
conversation.
Workingsoftwareistheprimarymeasureof
progress.
Agileprocessespromotesustainabledevelopment.Thesponsors,developers,
andusersshouldbeabletomaintaina
constantpaceindefinitely.
Continuousattentiontotechnicalexcellenceandgooddesignenhances
agility.
Simplicity--theartofmaximizingtheamountofworknotdone--isessential.
Thebestarchitectures,requirements,anddesignsemergefromself-organizing
teams.
Atregularintervals,theteamreflectsonhowtobecomemoreeffective,then
tunesandadjustsitsbehavior
accordingly.
Individualsandinteractions
Workingsoftware
Customercollaboration
Responding tochange
processesandtools
comprehensivedocumentation
contractnegotiation
followingaplan
AgileManifesto
Weareuncoveringbetterwaysofdeveloping
softwarebydoingitandhelpingothersdoit.
Throughthisworkwehavecometovalue:
Thatis,whilethereisvalueintheitemson
theright,wevaluetheitemsontheleftmore.
over
Scrum
TheRulesoftheGame
Roles
• TheProductOwner
• TheDevelopmentTeam
• TheScrumMaster
DefiningScrum
Events Artifacts
• TheSprint
• SprintPlanning
• DailyScrum
• SprintReview
• SprintRetrospective
• ProductBacklog
• SprintBacklog
The Definition of Scrum
A framework within which people can address complex
adaptive problems, while productively and creatively
delivery products of the highest value possible.
Lightweight
• Moreefficientmeetings
• Lesstimespentinupfront
requirements
• QAiniteration
Scrumis:
Simpletounderstand Difficulttomaster
• Straightforwardguidelines
• Commonlanguage
• Artandscience
Transparency
• Aspectsofprocessvisible
• Aspectsdefinedbyacommon
standard
ScrumTheory
Inspection Adaption
• Inspectionofartifacts
• InspectionofSprintgoal
progress
• Shouldnotgetintheway
• Whenprocessdeviatesandthe
productisunacceptablewe
adjust
• Minimizefurtherdeviationby
adaptingquickly
TheScrumTeam
Self-organizing– theteamchooseshowtobestcompletethework
Cross-functional– theteamhasallskillsneededtocompletethework
Promotescreativityandproductivity
Deliversproductsiteratively11
ProductOwner DevelopmentTeam ScrumMaster
TheProductOwner
Responsible formaximizingvalue
ofproductandworkofthe
development team
Thesole personresponsible for
backlog
Includingclearlyexpressing,
ordering,andoptimizing
12
TheDevelopmentTeam
Thosewhodotheworkof
deliveringapotentially shippable
productattheendofaniteration
Empoweredbytheorganizationto
managetheirownwork
Self-organizingandcross-functional
Nosub-teams, notitleotherthan
developer, theteamasawholeis
accountable
13
TheScrumMaster
Responsible forensuringScrumis
understood andenacted
Servant-leadertoteam,helps
thoseoutside ofteamunderstand
whichoftheiractionsarehelpful
orhurtful
14
ToProductOwner
• Helpseffectivelymanage the
backlog
• Helpstheteamunderstandthe
needforclearlyexpressed
backlogitems
• FacilitatesScrumeventsas
needed
ScrumMasterService
ToDevelopmentTeam ToOrganization
• Coachesdevelopmentteam
• Removesimpediments
• FacilitatesScrumeventsas
needed
• LeadsorganizationinScrum
adoption
• PlansScrumimplementations
• Helpsstakeholdersunderstand
Scrumandempiricalproduct
development
ScrumEvents
• TheSprint
• SprintPlanning
• DailyScrum
• SprintReview
• Sprint
• Retrospective16
Createregularity
Opportunitytoinspectandadapt
Minimizemeetings
Failuretoincludereducestransparency
TheSprint
TheheartofScrum
Time-boxedto1monthorless
Consistent durationsthroughout effort
NewSprintstartsafterSprintend
Contains allotherevents
Scopemaybere-negotiated
Canbecanceledifgoalisobsolete
17
TheProductOwner
• GroomsProductBacklogtoprepare
forfutureSprints
• ReviewsPBIwithDevelopment
Team
TheSprint+VSTS
TheDevelopmentTeam TheScrumMaster
• CreatesTasks forPBI
• Keepsboardupdated
• Assures ProductOwnerisgrooming
ProductBacklogforfutureSprints
• ConfirmsDevelopmentTeamis
updatingboard
SprintPlanning
TheworktobeperformedinSprint
Time-boxedto8hoursorless
DevelopmentTeamforecastswork
ScrumTeamcraftsaSprintGoal
DevelopmentTeamdecomposeswork
ScrumTeamandDevelopmentTeam
invitations attend
19
TheProductOwner
• DescribeshighestpriorityProduct
BacklogitemstoDevelopment
Team
• Updatesworkitemsasneeded
• Workstocraftgoalforiteration
SprintPlanning+VSTS
TheDevelopmentTeam TheScrumMaster
• Estimatesworkitemsdescribedby
ProductOwner
• Confirmsappropriateamountof
workisreadyforSprintPlanning
• CapturesDevelopmentTeam
estimates
DailyScrum
DevelopmentTeamdailysync
Time-boxedto15minutes
Inspectworkdoneinprevious 24
hours
Forecastworkinnext24hours
Raiseimpediments toSprintGoal
ScrumMaster/ProductOwner
optional
OnlyDevelopmentTeamparticipates
21
TheProductOwner
• UpdatesProductBacklogasneeded
DailyScrum+VSTS
TheDevelopmentTeam TheScrumMaster
• UpdatesSprintBacklogTasksas
needed
• AssuresDevelopmentTeamis
updatingboard
SprintReview
HeldatendofSprint
Time-boxedto4hoursorless
ProductOwnernavigatesSprintBacklog
DevelopmentTeamdiscusses Sprint
DevelopmentTeamdemoswork
Entiregroupdetermines next
Reviewoftimeline,budget,marketplace
Resultisrevised ProductBacklog
ScrumTeamandstakeholdersinvitedby
ProductOwnerattend
23
TheProductOwner
• Worksthroughademoofthe
completedworkitemsfromthe
SprintBacklog
SprintReview+VSTS
TheDevelopmentTeam TheScrumMaster
• UpdatesSprintBacklogtasksas
needed
• Assures SprintBacklogisupdated
SprintRetrospective
AchanceforScrumTeaminspection
Time-boxedto3hoursorless
OccursafterSprintReview
OccursbeforenextSprintPlanning
ScrumMasterparticipates
InspectslastSprint
Identifygoodandbad
Createaplanforimprovement
ScrumMasterandDevelopmentTeam
attendandparticipate
25
TheProductOwner
• Doesnotattend
SprintRetrospective+VSTS
TheDevelopmentTeam TheScrumMaster
• Outcomeusuallynottrackedin
VSTS
• Outcomeusuallynottrackedin
VSTS
BacklogGrooming
TheunofficialmeetingofScrum
Besttotime-boxit
OccursduringSprint
ScrumTeamattendsand
participates
Focusisontopmostitems
Provides initialestimates
HelpsstreamlineSprintPlanning
ScrumTeamattendsand
participates
27
TheProductOwner
• PreparestopmostProductBacklog
itemsforSprintPlanning
• ConfirmsProductBacklogis
prioritized
BacklogGrooming+VSTS
TheDevelopmentTeam TheScrumMaster
• HelpsgroomProductBacklog • AssistswithProductBacklog
grooming
ScrumArtifacts
• ProductBacklog
• SprintBacklog
29
Providestransparency
Opportunitiesforinspection/adaption
Ensurescommonunderstanding
ProductBacklog
Orderedlist
Everythingthatmightbeneeded
Singlesourceofrequirements
ProductOwnerisresponsible
Nevercomplete
Evolveswiththeproduct
RefinedbyPO/Development Team
Higheritemsmoreclear
30
SprintBacklog
SetofPBIselectedforSprint
Highlyvisible, real-timepictureofwork
Canbesummedatanytime
31
BurnDown
Chart
Displaysremainingeffortovertime
X-axisdisplaystime– days
Y-axisdisplaysremainingeffort– hours
Displaysidealeffortasaguide
Canleadtomicromanagement
32
CumulativeFlow
33
Areadiagramthatdisplaysqueues
X-axisdisplaystime– days
Y-axisdisplayseffort– workitems
Displaysworkitemtimeinvariousstates
Plotstotalscope
Velocity
34
Displayssumofestimatesdelivered
X-axisdisplaysiterations– Sprints
Y-axisdisplaysestimates– storypoints
Hardtogaugeatfirst,usuallystabilizes
Capacity
35
Displaysteam,capacity,activity,timeoff
AddsvisualizationtocapacityduringSprint
Questions?Getintouch.
References
http://agilemanifesto.org/1
http://agilemanifesto.org/principles.html2
http://www.scrumguides.org/3