Conclusions


We think our first story now runs; certainly all our tests run and the acceptance tests run. We are open to the possibility that the next story will show a defect thats already here, but thats why we do lots of small releases: so that we, and our customer (hat), can learn. We just hope our customer hat is smarter than we are.

In a final retrospective chapterChapter 31, Project Retrospective well take a look back at all the books chapters and well draw some overall lessons and conclusions. And youll notice that we look back frequently, on a smaller scale, just like we did this time. For now, were ready to ship our first story. The code is pretty cleanwere honestly happy with itand the tests all run. Maybe were being too kind to ourselves in not cleaning up some of the things we looked at, but we looked at all of them and consciously decided. If they bite us later, well remember and adjust our behavior based on what we learn. We figure thats the best a person can do.




Extreme Programming Adventures in C#
Javaв„ў EE 5 Tutorial, The (3rd Edition)
ISBN: 735619492
EAN: 2147483647
Year: 2006
Pages: 291

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net