fluent@agile - the game

53
fluent@agile - the game The game is a pla2orm for teams to move towards becoming a high impact team by helping them understand where they are, where they are striving to go, and by giving the team a strong feeling of ownership of their journey. This document provides a guide for facilita?ng the game and material for prin?ng and building the game. Chris&an Vikström, Peter Antman (Spo&fy/Crisp) 2014 [email protected] chris?an.vikstrom@spo?fy.com

Upload: dophuc

Post on 03-Jan-2017

235 views

Category:

Documents


3 download

TRANSCRIPT

Page 1: fluent@agile - the game

fluent@agile-thegame

Thegameisapla2ormforteamstomovetowardsbecomingahighimpactteambyhelpingthemunderstandwheretheyare,wheretheyarestrivingtogo,andbygivingtheteamastrongfeelingofownershipoftheirjourney.

Thisdocumentprovidesaguideforfacilita?ngthegameandmaterialfor

prin?ngandbuildingthegame.

Chris&anVikström,PeterAntman(Spo&fy/Crisp)2014

[email protected]?an.vikstrom@spo?fy.com

Page 2: fluent@agile - the game

Threepillarsforthegame•  Basedonamodel:Thegameisbasedonamodelforhow

teamsusuallymovesontheirjourneyfrom“pre-agile”tohighimpactagileteams.

•  Visualiza0on:Webelievethatvisualizingisasuperstrongwaytobuildsharedunderstanding,engagementandcollabora?on.

•  Ownership:Thegameisbuiltsothatteamscantakeastrongownershipovertheirjourneytowardsbecomingahighimpac?ngagileteam.

Page 3: fluent@agile - the game

Agile Fluency*

WorkthePlan Learn&Adjust

*Thefluent@agilegameisheavilybasedonthe“YourPaththroughAgileFluency”byDianaLarsenandJamesShore

Successfulcompaniesopera?ngateachlevel

???

??????????

Fitforpurpose–theamountoffluencyyouwantdependsonyourneeds!

Page 4: fluent@agile - the game

FluencyishowateamdevelopssoIwarewhenit’sunderpressure.Anyonecanfollowasetofprac?ceswhengiven?metofocusinaclassroom;truefluencyisaskillful,rou?neprac?cethatpersistswhenyourmindisdistractedwithotherthings.ForAgile,we’reconsideringteamfluencyratherthanindividualororganiza?onalfluency.Agiledevelopmentisfundamentallyateameffort,andyourorganiza?on’ssuccesswithAgilewilldependonthefluencyofyourteams.Teamfluencyalsodependsonmanagementstructures,rela?onships,organiza?onalculture,andmore.Don’tmakethemistakeofblamingindividualsforlowteamfluency,orassumingthatonehighly-skilledindividualwillguaranteehighteamfluency

Proficiencyvs.Fluency:Fluencyisunconsciouscompetence;howwellyoudounderpressure

Page 5: fluent@agile - the game

We’veseenthatteamsprogressfasterwhentheyprac?ceadvancedtechniquesalongsidebasictechniques.Teams’prac?cesbecomemoredeeplyandreliablygroundedwhentheyworkthisway.So,it’sbesttochoosetheleveloffluencyyouwanttoachieveandtoprac?ceeverythingneededforthatlevelfromthebeginning.

Chooseyourleveloffluency

Page 6: fluent@agile - the game

DifferentapproachestofacilitateWebelievethatoneofthepillarsforthegametobesuccessfulisthattheteamfeelsastrongownershipoverthegameandtheirimprovementwork.Ourexperienceisthatwhenwefacilitateinawaywherewelistentotheteamandtrytoadaptourfacilita?onalongthewaymakesiteasierfortheteamtotakethatownership.Possiblewaystofacilitate:1.   Presentthemodelapproach:Presentthemodel/gameandlettheteambuild

thegameandthendecideonwhatprac?cestheywanttoworkongeVngfluentonnext.Establishthevalue/goalsofimplemen?ngtheprac?ces.WriteoneorseveralimprovementstoriesasfirststepstowardsgeVngfluentattheprac?ces.

2.   Musicmetaphorapproach:Presentthemusicmetaphor.Eitherbypresen?ngityourselforbyfacilita?ngadiscussionthatbuildsthemetaphor.Lettheteam(s)buildtheirmodelsusingatrainingfromthebackoftheroomapproach.

3.   Trainingfromthebackoftheroomapproach:Givetheteamminimalinstruc?onstogetstartedwiththegame,stayavailablefortheteamtopullinforma?onorgivedirec?oniftheteamgetsstuckormisunderstandhowtoplaythegame.

