Reference Information
Title: Extreme Programming Installed
Author: Ron Jeffries, Ann Anderson, Chet Hendrickson
Editor: Addison-Wesley Professional, October 2000
Summary
Chapter 16 outlined things that you should and should not do when practicing the extreme programming approach to programming. This list includes things like don't try to design the whole system before you start implementing it, don't produce voluminous design documents at the beginning, focus on communication, and don't build for tomorrow. In addition, the aspects of a good program are listed: well-designed, flexibly structured, properly documented, tested, and meeting known and documented requirements.
Chapter 17 discussed how with each iteration, experience is gained that can be put towards improving estimates of future stories. The important concepts of task estimation are listed: estimate each task that you sign up for; estimate time you'll spend working; pay attention to the actual time spent working; then evaluate how the estimation time compared with the actual time.
Chapter 18 discussed how to evaluate resources, scope, quality, and time associated with a project. This evaluation lets those people working on a project know where the project currently is, and how well it is doing. Examples of each of the indicators are provided, as well as example graphs of how to plot the actual information associated with each project aspect in order to see how progress is going. For example, to evaluate quality, it is suggested to graph unit test scores vs. time.
 |
| An example graph evaluating quality by the acceptance test scores. Source: Book. |
I find it helpful that most of these chapters were just the authors outlining the main points that readers need to know about Extreme Programming and how to successfully use it. In addition, I think it's very useful that example graphs and suggestions were provided for evaluating project progress, which is very useful to us at this point in time. Since we have been working on our group project for a while now, it is getting to the point where it would be helpful to have more of an indicator of how well we are doing and an estimate of what pace we are currently working at. Some of these graphs seem like they could be useful for us to employ to help with this.
No comments:
Post a Comment