Your SlideShare is downloading. ×
0
The Future
is Agile
David & Oliver

• David: davidtanzer.net, @dtanzer
• Oliver: source-knights.com, @sourceknights
• both independent softwar...
"Engineers are hired to create
David & Oliver
business value, not to
program things.
Patrick McKenzie

Copyright © 2010 So...
Defining Agile

•
•
•
•
•
•

Responsibility / Trust
Flexibility
People & Interactions
Continuous Delivery / Buildability
B...
Agenda

• Companies
• Teams
• Developers

Copyright © 2010 Source-Knights.com
Voting

39%
“Our company says we are agile but it’s not
really agile”

http://jaxenter.de/polls/Wie-gut-funktioniert-bei-I...
Short history

Companies

Copyright © 2010 Source-Knights.com
Time

Copyright © 2010 Source-Knights.com
Cycle Time & Deployment

• Daily Deployment
• possible?
• really needed?

Copyright © 2010 Source-Knights.com
Cycle Time & Deployment

• Long cycle time
•
•
•
•

solve last year’s problems
late ROI
vulnerable to competition
impact/v...
Cycle Time & Deployment

Copyright © 2010 Source-Knights.com
Quality

Cycle Time & Deployment

Copyright © 2010 Source-Knights.com
"Worried that TDD will slow down
Cycle Time & Deployment
J. B. Rainsberger

Copyright © 2010 Source-Knights.com
Quality vs. speed

• low quality slows you down
• technical debt

• impact on the future
=> Quality AND speed

The general...
Maintaining quality

• Manually testing
• Test department
=> not sufficient for short cycles
• Test driven development
• S...
Maintaining quality

• external feedback via early delivery

Copyright © 2010 Source-Knights.com
Short history

Teams

Copyright © 2010 Source-Knights.com
Self organisation
“Hierarchy is great for maintaining predictability and
repeatability. It simplifies planning and makes i...
Responsibility

“Why does your desk have wheels?
Think of those wheels as a symbolic reminder that you
should always be co...
Responsibility

Pull

Copyright © 2010 Source-Knights.com
Pull

• let the experts decide
• the team knows what they can do
(at least they should ;))
• better distribution of worklo...
Pull

Own
Quality!

Copyright © 2010 Source-Knights.com
This surgery is hard at the budget.
Can you reduce the costs by
skipping something simple?
We can skip washing hands...
(j...
Pull

No!

Copyright © 2010 Source-Knights.com
Own Quality

•
•
•
•
•

Refactoring
Test driven development
Pair Programming
Overload of tasks
Bug managing vs fixing

Cop...
Continuous
improvement

Own Quality

Copyright © 2010 Source-Knights.com
Continuous improvement

•
•
•
•
•

retrospectives
coding dojos
skill meeting
communities of practice
look beyond one’s own...
business@davidtanzer.net
Continuous improvement
oliver.szymanski@source-knights.com

Copyright © 2010 Source-Knights.com
• (c) 2013 Oliver Szymanski & David Tanzer
• Image credits
•
•
•
•
•

Idea:
Delivery:
Bomb:
Wolf:
Leopards:

• All other p...
Upcoming SlideShare
Loading in...5
×

Future is Agile

241

Published on

Introduction to agile

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
241
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Future is Agile"

  1. 1. The Future is Agile
  2. 2. David & Oliver • David: davidtanzer.net, @dtanzer • Oliver: source-knights.com, @sourceknights • both independent software consultants • both striving for simplicity in software development Copyright © 2010 Source-Knights.com
  3. 3. "Engineers are hired to create David & Oliver business value, not to program things. Patrick McKenzie Copyright © 2010 Source-Knights.com
  4. 4. Defining Agile • • • • • • Responsibility / Trust Flexibility People & Interactions Continuous Delivery / Buildability Business Value / Quality Continuous Feature Flow vs. strict dates Copyright © 2010 Source-Knights.com
  5. 5. Agenda • Companies • Teams • Developers Copyright © 2010 Source-Knights.com
  6. 6. Voting 39% “Our company says we are agile but it’s not really agile” http://jaxenter.de/polls/Wie-gut-funktioniert-bei-Ihnen-Agile-Softwareentwicklung-167431 Copyright © 2010 Source-Knights.com
  7. 7. Short history Companies Copyright © 2010 Source-Knights.com
  8. 8. Time Copyright © 2010 Source-Knights.com
  9. 9. Cycle Time & Deployment • Daily Deployment • possible? • really needed? Copyright © 2010 Source-Knights.com
  10. 10. Cycle Time & Deployment • Long cycle time • • • • solve last year’s problems late ROI vulnerable to competition impact/visibility of an issue Copyright © 2010 Source-Knights.com
  11. 11. Cycle Time & Deployment Copyright © 2010 Source-Knights.com
  12. 12. Quality Cycle Time & Deployment Copyright © 2010 Source-Knights.com
  13. 13. "Worried that TDD will slow down Cycle Time & Deployment J. B. Rainsberger Copyright © 2010 Source-Knights.com
  14. 14. Quality vs. speed • low quality slows you down • technical 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 timethey all go hand in hand. Steve McConnell Copyright © 2010 Source-Knights.com
  15. 15. Maintaining quality • Manually testing • Test department => not sufficient for short cycles • Test driven development • Specification by example • Pair programming / Code reviews => fast feedback Copyright © 2010 Source-Knights.com
  16. 16. Maintaining quality • external feedback via early delivery Copyright © 2010 Source-Knights.com
  17. 17. Short history Teams Copyright © 2010 Source-Knights.com
  18. 18. 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
  19. 19. Responsibility “Why does your desk have wheels? Think of those wheels as a symbolic reminder that you should always be considering where you could move yourself to be more valuable.” Valve Handbook for new Employees Copyright © 2010 Source-Knights.com
  20. 20. Responsibility Pull Copyright © 2010 Source-Knights.com
  21. 21. Pull • let the experts decide • the team knows what they can do (at least they should ;)) • better distribution of workload • less idle time • helps optimizing the flow • helps dealing with technical debt by the team Copyright © 2010 Source-Knights.com
  22. 22. Pull Own Quality! Copyright © 2010 Source-Knights.com
  23. 23. This surgery is hard at the budget. Can you reduce the costs by skipping something simple? We can skip washing hands... (just list it as technical debt) Copyright © 2010 Source-Knights.com
  24. 24. Pull No! Copyright © 2010 Source-Knights.com
  25. 25. Own Quality • • • • • Refactoring Test driven development Pair Programming Overload of tasks Bug managing vs fixing Copyright © 2010 Source-Knights.com
  26. 26. Continuous improvement Own Quality Copyright © 2010 Source-Knights.com
  27. 27. Continuous improvement • • • • • retrospectives coding dojos skill meeting communities of practice look beyond one’s own nose Copyright © 2010 Source-Knights.com
  28. 28. business@davidtanzer.net Continuous improvement oliver.szymanski@source-knights.com Copyright © 2010 Source-Knights.com
  29. 29. • (c) 2013 Oliver Szymanski & David Tanzer • Image credits • • • • • Idea: Delivery: Bomb: Wolf: Leopards: • All other photos: David Tanzer Copyright © 2010 Source-Knights.com
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×