Search

Agile, TDD and .NET

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    Add “story” definition.Add “alignment” as a principle?Add release and sprint burn-down charts

    This is of successful projects

    This is the “perceived wisdom” – the way that we have been taught.Developed by Royce – “Managing the Development of Large Scale Systems” Proceeding, IEEE Wescon, August 1970 This model has been misinterpreted – Royce meant to show that this was actually a “bad idea”! “the implementation described above is risky and invites failure … one can expect up to a 100-percent overrun in schedule and/or costs” However in practice we have the prevalent notions of: Get it right the first time. If only we did a better job of defining requirements then …The agile community argues that: The cost of change curve is as much a result of the process rather than intrinsic to software development

    Team communicationsFocus on communication and collaboration rather than process and toolsFeedbackLots of internal feedback loops: daily, weekly, quarterly Get customer feedback oftenRegularly DeliverRelease S/W typically quarterly with internal releases weekly or bi-weeklyValueFocus on highest value featuresWorking SoftwareFocus on getting S/W working early and keeping it releasable rather than big-bang waterfall approach It is not binary … it is a mindset

    Use of collaborative spaces

    ThanksMain Points- Agile is a mindset Values, principles and practices that foster team communication and feedback to regularly deliver customer value through working softwareAgile has crossed the chasm – it is widely deployed across many companies small to large and across many domains – including enterprise software- Agile is like losing weight – easy to understand; hard to do

    ThanksMain Points- Agile is a mindset Values, principles and practices that foster team communication and feedback to regularly deliver customer value through working softwareAgile has crossed the chasm – it is widely deployed across many companies small to large and across many domains – including enterprise software- Agile is like losing weight – easy to understand; hard to do

    Agility movement has succeeded by embedding proven practices into a cohesive package supported by a mindset focused on core values and principles.

    1 Group

    Agile, TDD and .NET - Presentation 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
    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
    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

    + guest18f66d7guest18f66d7, 5 months ago

    custom

    267 views, 0 favs, 0 embeds more stats

    Brief overview of Agile and TDD.

    More info about this document

    CC Attribution License

    Go to text version

    • Total Views 267
      • 267 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 14
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories

    Groups / Events

    -->
    Search
    RSS Feed
    What's new?

    © 2009 SlideShare Inc. All Rights Reserved