Agile (mal)Practices Considered Harmful
Post on 22-Jan-2018
244 Views
Preview:
Transcript
…anAgilecoach
33
Ò VuTungLamÒ AgileCoach&Trainer,WhyInnovation!
Ò ExpertinAgileTraining&Coaching,AgileTransformation&Scaling,Leadership, ITOrganization&Management.
Ò Havesuccessfullyguidedcompaniesofvariedsize(fromasingleteamtomultiple teamsgeographicallydistributed)through theirtransformationtohigherAgilefluency.
Ò ExperiencesscalingAgiletransformation tomultiple teams,multipledepartmentsbeyond IT.
Ò PracticalapproachforAgileimplementationwithacombinationScrum,XP,Kanban,Lean,DevOps,LeSS andSAFe.
Ò Decadeofexperiencemanaging,building engineeringteamandimplementing besttechnicalpracticessuchaspair-programming, unittesting, testdriven,automation,CI/CD.
StoryPoints-basedEstimation
36
• Relativeestimationtechnique:bycomparisonorbygroupingofitemsofequivalentdifficulty,insteadofestimationinabsoluteunitsoftime
• Itofferssomeusefulinformation• Notmoreaccurate• Inflatable• Languagebarrier
• …couldhavebeenmorecosteffective
38
Costeffectivetool… but
Perhapsjustcounttheitems…• Whatifastoryistoobig?– Doesthisstoryfitintoasprint?– Ifnotsplititupintotwo…• Iftheystilldon’tfit,splitthemfurther…
• Focusattentiontodeliverycustomervalueinsteadofdelieveryingtasks
39
Scaffolding
40
• “Scaffolding,alsocalled scaffold orstaging,isatemporarystructureusedtosupportaworkcrewandmaterialstoaidintheconstruction,maintenanceandrepairofbuildings,bridgesandallothermanmadestructures.“
• Storypointsareusefultoteachteamadifferentmentalitywhenitcomestoestimation• Toberemovedoncetheteamhasmasteredtheideaandbecomemature
Isitnecessary?• Verywaterfall-ish• Moretimeconsumingthannecessary• Mainlyusedtoconstructburndown chart– “Let’shaveaprettychart”syndrome
• Estimationbecomesthegoalofthetechnicalplanningexercise– Insteadofhavingameaningfuldiscussionabouttechnicalsolution
43
TeamA
• Estimatestoriesinpoints• Estimatetasksinhours• Sprintburndown chartcreatedandupdatedondailybasis
• Fasterceremonies,nicegraphs• Moresurprises
TeamB
• Splitstoriesuntiltheyfitinsprint• Focusonthetechnicaldiscussion,captureoutputsintasks• Butmakesuretasksare<2days
• Longerbutdeeperdiscussion• Morecreativity
44
Ataleoftwoteams…
Theessence• Focusontheconversation,don’tletestimationgetsintheway• Thetechnicalsolutionmattersmore• Itdoesn’tmatterhowlongittakes– Aslongaseachtaskcanbereasonablyachievedbyteaminlessthen1-2days
• Burndown chart?– Removeit–Orjustcountthenumberoftasks–Orjusttrackpoints/storiesburndowninstead
45
HappierTeam
Pickyour tools appropriatelyTasksFeatures
1. Don’t estimate features. Just count them.
2. Estimate features in t-shirt size
1. Skip tasks
2. Don’t estimate tasks. Just count them.
3. Estimate tasks in days1d2d0.5d
4. Estimate tasks in hours12h8h4h
S M LHours?Days?
Weeks?
S ML
3. Estimate features in story points
1sp 2sp5sp
4. Estimate features in ideal man-days
1d 3d 6d
HenrikKniberg
Predictingthefuture…• Whencanweshipthisfeature?• Whatcanweshipinthenextreleasecycle?• Whatourroadmapisgoingtolooklike?
• Howdowecoordinateinter-teamsefforts?
48
Observations• Usefulforcommunication,buildingconsensus…• Usefulforinter-teamsdependencies• Addingalotofassumptionsasrequirements• Usuallyleadtothediscussionofscope,commitmentanddeadlines• Fairlyinaccurate
50
From
• Howtoestimateaccurately• Howtoanticipatechanges• Deliveringsoftware• Meetdeadlines• Resolvingdependencies
To
• Howtomakeestimationinsignificant• Howtofacilitatechanges• Deliveringcustomervalue• Meetbusinessobjectives• Abilitytodeliveryfast,frequentlywithhighvalue
51
Ashiftofmindset…
top related