Chapter 13 talks about debugging and how to produce programs that work. It highlights different ways to go about debugging the system as a whole and its individual parts. The next chapter talks about how to deal with schedule slippage and that if the team is able to get ahead then they will have some cushion in case of an emergency. The final chapter of this excerpt focuses on how to write good documentation with the author "showing" the reader how to write good documentation.
The second chapter of the excerpt, chapter 14, was really weird to me because it seemed to contradict the rest of the book. For the entire book the authors had argued for the reader to make tight schedules that have no cushion but in this chapter, they argue that the team should work really hard to form a cushion. So the question is what do they want, a looser schedule with cushion or a tight schedule with a team that is dying trying to get ahead.
No comments:
Post a Comment