Summary:
The first chapter dealt with user stories. These stories are a conversations had by the programmers and the customers to see what specifications a system needs. The stories are given in 2 week programmer time and written down on cards. Stories should mainly come from the customer. Chapter 5 deals with testing. It is very important in XP to check test often in order to avoid waiting time later by testing in the end and forgetting the code. This way, bugs are caught much faster. Testing each story is a good way to test the overall program. Another way is to manually compute and check against the software. Chapter 6 discusses the importance of assigning points to each story to come up with solutions to the most important ones first. By doing so, we can choose which stories to do and give an approximation of time. Comparing is a good way to estimate and calling from previous stories implemented. It is good to start early on with intuitive time testing. This helps steer the project. It is best to experiment when dealing with stories never seen before. One will not get the perfect solution the first time around. Keeping records of all this is extremely important. It is the programmers who set the pace of the project.
Discussion:
All these tips seem very crucial and extremely helpful. It can really cut down on time of programming as well as debugging. I will be implementing these methods when it comes to my design project to keep on task and avoid falling behind.
No comments:
Post a Comment