Monday, March 21, 2011

Extreme Programming Installed Ch 22-24


Summary

Chapter 22 – Handling Defects – the chapter talks about “bugs” in the code and how to handle them. The first thing is making sure the users have an easy way of submitting problems, whether it is through email or through a problem reporting tool. After getting these errors we should write them on cards and schedule them according to how urgent they are. When we are ready to work on the bug we should write a test that shows the problem, and then fix it. Finally, try to prevent more problems by understanding how and why the existing problems appeared.

Chapter 23 – Conclusion – This chapter wraps up the book (minus the Bonus Tracks). We should now know that the values of XP are simplicity, communication, feedback, and courage. Basically, the chapter indicates how simple XP is and how useful it has been for the authors.

Chapter 24 – We’ll try – this chapter goes over the importance of estimating tasks from the beginning once again. We should be able to estimate how long any project will take without a problem, as long as we write the user stories and estimate each of them by separate; then we can just add them!


Discussion

The first chapter was interesting as it describes how to handle bugs after a system has already been shipped. However, the chapters are getting repetitive and is easy to anticipate what and how the chapter will word something. Even more, the chapter after the conclusion (bonus) was just a repetition of another chapter of the book.  

No comments:

Post a Comment