Page 7: fluent@agile - the game

PresenttheModelapproacho  Introduc?ontothemodel/game.

o  Putthedifferentlevelsuponthewall.Describeshortlywhateachlevelmeans,stayopentoanswerques?onsorhaveshortdiscussionswiththeteamoneachlevel.

o  Teamdiscussion:“Atwhatlevelinthemodeldoyouasateamwanttogetfluent?”–  “Areyoufluentonanyofthelevelsalready?”–  “Wherewouldyouliketobeasasquad?”–  “Onapersonallevel,wheredoyouthinkyouwouldbemostsa?sfied?”o  Iftheteamseemsopentoityoumightevengoforaconsensusdecisiononthis.

o  “Whatprac?cesdoyoubelieveyouneedtobefluentattobeabletobefluentatallthelevelsuptothelevelyouareaimingat?”o  Lettheteamgothroughalltheprac?cesnotesanddiscusswhichonestheyare:(“teachingmoments”oIenariseherewhenteammembers

askwhatspecificprac?cesare,andwhattheyaregoodfor:)o  Fluentat(putthemontheroad)o  Prac?cing(putthembesidestheroad)o  Needtodo(putthemunderthe“driverslicense”)o  Don’tneed(putthemunder“Park”)

o  “Arethereanyprac?cesmissinginthegamethatyouarealreadydoingorthatyouthinkyouneedtobedoing?”o  “Isthereanyprac?cesthatwecanremoveands?llgetfluent?”

o  Nextprac?ce(s)togetfluentat:o  Createatargetcondi?on:

o  Lettheteampicksomethingtheywanttostartworkingontogetfluentat,e.g.bydot-vo?ng.o  Discussanddefinewhatitwouldmeanfortheteamiftheygotfluentattheprac?ce(s).E.g.bybrainstormingpost-itsonthepossiblebenefits,then

discussandgroupthem;nowyouhaveagoal/targetcondi?on.o  Writeimprovementstoriesthatdescribesthefirststepstotaketomovetowardsfluency.

o  Howtointegratethisimprovementworktoyourdailywork:o  Discusshowtheteamwillmakethishappenaspartoftheirdailywork.E.g.:

o  Theimprovementsstoriesarepriori?zedtogetherwiththerestoftheirworkinthebacklog.o  Havingweeklymee?ngstoplan/groomtheirimprovementwork.

o  Op?onalperspec?ves:o  “Giventhepaceofimprovementworkwearecurrentlyhavingintheteam-howlongdoyouthinkthatitwouldtakeforyourteamtoget

fluentatalltheprac?cesthatyouhavelisted?””o  “Doyoubelievethatitwouldbevaluableforyourteamandfortheorganiza?ontoincreasethepaceofimprovementwork?”

Page 8: fluent@agile - the game

Trainingfromthebackoftheroomapproach

•  Doareallyshortpresenta?onofthelevel(s)youwanttofocusonandthengivethissheetofques?onstodirectthemduringtheworkshop

Page 9: fluent@agile - the game

Prepara?onsforfacilita?ng•  PrinttheGame(s)(oneforeachsquad)(seebelow

onhowtodothis).Putinanenvelopeandwritethe“userstory”onit,orjustwritethesquadname.

•  Makesureyouhave:–  enoughhäImassa(thes?ckystuffyouputontheback

ofthenotestos?ckthemtoawall)ifyouwillbuildthegameonthewall/whiteboard

–  Post-itsoftherightcolorandsize;sothattheteamcanwritenew“prac?cesnotes”(i.e.orange,yellow,green&pink);analterna?veisthattheywritethenewprac?cesonblankprac?cenotes

–  Sharpies–  Scissors(unlessyoucutthepapersbeforehand)–  Op?onal:Amovableboardthatyoucanbringfrom

yourworkshoptoyoursquadarea(withyourbuiltgameon:).

“UserStory”AsaSquadWewanttovisualizeandgetasharedunderstandingofourcurrentwayofworkingandourvisionofhowweasahighimpactteamwouldworkSothatwecantakeownershipovercon?nuousimprovementstowardsbecominganhighimpactteam

Envelopetoteam

Page 10: fluent@agile - the game

Anexampleonhowagamecouldlooklikeforateam

Seemore:-OurtalkatAgileSverige(inswedish)-Fluent_agile-as2014.pptx

Page 11: fluent@agile - the game

Buildingthegame

•  Printthegame;onecopyforeachteam(seeinstruc?onsbelow)

•  Laminatethesheets(thereisalamina?onmachineon10thfloorintheprinterroom*)

•  Putthesheetsinanenvelope

