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

895

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

×