Agile Myths


Published on

Presented on Agile Latvia Evening in August 2010

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • That is one of the goals of Agile Latvia to break the culture and spread the word
  • knowledge inside a team may be distributed in informal ways, but for remote collaborations tooling is required
  • By F.Brooks any new technology/methodology makes you less productive, but only after some time you start gaining the advantages
  • Agile Myths

    1. 1. Agile Myths ... from the "real world" Agile Latvia Evening 26.08.2010 Dmitry Buzdin
    2. 2. What are Agile Myths? <ul><li>An excuse not to use Agile or some of the Agile Practices because of the &quot;real world&quot; conditions </li></ul>
    3. 3. Myths, where do they come from? <ul><ul><li>old habits </li></ul></ul><ul><ul><li>previous experience </li></ul></ul><ul><ul><li>lack of knowledge </li></ul></ul><ul><ul><li>no hands on experience </li></ul></ul><ul><ul><li>fear of change/responsibility/transparency... </li></ul></ul>
    4. 4. Spot the Reality Competition <ul><li>If Myth is real --> raise your hand </li></ul>
    5. 5. Disclaimer <ul><li>All infomation in given presentation is based on speaker's personal experience and reality he lives in... </li></ul>
    6. 6. Developer Myths
    7. 7. Myths about Test Driven Development <ul><ul><li>TDD makes me slow </li></ul></ul><ul><ul><li>Real code is too complex to test </li></ul></ul><ul><ul><li>Unit Testing is a separate product </li></ul></ul><ul><ul><li>Just a waste of time </li></ul></ul>
    8. 8. Reality: Test Driven Development <ul><ul><li>yes, it takes more time now because ... </li></ul></ul><ul><ul><li>... you do not know how to do that </li></ul></ul><ul><ul><li>... it will save time later </li></ul></ul><ul><ul><li>... it makes you think </li></ul></ul>
    9. 9. Myths about Pair Programming <ul><ul><li>Takes twice as much time </li></ul></ul><ul><ul><li>Not so good idea </li></ul></ul><ul><ul><li>Not efficient </li></ul></ul>
    10. 10. Reality: Pair Programming <ul><ul><li>It will not save time now </li></ul></ul><ul><ul><li>Knowledge sharing </li></ul></ul><ul><ul><li>Constant reviews </li></ul></ul><ul><ul><li>Not necessary for the whole day </li></ul></ul><ul><ul><li>Impossible if developers are against </li></ul></ul>
    11. 11. Myths about Agile in Big Teams <ul><ul><li>Not for Big Teams </li></ul></ul><ul><ul><li>Not for Distributed Teams </li></ul></ul><ul><ul><li>Our daily meetings take too much time </li></ul></ul><ul><ul><li>Total Chaos </li></ul></ul>
    12. 12. Reality: Agile in Big Teams <ul><ul><li>Split teams to smaller ones, by functionality/location/other </li></ul></ul><ul><ul><li>Distributed collaboration can be automated </li></ul></ul><ul><ul><li>Strict daily meeting format </li></ul></ul>
    13. 13. Myths about Agile Developers <ul><ul><li>Only highly skilled and talented could do agile </li></ul></ul><ul><ul><li>You can not just become agile </li></ul></ul><ul><ul><li>That is why agile is not working... </li></ul></ul>
    14. 14. Reality about Agile Developers <ul><ul><li>Simply follow the rules </li></ul></ul><ul><ul><li>Responsibility is the key </li></ul></ul><ul><ul><li>Skilled developers are welcome </li></ul></ul><ul><ul><li>Newcomers are involved from day one </li></ul></ul>
    15. 15. Recap of Developer Myths <ul><ul><li>Spend more time today to save time tomorrow </li></ul></ul><ul><ul><li>Every team can do Agile </li></ul></ul>
    16. 16. Manager Myths
    17. 17. Myths about Having No Process <ul><ul><li>Agile throws away processes </li></ul></ul><ul><ul><li>Agile replaces &quot;bureaucracy&quot; </li></ul></ul><ul><ul><li>Our CMMI Level 4 is incompatible with Agile </li></ul></ul>
    18. 18. Reality: Having No Process <ul><ul><li>Agile is more disciplined than &quot;ad-hoc&quot; development </li></ul></ul><ul><ul><li>Reliance on practices </li></ul></ul><ul><ul><li>Continuous feedback </li></ul></ul><ul><ul><li>Measurable progress </li></ul></ul><ul><ul><li>Continuous improvement </li></ul></ul>
    19. 19. Myths about No Documentation <ul><ul><li>Documentation should be discarded </li></ul></ul><ul><ul><li>&quot;I am agile, I do not need documentation&quot;... </li></ul></ul>
    20. 20. Reality about No Documentation <ul><ul><li>Documentation is not forbidden </li></ul></ul><ul><ul><li>Documentation should be generated </li></ul></ul><ul><ul><li>No documents for sake of the documents </li></ul></ul>
    21. 21. Myths about Agile and Customers <ul><ul><li>Agile is impossible in Fixed-Price contracts </li></ul></ul><ul><ul><li>Our customer should be on-site </li></ul></ul><ul><ul><li>Our customer should be agile </li></ul></ul>
    22. 22. Reality: about Agile and Customers <ul><ul><li>Possible with any type of contracts </li></ul></ul><ul><ul><li>Agile is for you, not for the customer </li></ul></ul><ul><ul><li>Backlog is the key </li></ul></ul><ul><ul><li>Pick customer from your team </li></ul></ul>
    23. 23. Recap on Manager Myths <ul><ul><li>Having as little process and documentation as possible </li></ul></ul><ul><ul><li>But no less than that! </li></ul></ul><ul><ul><li>Customer should not necessary be Agile </li></ul></ul><ul><ul><li>Agile is about efficiency and responsibility </li></ul></ul>
    24. 24. General Myths
    25. 25. Myth: We are Already Agile! <ul><ul><li>We are already Agile enough </li></ul></ul>
    26. 26. Reality for being Agile <ul><li>Agile is a strive for excellence, not a stop </li></ul>
    27. 27. Myth about Agile Solving any Problem <ul><ul><li>Agile will rescue our project </li></ul></ul><ul><ul><li>Agile will make me happy </li></ul></ul><ul><ul><li>Agile will cut the development costs </li></ul></ul><ul><ul><li>Agile does the job for you by automation </li></ul></ul>
    28. 28. Reality: Agile Solves Any Problem <ul><ul><li>Not a silver bullet </li></ul></ul><ul><ul><li>Takes time and commitment to master </li></ul></ul><ul><ul><li>Will not be effective during first X weeks/iterations/months/releases/years </li></ul></ul><ul><ul><li>Sorry for that... </li></ul></ul>
    29. 29. The Grand Myth: My Project is Unique <ul><li>Agile is great, but my project is very special, because of design/code/customer/technology/team/... </li></ul>
    30. 30. The Reality <ul><li>NO , it was implemented hundreds of times!!! </li></ul><ul><li>  </li></ul><ul><li>... there is nothing special about your clustered real-time embeddable enterprise project </li></ul>
    31. 31. Conslusions <ul><ul><li>If project is not special, Agile just might work </li></ul></ul><ul><ul><li>  </li></ul></ul><ul><ul><li>Most of the myths have some ground </li></ul></ul><ul><ul><li>It is all about people </li></ul></ul><ul><ul><li>Adopt practices one by one </li></ul></ul><ul><ul><li>Do not go blindly into agile </li></ul></ul><ul><ul><li>Think... </li></ul></ul>
    32. 32. Anything Else to Add? <ul><li>Questions? </li></ul><ul><li>What other Myths have you encountered? </li></ul><ul><ul><li>a - ... </li></ul></ul><ul><ul><li>b - ... </li></ul></ul><ul><ul><li>c - ... </li></ul></ul><ul><ul><li>d - ... </li></ul></ul><ul><ul><li>e - ... </li></ul></ul><ul><ul><li>f - ... </li></ul></ul>
    33. 33. Who am I? <ul><li>Dmitry Buzdin </li></ul><ul><li>  </li></ul><ul><li>Software developer/architect practicing Agile since 2005. Currently working in C.T.Co. </li></ul><ul><li>Reach me by [email_address] </li></ul>