future is agile
TRANSCRIPT
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
••
••
Copyright © 2010 Source-Knights.com
David & Oliver"Engineers are hired to create
business value, not to program things.��
Patrick McKenzie
Copyright © 2010 Source-Knights.com
Defining Agile
Responsibility / TrustFlexibilityPeople & InteractionsContinuous Delivery / BuildabilityBusiness Value / QualityContinuous Feature Flow vs. strict dates
••••••
Copyright © 2010 Source-Knights.com
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
Copyright © 2010 Source-Knights.com
Cycle Time & Deployment
Daily Deploymentpossible?really needed?
•••
Copyright © 2010 Source-Knights.com
Cycle Time & Deployment
Long cycle timesolve last year’s problemslate ROIvulnerable to competitionimpact/visibility of an issue
•••••
Copyright © 2010 Source-Knights.com
Cycle Time & Deployment"Worried that TDD will slow down ������������������������� ���������
������������������J. B. Rainsberger
Copyright © 2010 Source-Knights.com
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
Copyright © 2010 Source-Knights.com
Maintaining quality
Manually testingTest department
=> not sufficient for short cycles
Test driven developmentSpecification by examplePair programming / Code reviews
=> fast feedback
••
•••
Copyright © 2010 Source-Knights.com
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
Copyright © 2010 Source-Knights.com
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
Copyright © 2010 Source-Knights.com
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
••
••
••
Copyright © 2010 Source-Knights.com
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)
Copyright © 2010 Source-Knights.com
Own Quality
RefactoringTest driven developmentPair ProgrammingOverload of tasksBug managing vs fixing
•••••
Copyright © 2010 Source-Knights.com
Continuous improvement
retrospectivescoding dojosskill meetingcommunities of practicelook beyond one’s own nose
•••••