After reading through the article, I had some thoughts:
1. Planning game: Customers decide the scope and timing of releases
=> It is difficult even for PM to perform planning for scope and time. Besides, customers are ambitious so they may try to get the most out of the programmer by setting unrealistic scope and time.
2. On-site customer: A customer sits with the team full-time
=> A assigned customer to the team is currently a staff within a company. This staff must clearly know everything about the requirements so they must be a key staff in the company. It is hard to get them full-time in the project and remove them completely from what they are currently doing.
Bibliography:
Beck, Kent. "Embracing change with extreme programming." Computer 32.10 (1999): 70-77.
The clue I think is in the name, "planning game", indeed what customers attempt to do to suppliers is itself a kind of game.
ReplyDeleteThe clue I think is in the name, "planning game", indeed what customers attempt to do to suppliers is itself a kind of game.
ReplyDelete