Your SlideShare is downloading. ×
0
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Agile, Tdd And .Net
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile, Tdd And .Net

905

Published on

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

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
905
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
44
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Agile<br />It’s not something you do,<br />it’s something you are.<br />Declan Whelan<br />
  • 2. Waterfall<br />
  • 3. “The CHAOS Chronicles” 2006 The Standish Group<br />
  • 4.
  • 5. Waterfall<br />
  • 6. “… risky and invites failure.”<br />Winston Royce<br />
  • 7. agility<br />values, principles and practices thatfoster team communication and learning to regularly deliver customer value through working software<br />
  • 8. agile values<br />
  • 9. individual and interactions<br />over processes and tools<br />
  • 10. working software over comprehensive documentation<br />
  • 11. customer collaboration over contract negotiation<br />
  • 12. responding to change over following a plan<br />
  • 13. agile principles<br />
  • 14. working software as primary<br /> measure of progress<br />
  • 15. craftsmanship<br />
  • 16. emergent design<br />
  • 17. do the simplest thing that could possibly work<br />
  • 18. feedback<br />
  • 19. agile practices<br />
  • 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.
  • 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. Simple Design Rules<br />Has a test<br />Intent revealing<br />No duplication<br />Minimum number of classes/methods<br />
  • 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 />

×