future is agile

The Futureis Agile

Copyright © 2010 Source-Knights.com

David & Oliver

David: davidtanzer.net, @dtanzerOliver: source-knights.com, @sourceknights

both independent software consultantsboth striving for simplicity in software development

••

••


David & Oliver"Engineers are hired to create

business value, not to program things.��

Patrick McKenzie


Defining Agile

Responsibility / TrustFlexibilityPeople & InteractionsContinuous Delivery / BuildabilityBusiness Value / QualityContinuous Feature Flow vs. strict dates

••••••


Agenda

CompaniesTeamsDevelopers

•••


Voting

“Our company says we are agile but it’s notreally agile”

39%

http://jaxenter.de/polls/Wie-gut-funktioniert-bei-Ihnen-Agile-Softwareentwicklung-167431


Short history

Companies


Time


Cycle Time & Deployment

Daily Deploymentpossible?really needed?

•••



Long cycle timesolve last year’s problemslate ROIvulnerable to competitionimpact/visibility of an issue

•••••


Cycle Time & DeploymentQuality


Cycle Time & Deployment"Worried that TDD will slow down ��

��J. B. Rainsberger


Quality vs. speed

low quality slows you downtechnical debt

impact on the future

=> Quality AND speed

••

•

The general principle of software quality is:Improving quality reduces development cost.

You don’t have to choose between quality, cost and time-they all go hand in hand.

Steve McConnell


Maintaining quality

Manually testingTest department

=> not sufficient for short cycles

Test driven developmentSpecification by examplePair programming / Code reviews

=> fast feedback

••

•••


Maintaining quality

external feedback via early delivery•


Short history

Teams


Self organisation

“Hierarchy is great for maintaining predictability and repeatability. It simplifies planning and makes it easier to control a large group of people from the top down, which

is why military organizations rely on it so heavily.

But when you’re an entertainment company that’s spent the last decade going out of its way to recruit the most intelligent, innovative, talented people on Earth, telling

them to sit at a desk and do what they’re told obliterates 99 percent of their value.”

Valve Handbook for new Employees


Responsibility

“Why does your desk have wheels?

Think of those wheels as a symbolic reminder that youshould always be considering where you could move

yourself to be more valuable.”Valve Handbook for new Employees


Responsibility Pull


Pull

let the experts decidethe team knows what they can do

(at least they should ;))better distribution of workload

less idle timehelps optimizing the flowhelps dealing with technical debt by the team

••

••

••


Pull OwnQuality!


This surgery is hard at the budget. Can you reduce the costs byskipping something simple?

We can skip washing hands...(just list it as technical debt)


Pull

No!


Own Quality

RefactoringTest driven developmentPair ProgrammingOverload of tasksBug managing vs fixing

•••••


Own QualityContinuousimprovement


Continuous improvement

retrospectivescoding dojosskill meetingcommunities of practicelook beyond one’s own nose

•••••


Continuous [email protected]

[email protected]


(c) 2013 Oliver Szymanski & David TanzerImage credits

Idea:Delivery:Bomb:Wolf:Leopards:

All other photos: David Tanzer

•••••••

•

future is agile

Technology

speedlow quality

new employeescopyright

createbusiness value

software developmentcopyright

valve handbook

comshort historyteamscopyright

comdavid oliverengineers

comdavid oliverdavid