Chapter 4: User Stories
This chapter talks about the importance of user stories. In XP, informal user stories are an essential manner in which the system gets build up. These stories are preferably written in small note cards; and they can be changed over time while adapting to customer needs. In fact, the more the story changes early in the building process, the better it is for programmers since this means that users are writing what they really mean.
Chapter 5: Acceptance Tests
When discussing testing, it is the author's recommendation that tests are run right immediately; along the same period of the related story. If the programmers get their testing acceptance tests sooner, they can make the product work sooner. One of the things that XP values is feedback, therefore it is very important to do the testing as this allows the users to know whether progress is being made and that the functions addressed in the current stories work. The author also stresses the importance of acceptance tests being automated as this allows the smallest amount of errors and facilitates reporting.
Chapter 6: Story Estimation
This chapter talks about estimating the time it takes to complete a story and how to estimate it. The author suggests that story completion times should be calculated by comparing the story to be completed to another story that has been completed and therefore its completion time known. Another technique for time estimation is based on the perfect engineering week. This techniques attempts to find out how much work can be accomplished in a week where the programmers work perfectly all day every day of the week. If there is no initial story that can serve as a reference to a new story, the author suggests implementing a spike solution, which is a made up story that closely resembles the task to be completed (yet it is simple enough that does not overload the programmers).
No comments:
Post a Comment