just enough minimal viable agile

Post on 12-Jan-2017

180 Views

Category:

Technology

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

Just Enough: Minimally Viable Agile

TroyTu'leLeanAgileCoachKanFlow.comtroy@kanflow.com@troytu:le

Learningisnotcompulsory...neitherissurvival.-W.EdwardsDeming

The Agile Dysfunction Spiral

Detailedsprintplanning

Formalsprintcommitment

WorkthesprintUnfinishedwork

Weneedtogetbe:erat

planningsprints

Coachingtohelpimprovesprintplanning

Sprintplanningtakeslonger

ManagementAppliespressure

CultureofBlamecreepsbackin…

TeamworksoverIme

ArewereallyjustaKerbe#ersprints?

The Agile Dysfunction Spiral

Detailedsprintplanning

Formalsprintcommitment

WorkthesprintUnfinishedwork

Weneedtogetbe:erat

planningsprints

Coachingtohelpimprovesprintplanning

Sprintplanningtakeslonger

ManagementAppliespressure

CultureofBlamecreepsbackin…

TeamworksoverIme

ArewereallyjustaKerbe#ersprints?

Which is why we see…

(ActualGooglesearches,BTW)

Minimally Viable Agile

Borrowing from the Product Development concept of Minimum Viable Product. "The minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort."

What is it?

Minimally Viable Agile

Minimally Viable Agile is a search for Agile practices and ceremonies, informed by Lean and Agile theory, that produces the maximum amount of customer value, with the least amount of effort.

What is it?

MinimallyViableAgileisamindsetwheredecentralizedAgileinnova@oniscul@vated.

Or(JustEnoughpracIcesandceremoniestobeeffecIve).

Cargo Cult (Agile)

ManyearlyAgilea:emptssimplyinstalledpracIces(recipes).

Warning!FollowingrecipesleadstoCargoCultAgile

Mob Programming

--AaronGriffith,WoodyZuill,LlewellynFalco

Mob Programming: An original MVA? ReducesorEliminates:1.  StanduporotheralignmentmeeIngs2.  Detailedplanning-onlysessions3.  TheneedforesImates4.  ContextSwitching5.  Burn-downchartsforperformancetracking6.  CodeReviews

Increases:1.  Quality2.  CollaboraIon3.  ProducIvity4.  SaIsfacIon

Mob Programming: Why does it work? SampleImelineofauserstoryorrequirement.

Time2

=waitIme

weeks =touchIme

weeks

4-10 4-10 2

CustomerRequest

PrioriIzedinProductBacklog

BacklogGroomingPlanningIntoaSprint

StoryCompleted

(tacitknowledgedecay)

Minimally Viable Agile Canvas

Focus Learning

Simplicity CustomerValue

•  WorkVisualizaIons•  WIPlimits/smallerbatches•  Cadence/Time-boxes

•  RetrospecIves/ImprovementKata•  AcceptanceTestDrivenDevelopment•  ConInuousIntegraIon/Delivery

•  EmergentArchitecture•  Artoftheworknotdone

•  DefiniIonofDone•  Progressmeasuredinworking

soKware

RespectforPeople•  Sustainablepace•  Purpose,Autonomy,Mastery

(CollaboraIon)

Visceral Reaction Disclaimer

Wemightcoversome“controversial”topics.

Minimum Viable Agile

Let’stakeacloserlookatsomepopularAgilepracIces.

1.  StoryPointbasedVelocity2.  BurnDowncharts

Thisismyjourney,yourmileagemayvary!

Story Points based Velocity

Story Point Predictability?

CourtesyofBennetVallet

DirectorofDevelopment

SiemensHealthServices

ExpectedDistribuIonActualDistribuIon

Minimalist Planning

OpAon#1Hours-longtradiIonalsprintplanningmeeIngsspentplayingplanningpokerandateamarguingaboutthedifferencebetween2’sand3’s.

OpAon#2ShortstoryslicingmeeIngwherethefocusisonunderstandingandslicinglargestories.“Doweunderstandthisstory?Ifnot,let’skeepslicing.”

1 2 3 5 8 13 21 40 100

Right-sizingthework

Minimalist Planning

InputQ Design Develop Test Done

3

1 2

9

7

8

6

4

5

Cycle Time

Throughput

10

14daysfromthispoint

5storiesperweek

ProbabilisIcForecasIngispreferred!

ForExample:-85%certainonecarddelivered<20days-75%certain50storiesdeliveredin15weeks

Burn Down Charts

Whydoweassumethisisthewrongplaceforthisteamtobe?

Work

Time

Nature of the Work

Manufacturing=repeatableprocessesProductDevelopment=oneImeprocesses

One-Imeprocessesarenon-determinisAcinnature

Nature of the Work

DeterminisAcApproach

ProjectStart

Knowledge

“Complete”PlannedAcIvity

Non-determinisAcReality

ProjectStart

Knowledge

“Complete”?

WhatCustomerReallyWantsBe:erKnowledge

ProjectManagersinthemiddle,pullingouttheirhair

Burn Down Charts

Evenifthisisaproblem,whatexactlydowedonow?

Work

Time

It’snotacAonable!

Burn Down Charts (refactored)

AcAonableInformaAon!

Burn Down Charts (refactored)

(fromAc@onableAgile.com)

Work

Time

AcIonableInformaIon!

Minimally Viable Agile While there is value in the items on

the right, we value the items on the left more.

Flow-basedmetricsandvisualizaAonsoverburndowncharts

StoryslicingskillsoveresImaIonschemes

(...)

Applying Minimally Viable Agile

We can apply MVA thinking in two forms:

TrainingandeducaIon

HowwetransiIon

“We’regoingtostopcreaIngburndownchartsandstopusingvelocity.”

“Areyouinsane?”

Improvement Kata

Awesome

CurrentCondiAon

OurVision

NextTargetCondiAon

Steps:PDCA

P

D

C

A

Improvement Kata

ImprovementTheme

Now/CurrentCondiAon

NextTargetCondiAon

DefiniAonofAwesome(vision)

FirstSteps

--JimmyJanien,CrispBlog

Improvement Kata PracIcalToyotaKataFormat:

Improvement Kata

Improvement Kata

MergeDay ConInuousIntegraIon

Minimally Viable Agile Summary

Focus Learning Simplicity

CustomerValueRespectforPeople

UnderstandtheWhybehindLeanandAgile,asyourinoculaIonagainstCargoCultAgile.

DecentralizetheAgileInnovaIon.

FocusonAwesome,anddeliberatelyworktowardsthatvision,andtheprocesscruKwillfallaway.

MinimallyViableAgileCanvas:

Just Enough: Minimally Viable Agile

TroyTu'leLeanAgileCoachKanFlow.comtroy@kanflow.com@troytu:le

Learningisnotcompulsory...neitherissurvival.-W.EdwardsDeming

References A Day of Mobbing, Aaron Griffith, Woody Zuill, Llewellyn Falco. Improvement Theme – Simple and practical Toyota Kata, Jimmy Janien, Crisp’s Blog (http://goo.gl/beHbNp) Toyota Kata, Mike Rother Drive, Daniel Pink Lean Startup, Eric Reis Kanban at Scale – A Siemens Success Story, Bennet Vallet CFD generated from ActionableAgile.com

top related