Monday, April 11, 2011

Extreme Programming Installed chapters 22 - 24

Summary:
Ch 22
We want to avoid bugs and defects when programming. We slow down the project and fail tests when these arise. It is very important to keep track of these to reference back and avoiding them in the future for better programming. This will speed up the project as a whole.

Ch 23
XP is meant to be simple with a great emphasis on communication and feedback. The progression of the project depends on these. Goals should also be kept realistic to the point where you can have deliverables weekly.

Ch 24
It is important to properly  deliver a project and estimate its completeness. Having these documented estimates can lead you to push back deadlines and release dates put on by managers. You do not want to release code that is not properly finished.



Discussion:
I am glad to be done with this book! I think I have implemented enough XP into our senior design project and I learned better like that than reading the book

No comments:

Post a Comment