Agile PrinciplesAgile People

Gaetano MazzantiGama-Tech

> “Hello, I’m Agile”

“and I’m not alone”

Agile is about

changeculturepeople

organization

projectproduct

Comprehensive

DocumentationProcesses

and Tools

Following

a PlanContractNegotiation

a recipe for success?

“even monkeys could write good software”

“all you need is a good process and good tools”

design

requirements

testing

implementation

do you spot any problem?

A SOFTWARE ODYSSEY

Processes and Tools

Contract Negotiation

Comprehensive Documentation

Following a Plan

1994 Chaos Report(Standish Group)

of projects cancelled31% 53% challenged

1994 Chaos Report(Standish Group)

why projects fail:

lack of user inputincomplete requirements

changing requirements

2002 Chaos Report(Standish Group)

45%of features are never used

software is about

learning, continuously

planning is guessing

estimating is not committing

over Processes and Tools

over Comprehensive Documentation

over Contract Negotiation

over Following a Plan

Individuals and Interactions

Working Software

Customer Collaboration

Responding to Change

2OOI AGILE MANIFESTO:

XP

scrum

kanban

Agile manifesto

Agile timeline

1996

2004

1993

crystal

DSDMcomplexadaptivesystems

EdwardDeming

theory ofconstraints

leanthinking

new new product development

queueingtheory

leandevelopment

2001

“I don’t know what I want,but I know how to get it”

Johnny RottenSex Pistols

deliver value in small evolutionary steps

delay commitment, make decisions at the last responsible moment

build in qualityonly what is needed andonly when is needed

make project statustransparent and visible,highlight issues and impediments

XPrebellious and prescriptive (!)

on site customerfrequent small releasessmall colocated teamspair programmingunit tests / TDDrefactoring. . .

time

cost of change

Agile

traditional

flattening the cost of

change

2010 State of Agile Development Survey

cross-functional team

split & prioritize

timeboxed iterations(sprints)

Scrumused by 58% of Agile adopters

Scrum

productbacklog

sprintbacklog

sprint

deliverable

standupmeeting

scrummaster

productowner

team

demo & retrospective

teamtrusted

respectedsupported

work autonomouslymakes all

day-to-day decisions

managercoach

servant guidance

provides feedback

enable excellence

connects the team to the business

{

frequent and repeated success

builds trust and motivation

0 1 2 3 4 5 6 7 8 9 10 110

50

100

150

200

250

real SP leftideal burndownreal SP left proj

instant feedback

story

poin

ts

days

delay

burndown chart

lean & agile

valuewastepullflow

cadencekaizen

respect for people

Kanban inproduct development

visualizemeasureoptimize

flow

pulllimit WIP (work in process)

}

visualize flow

backlog to do in progress done

backlog to do in progress test done

visualize flowlimit WIP (work in process)measure and optimize flowexplicit policies (limit WIP, pull, definition of ”done”, etc) ->

project and process trasparency

232

lead timelead time

cycle timecycle time

cycle time = WIPthroughput

slide credit: H.Kniberg www.crisp.se

pull

2 31readybacklog to do in progress done

WIP excess

slide inspired by Claudio Perrone

WIP limit

slide inspired by Claudio Perrone

no WIP limit -> queue!

2 3readybacklog to do in progress done

stuck!

2 31readybacklog to do in progress done

2 31readybacklog to do in progress done

up to the team

everyone ownsthe commitment

the processthe delivery

each otherhelps

learning fromeveryone

performingcollaborativesupporting

a highly group

on teams, again

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 200

5

10

15

20

25

30

35

BacklogTo DoIn ProgressDone

cumulative flow diagram

WIP

cycle time

done

in progress

to do

backlog WIP

cycle time

WIP

days

story

poin

ts

throughput

cancelledprojects

challengedprojects

24%

44%

Chaos Report 2009

were31%

were53%

loss of management control

ability to change organizational culture

36%

51%

concerns about Agile adoption

barriers to furtherAgile adoption

2010 State of Agile Development Survey Results

87%

74%

70%

66%

77%

2010 State of Agile Development Survey Results

benefits from Agile implementation

manage changing priorities

increase productivity

accelerate time to market

enhance product quality

improve project visibility

Agile encourages/favors

change

any other methodologysupporting this?

changeis the only constant

Gaetano Mazzanti

Gama-Techinfo@gama-tech.net

photo credits:Flickr, iPhotostock, life.com