This IS Agile Development

393 views

Published on

As presented at Chicago Code Camp 2013.

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

No Downloads
Views
Total views
393
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Working Software ASAP, Cross-Functional Teams, Emergence
  • Note this is NOT the same as SPEED
  • Note that the definition here aligns with the dictionary definition of Agile, and is NOT about SPEED
  • We 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 toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a planThat is, while there is value in the items on the right, we value the items on the left more.
  • Point out that the vertical lines on the right-hand (slices) diagram are never straightFor example, Sprint 2 may require the team to go back and refactor code/decisions made in Sprint 1Also, it takes a cross-functional team to do this effectivelyDoes it take smart people to do emergent architecture? No, it takes smart people to develop software
  • We 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 toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a planThat is, while there is value in the items on the right, we value the items on the left more.
  • You know, like what ‘Team’ is supposed to mean.
  • We 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 toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a planThat is, while there is value in the items on the right, we value the items on the left more.
  • Where ACTIVITY formerly meant SEQUENTIAL STEP
  • Emergent Design/Architecture: Following conventions of the original application, which does have some basic layering and use of good, known patterns (MVC, Repositories), negotiating for a “harvest, don’t grow” approach with CC ServiceTesting Pyramid – what’s interesting about the testing pyramid is that it’s not just about testing – yes, it shows that automation has a lot more ROI as you move towards the base, but it also talks about the amount or focus of tests, in a way that CANNOT be achieved without good application design
  • This IS Agile Development

    1. 1. ••••••
    2. 2. ••••••
    3. 3. ••••••
    4. 4. ••••
    5. 5. ••••
    6. 6. ə əhttp://www.merriam-webster.com/dictionary/agile
    7. 7. http://en.wikipedia.org/wiki/Agile_software_development
    8. 8. ••••••••
    9. 9. ••••
    10. 10. © 1993 - 2013 Scrum.org, All Rights Reserved
    11. 11. ••
    12. 12. ••
    13. 13. •••••
    14. 14. •••••••
    15. 15. •••
    16. 16. ••••
    17. 17. http://www.managedmayhem.com/2009/05/06/agile-software-development-process/
    18. 18. •••RequirementsDesignCodeTest© 1993 - 2013 Scrum.org, All Rights Reserved
    19. 19. ••••
    20. 20. ••••••
    21. 21. •••••
    22. 22.
    23. 23. Managing the Development of Large Software Systems – Dr. Winston W.Royce
    24. 24. Managing the Development of Large Software Systems – Dr. Winston W.Royce
    25. 25. Managing the Development of Large Software Systems – Dr. Winston W.Royce
    26. 26. http://www.managedmayhem.com/2009/05/06/agile-software-development-process/
    27. 27. •••
    28. 28. ••••
    29. 29. ••••
    30. 30. Complete Cross-FunctionalityAll GeneralistsPure TeamworkCondescending Jerks
    31. 31. ••
    32. 32. ••
    33. 33. •••••

    ×