Summary
Chapter 16 – This chapter is a summary of recommendations to achieve the XP goal of delivering well designed, well crafted, flexible structured, properly documented, and tested computer programs. Here are a few of the many recommendations: don’t try to design the whole system before you start implementing it, don’t try to freeze requirements before you start implementing, don’t produce documents or other artifacts that aren’t being used, don’t separate the team into designers and coders, and don’t build for tomorrow.
Chapter 17 – This chapter is about stories time estimation. A few things to remember are the following: estimate each task that you sign up for, estimate the amount of actual time you will spend working, and pay attention to the actual time you spend working. After a few times of doing this, you will be able to accurately estimate the amount of time tasks will take you.
Chapter 18 – This chapter discusses tracking and reporting approaches. There are 4 major things that need to be tracked and reported: resources, scope, quality, and time. Keep track of key resources, number of developers, testers, etc. Also, keep a close eye on the number of stories over time, how many exist, how many are done, and how many more are expected. Use a standard acceptance-testing graph showing number of tests and number succeeding over time. Finally, track the results of each release plan so you are aware of your time constrains. The chapter goes into more detail of each of these tracking mechanisms. Discussion
As always, the chapters are short, sweet, and easy to understand. Chapters 16 and 17 were mostly about recapping what has already been said before. Chapter 18 was interesting; however, I feel the book is starting to repeat itself too much. I understand they just want to reiterate in order for the info to really stick with us, but I am getting a little tired of it.
No comments:
Post a Comment