Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Introduction to AGILE          31. March 2011Jeppe Cramon – jeppe@tigerteam.dk
Does this sound familiar?• “We are doing Agile so we”:  •   Do not Document  •   Do not handle and register Requirements  ...
From the movie “Clueless”
Same procedure as last year?“Even a dead fish can float down a waterfall”
Can 9 women deliver a baby in 1 month? • More developers on a project decreases   developer efficiency   – Communication o...
Why Agile?•   Focus on the Business and what they need•   Focus on delivering quality•   Doing the “right thing” – not jus...
We need an Agile Machine!
Who?• Take 17 IT gurus:  – Kent Beck, Alistair Cockburn, Martin Fowler,…  – Add them to a ski resort in Utah• Let them sim...
What? The Agile ManifestoWe are uncovering better ways of developing software by doing it and helping others              ...
According to the Oxford Dictionary• Agile  – “Able to move Quickly and Easily”  – “Able to think Quickly and in an Intelli...
Can be?Confusing                               Unified Process             XP                   Scrum                  AGI...
eXtreme Programming (XP)                                 Iteration Plan                                 Iterations plan   ...
XP Practices•   The Planning Game     •   Pair Programming•   Small Releases        •   Collective Ownership•   Metaphor  ...
ScrumProject Management Practices
Scrum Practices•   Self managed teams                • Estimates are made by those•   30 days iterations, Sprints         ...
How they compare?                                                                                      Waterfall(One itera...
So, What’s next?
Please…..• Agile is not a solution. It’s a tool!   – Focus on your problems and how to solve them• There is no such thing ...
Pretty Please……..• Apply your learnings iteratively – It’s the least  expensive way• Pick the right tools for the right jo...
With sugar on top…….We need:• Smaller teams (5-10 people)• More skilled developers and managers• Close contact to Product ...
Excerpts from a 3 hour seminar on how to fail with Agile and Iterative Development
Failing with Iterations• Waterfall iterations   – “Analysis iteration”, “Design Iteration”….• Remember to minimize technic...
Failing on a Management level• Unclear goals. What are we trying to achieve?• Method = Product   – Buy a license and a con...
Failing on a larger scale• Agile affects the whole organization  – Users, business, management, test, deployment,..• Under...
What to do?• Communication, communication, …  – Make sure to involve people in the process  – Listen, Learn and Adapt  – I...
How to supercharge AgilityA “radical” shift – to a larger degree of automation                     
Lean & AgileAre both treatmenting Symptoms      not providing a cure!
We can’t control everythingRather than focus on being Agile which may lead to beingsuccessful, focus on being successful, ...
ThanksFor more informationjeppe@tigerteam.dk         or @jeppec on Twitter
Upcoming SlideShare
Loading in …5
×

Intro to agile

1,824 views

Published on

Introduction to what Agile development is, what it isn't, recommendations and the common pitfalls.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Intro to agile

  1. 1. Introduction to AGILE 31. March 2011Jeppe Cramon – jeppe@tigerteam.dk
  2. 2. Does this sound familiar?• “We are doing Agile so we”: • Do not Document • Do not handle and register Requirements • Do not do formalized testing • Do not plan more than 2 days in advance • Do not follow up on expenses and economy • Do not ____________________ (Fill in yourself)
  3. 3. From the movie “Clueless”
  4. 4. Same procedure as last year?“Even a dead fish can float down a waterfall”
  5. 5. Can 9 women deliver a baby in 1 month? • More developers on a project decreases developer efficiency – Communication overhead – More ceremony (Documents and Process) • Close contact with product owner and business experts leads to effective developers • Writing code typically only amounts to 30% of the total project time
  6. 6. Why Agile?• Focus on the Business and what they need• Focus on delivering quality• Doing the “right thing” – not just doing things right• Get feed-back often and act on it• Work on things that directly improves the end result• Minimize overhead Do what we are paid for as Developers!
  7. 7. We need an Agile Machine!
  8. 8. Who?• Take 17 IT gurus: – Kent Beck, Alistair Cockburn, Martin Fowler,… – Add them to a ski resort in Utah• Let them simmer for 2 days: – February 11-13 2001• You can now serve: – The Agile Manifesto, The Agile Principles – Agile Software Development Alliance
  9. 9. What? The Agile ManifestoWe are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
  10. 10. According to the Oxford Dictionary• Agile – “Able to move Quickly and Easily” – “Able to think Quickly and in an Intelligent way”• Adaptive – “Concerned with Change” – “Able to change when necessary in order to deal with different situations”
  11. 11. Can be?Confusing Unified Process XP Scrum AGILE Sterile Virile Lean
  12. 12. eXtreme Programming (XP) Iteration Plan Iterations plan System!!! ”Stories” Stories User Bruger Whiteboard Whiteboards Developer UdviklereEngineering Practices Kommunikation og samarbejde
  13. 13. XP Practices• The Planning Game • Pair Programming• Small Releases • Collective Ownership• Metaphor • Continuous Integration• Simple Design • Normal work week• Testing • On-site Customer• Refactoring • Coding Standards
  14. 14. ScrumProject Management Practices
  15. 15. Scrum Practices• Self managed teams • Estimates are made by those• 30 days iterations, Sprints who will do the actual work• Daily Scrum meetings • All contact to the project is via• All participates in Planning the Scrum Master• User Stories becomes Tasks • Teams on max 10 people• Customer on site – Product Owner • Everyone is in the same room• Tasks are not assigned but chosen • Use of Sprint and Product• The Scrum Master is not “just” Backlogs and burndown charts project manager • “Pigs and Chickens”
  16. 16. How they compare? Waterfall(One iteration) Iterations Few Documents Many Documents Little Ceremony High Ceremony Ceremoni Scrum Unified Process XP Many short IterationsSource: Craig Larman: Agile & Iterative development, a managers guide
  17. 17. So, What’s next?
  18. 18. Please…..• Agile is not a solution. It’s a tool! – Focus on your problems and how to solve them• There is no such thing as an Agile process! – Agile is a way of thinking and not a product• You HAVE to work Iteratively to become Agile – The only way to get feedback from our Customers• Trust in people – Agile is Trust over Control
  19. 19. Pretty Please……..• Apply your learnings iteratively – It’s the least expensive way• Pick the right tools for the right job• Use proper test approaches to ensure quality. – This helps you discover when new learning’s break old assumptions• Focus on importance and criticality
  20. 20. With sugar on top…….We need:• Smaller teams (5-10 people)• More skilled developers and managers• Close contact to Product owner and Business Experts• Higher level of Abstraction• High degree of Automation• Shorter feedback cycles• Make it cheaper to make mistakes and learn from it
  21. 21. Excerpts from a 3 hour seminar on how to fail with Agile and Iterative Development
  22. 22. Failing with Iterations• Waterfall iterations – “Analysis iteration”, “Design Iteration”….• Remember to minimize technical risks early• A time box has a fixed length – Max 1 month! Longer than that it’s no longer an iteration – Do not extend an iteration. Take things out!• Done is Done! – Done is including TEST! No hidden work• Changes are a part of the process. Not an exception
  23. 23. Failing on a Management level• Unclear goals. What are we trying to achieve?• Method = Product – Buy a license and a consultant, then we are OK• Isolate Agile to one project alone• Going Agile is an iterative a process in itself• Use traditional follow-up and management processes• You will NOT get pay-off from the day one
  24. 24. Failing on a larger scale• Agile affects the whole organization – Users, business, management, test, deployment,..• Understand what you do. Try before dissing – Scrum Buts: “We use Scrum, but……”• Be pragmatic and proactive – Focus on results and not on following the book
  25. 25. What to do?• Communication, communication, … – Make sure to involve people in the process – Listen, Learn and Adapt – Implement iteratively and actively by doing!• Have realistic goals. Short and long term• Accept changes – “Only 10% of what you worry about will ever happen”• Get professional help
  26. 26. How to supercharge AgilityA “radical” shift – to a larger degree of automation 
  27. 27. Lean & AgileAre both treatmenting Symptoms not providing a cure!
  28. 28. We can’t control everythingRather than focus on being Agile which may lead to beingsuccessful, focus on being successful, which may lead you to being Agile
  29. 29. ThanksFor more informationjeppe@tigerteam.dk or @jeppec on Twitter

×