Ch 16
The chapter talks about how at the end of an extreme programming project, you will end up with a very well designed project that is structured and tested thoroughly. Focus on documentation.
Ch 17
The chapter talks about when tackling a big project, it is always best to break up the problem into smaller manageable parts to solve individually. Estimate the time taken for each sub problem and the time worked on.
Ch 18
The chapter tells programmers to keep track of all their user stories. Graph the number of tests as well as the success rate. Also, track releases and plan out a schedule.
Discussion:
It seems like it is very repetitive. I have already heard all this in the previous chapter. It is just saying it in a slightly different way. We are implementing this process though with our project.
