Summary:
The chapter describes three roles (customer, programmer, and manager) and the rights and responsibilities of each. The customer gives stories that should be used to determine what types of features should be implemented for the project to be successful. Programmers need to coordinate efficiently and make sure to constantly test code so that each small release works. A manager needs to remove all obstacles from the programmers so that the ship runs smoothly.
Discussion:
I like the way this book includes customers as part of the team. Although they are not actually coding anything, the fact is everything is being done for them. While most of the topics in this chapter have been covered in other classes, its nice to have it all in one convenient place.
Chapter 2:
Summary:
This chapter introduces the circle of life for programmers and customers. The customer tells the programmer what they want and the programmer tells the customer how much time and resources that will take.
The chapter also covers the importance of not overworking programmers so that releases are predictably timed and made with high quality.
Discussion: I enjoyed the inclusion of not stressing out and overworking. I myself have been overzealous when attempting homework and it usually ends with less favorable results than if I had simply given myself more time for a less stressful work schedule.
Chapter 3:
Summary:
This chapter discusses the importance of on-site customers. Having on-site customers greatly increases communication and lowers the amount of misunderstandings. If it isn't possible to have on-site customers, release code to the customers as often as possible to minimize misunderstandings.
Discussion:
It seems that the overall theme of the first few chapters of this book is that the customer is just as (if not more) important as any programmer or manager on the team. The book does a good job of reminding us to always realize that we are working for the customer.
No comments:
Post a Comment