*Spo&fyStockholmofficespecificinfoJ

Page 12: fluent@agile - the game

Buildingthegame:

Prin0ng

Makesureto:-  Scaletofitpaper-  Two-sided:Short-edgebinding-  Settherangeofslidestoprint

(firstslideisthe“Focusontechnicaltasks”slide)

Page 13: fluent@agile - the game

Prin?ngstartsaIerthisslide!!

Page 14: fluent@agile - the game

Focus On

Technical Tasks

Page 15: fluent@agile - the game

Individualsorlooselycoupledteamsthatworkinanadhocmannerorfollowingaplan.ThisstateisoIencharacterizedbyhavingaPMs,Gankcharts,detailedandcomprehensivespecs.Oritcanbeveryadhocandreac?ngonstakeholderneeds.Thisstatemightresemblethe“Op?mizeValue”orthe“Op?mizeforSystem”states.

Pre-Agile

Page 16: fluent@agile - the game

Focus on

Value

Deliver Value

Page 17: fluent@agile - the game

You’llhavegreatervisibilityintowhatyourteamsareworkingon,andyou’llbeabletodirectthemtowardsthe20%oftheworkthatprovides80%ofthevalue.

Ittakes2–6monthsofprac?cetoshiIfromindependentindividualcontributorstoacollabora0ve,team-basedworkplace.Theteammayneedmoreaken?onfromtheorganiza?onintermsofinforma?onaboutbusinesspriori?esandcustomervalueaswell.

Teammembersmustlearntoplanintermsofbusinessresultsratherthantechnology,andtheymustlearntotakeresponsibilityforthesuccessofthewholeteamratherthantheircontribu?onasindividuals.ScrumandKanbanaremethodsusedatthislevel.

You’llseemuchhigherqualitysoIwareanddrama?callyimprovedresponsiveness,shippedasoIenasthemarketwillbear.

Toreachfluencyatthethislevel,studyandprac0cetechniquessuchasthosedescribedbyExtremeProgramming,SoIwareCraIsmanship,DevOps,andAgilesoIwarequalitygurus.Some,suchastest-drivendevelopment,areofthe“momentstolearn,life&metomaster”variety.

Developingteammembers’skillstothepointoffluencytakes?meandsignificanteffort,oIen3–24month.Produc?vitywilloIendecreaseastheteamlearnsnewskillsandpaysofftechnicaldebtinexis?ngcode.

AgileFundamentalsAgileSustainability

Page 18: fluent@agile - the game

Optimize Value

Optimize for

Systems

Page 19: fluent@agile - the game

Theteamunderstandwhatthemarketwants,whatyourbusinessneeds,andhowtomeetthoseneeds.Or,asinastartupenvironment,theyknowwhattheyneedtolearnandhowtogoaboutlearningit.

AchievingthisleveloffluencyoIentakesseveralyears--notbecauseoftheskillsrequired,butbecausepeopleintheorganiza0onmustlearntotrusttheteamanditsuseofAgilebeforemakingchangesthataffecttheirpower,control,andfamiliarwaysofworking.

Itrequiresteamstoincorporatebusinessexpertsasfull-?meteammembers.LeanStartup,LeanSoIwareDevelopmentareuseful.Agilechartering,embeddedproductmanagementteams,customerdiscovery,andadap?veplanningareallexamplesoftechniquesused.

Teamscontributetoenterprise-widesuccess.Teammembersunderstandorganiza?onalpriori?esandbusinessdirec?onandwillsacrificetheirownneedstosupporttheneedsofaproductmorecri?caltobusinesssuccess.

RequiresshiIingorganiza?onalculturetofocusonthewholesystem,italsorequiresworkingatthebleedingedgeofAgileprac?ceandpoten?allyinven?ngnewwaysofapplyingsystemsthinkingtoAgile.

Formostorganiza?ons,thisleveloffluencyisprobablybestleIasanaspira?onforthefuture.However,ifyou’vedonetheworktobuildandsupportmul?pleteamswithsolidthree-starfluency,youmaybemostofthewaythere.

ThePromiseofAgileAgile’sFuture

Page 20: fluent@agile - the game

“A team that works together to focus on creating business value rather than merely finishing technical tasks”

“A team with the ability to create and ship low defect software as frequently as the market will accept it”

2star 1star

“A team that collaborates with other teams to optimize the value produced by the whole organization”

“A team that dances and turns in response to changing market conditions, and collectively take responsibility for building the best product your investment can buy”

3star 4star

Page 21: fluent@agile - the game
Page 22: fluent@agile - the game

Team Culture Shift

Team Skills Shift

Organizational Culture Shift

