Agile, Tdd And .Net

1,167 views
1,085 views

Published on

Quick overview of agile craftsmanship. This was a prelude to a Coding Dojo with .NET and C#.

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

No Downloads
Views
Total views
1,167
On SlideShare
0
From Embeds
0
Number of Embeds
65
Actions
Shares
0
Downloads
46
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Agile, Tdd And .Net

  1. 1. Agile<br />It’s not something you do,<br />it’s something you are.<br />Declan Whelan<br />
  2. 2. Waterfall<br />
  3. 3. “The CHAOS Chronicles” 2006 The Standish Group<br />
  4. 4.
  5. 5. Waterfall<br />
  6. 6. “… risky and invites failure.”<br />Winston Royce<br />
  7. 7. agility<br />values, principles and practices thatfoster team communication and learning to regularly deliver customer value through working software<br />
  8. 8. agile values<br />
  9. 9. individual and interactions<br />over processes and tools<br />
  10. 10. working software over comprehensive documentation<br />
  11. 11. customer collaboration over contract negotiation<br />
  12. 12. responding to change over following a plan<br />
  13. 13. agile principles<br />
  14. 14. working software as primary<br /> measure of progress<br />
  15. 15. craftsmanship<br />
  16. 16. emergent design<br />
  17. 17. do the simplest thing that could possibly work<br />
  18. 18. feedback<br />
  19. 19. agile practices<br />
  20. 20. Agile Practices – They Aren’t New!<br />Data Hiding<br />Simple Design<br />Software Architecture<br />Cont. Integration<br />Software Reuse<br />Documentation<br />Risk Management<br />Collective Ownership<br />Project Planning<br />Incremental Releases<br />Test-Driven Design<br />Coding Standards<br />Evolutionary Design<br />Refactoring<br />Pair Programming 50s<br />On-Site Customer<br />Patterns<br />Metaphor<br />Requirements forever<br />Software Metrics<br />Sustainable Pace<br />Retrospectives<br />2000<br />1960<br />1990<br />1980<br />1970<br />Source: Software Best-Practices: Agile Deconstructed - Steven Fraser OOPSLA 2007<br />
  21. 21.
  22. 22. RedGreen Refactor<br />Write the test code<br />Compile the test code (it should fail)<br />Implement just enough to compile<br />Run the test and see it fail<br />Implement just enough to make it pass<br />Run the test and see it pass<br />Refactor for clarity and to remove duplication<br />Repeat from step 1<br />
  23. 23. Simple Design Rules<br />Has a test<br />Intent revealing<br />No duplication<br />Minimum number of classes/methods<br />
  24. 24. TDD Resources<br />“Test-Driven Development”Kent Beck<br />“xUnit Test Patterns”Gerard MeszarosRick Mugride, Ward Cunningham<br />“Pragmatic Unit Testing in C# with NUnit”Andrew Hunt, David Thomas<br />http://www.testdriven.com<br />http://www.nunit.org/ - NUnit<br />

×