Extreme Programming Installed Ch 22-24

Reference Information:

Title: Extreme Programming Installed

Author: Ron Jeffries, Ann Anderson, Chet Hendrickson

Editor: Addison-Wesley Professional, October 2000

Summary:

Chapter 22 - Handling Defects

In this chapter, the author talk about how the bugs in the code should be handled. Following approach should be followed:

• Have an easy way for the users to report the bugs - email, bug reporting tools etc.
• Once the users submit bug reports, they should scheduled for bug fix depending on the urgency and severity of the bug.
• Write a test case to recreate the bug, fix the bug and write a test case to verify that the bug has been fixed.
• Examine the root cause of the bug and try to prevent more bugs by addressing the problem.

Chapter 23 - Conclusion

This chapter summarizes the book and briefly goes over all the important aspects of eXtreme Programming, which are -

• Simplicity
• Communication
• Feedback
• Courage

Finally, the chapter praises the XP methodology and talks about how useful and productive it has been in the programming world.

Chapter 24 - We'll try

This chapter talks about meeting deadlines and the importance of accurately estimating the tasks. Authors suggest setting realistic goals and deadlines. The programmers should convey these realistic estimates to the managers.

Discussion:

I've enjoyed reading this book. Extreme programming is quite different from other methodologies that I've studied in the past, like the waterfall or the agile methodology. Chapter 22 was interesting since it emphasizes on handling the bugs when the product is already out in the market. Chapter 23 and 24 basically stressed on previously mentioned ideas. Overall, I think this book provides an articulate, yet detailed description of Extreme Programming Methodology.