Organizational Structure Shift

Page 23: fluent@agile - the game
Page 24: fluent@agile - the game

User Stories Small Stories

PO has product vision

Transparent PO

In team

Focus on Customer

Value Roadmap

Prioritization of work is

clear

Regular Planning

Product Backlog

Autonomous Backlog

Grooming Have DoD

Visualizing all work

Known Velocity

Estimation by team

Trust Good Daily Standups

Burndown Chart

Iterations

Share Responsibility

Self-organizing

Cross-functional

Demo Delivers end-

to-end

Page 25: fluent@agile - the game
Page 26: fluent@agile - the game

Deliver working

software every iteration

Visualization Retrospectives Explicit Way of Working

Removes Impediments

Usable Mission

Team size max 9

Scrum WIP limits Kanban

Co-located

Page 27: fluent@agile - the game
Page 28: fluent@agile - the game

Operational Responsibility

Dependencies Understood

Design Guidelines

Stable Throughput

Continuous Improvement

Cycle Time Working Software

Easy to on-board new

members

Collective Code

Ownership DRY

Continuous Refactoring

stop-the-line Culture CD

Evolutionary Design XP

BDD DDD Pair Programming

Monitoring of systems

Code Review

CI Testing fully

integrated part of Process

Zero Bugs Culture TDD Dev Ops

Page 29: fluent@agile - the game
Page 30: fluent@agile - the game

Post-mortems Anyone in

the team can deploy

No branches Feature Flags Automatic

Deploy

YAGNI Collective Quality

Ownership Unit Testing

Managing Tech Debt

System Testing

No Warnings in

Builds

Mob Code Review

Page 31: fluent@agile - the game
Page 32: fluent@agile - the game

Lead time Lean Startup Embedded

PM User Story

Maps Impact

Mapping

A/B-testing

Customer Discovery

Hypothesis UX & Design

is Squad Responsibility

Decisions informed by

Business Metrics

Direction based on Learning

Automatic Rollback

Key Designs validated with

real Users

Innovation Accounting

Mob Programming

Monitoring User

Behavior

Testing in Production

Validated Learning

Design in Squad

No Estimates

Page 33: fluent@agile - the game
Page 34: fluent@agile - the game

Radical Self-organization

Tangential business

stakeholders integrated in

team

From concept to cash, beyond squad

Value stream analysis on

whole system

Adapt to the need of the

system

Never blocked by external

factors

No defined roles

Bleeding edge agile

Page 35: fluent@agile - the game
Page 36: fluent@agile - the game

P AGILE DRIVERS LICENSE

Awesome Squad!

Page 37: fluent@agile - the game
Page 38: fluent@agile - the game

“Our Awesome vision”

*Pleaseupdatethevisionstatementinthisslidetofityourorganiza?on.Orasanalterna?vehaveadiscussionintheteamaboutwhattheyseeastheirvision.

Page 39: fluent@agile - the game
Page 40: fluent@agile - the game

Hobbymusician/Studioar?st/Soloar?st

Amusicianthatplaysbyherself.

Couldbeahobbymusicianoraprofessionalstudiomusicianorasoloar?st

Thepersonalskilllevelcanspanfromnovicetoworldclass...

Page 41: fluent@agile - the game
Page 42: fluent@agile - the game

BandCrea?ngmusictogethersimultaneously

Playothersmusic.

Playwhattheaudiencewantthemtoplay.

Havearepertoire.

UsuallyplaysatweddingsandaIer-skiordansband.

Canbeverysuccessful;e.g.???...

Page 43: fluent@agile - the game
Page 44: fluent@agile - the game

Symphonyorchestra

Superskilledmusicians

Playingbynotes

Directedbyaconductor

Page 45: fluent@agile - the game
Page 46: fluent@agile - the game

Successfulbandincontroloftheirmusic

Incontroloftheirmusic.

Theywrite,produceandrecordit.

Mightevenhavetheirownrecordcompany.

Deliveringmusicthatpeoplelike.

Page 47: fluent@agile - the game
Page 48: fluent@agile - the game

Improvising(symphony)orchestracrea?ngfantas?cmusicinthemoment

Noconductor.

Nonotes.

Canusesignalsandsignstogivedirec?on.

Everyperformanceisunique.

THELONDONIMPROVISERSORCHESTRA

Page 49: fluent@agile - the game
Page 50: fluent@agile - the game

Prin?ngStopsbeforethisslide!!

Page 51: fluent@agile - the game

Slideswithmaterialnotyetusedorthrownaway(i.e.ignorethem...)

Page 52: fluent@agile - the game
Page 53: fluent@agile - the game

Sparepics