| burningpaper 2006-07-17, 7:55 am |
| Hi
I wonder if people could share their experience about a part of XP I'm not so clear on.
We have a customer for whom we're building a fairly large system (6-8 month project) and using XP. A lot of things about work great, but my question is this: when the customer phones/emails and asks for a change or adds scope in some way, what is the correct way to handle this?
It's easy enough to note down that the change was requested, but do we turn it into a new user story? Do we estimate the effort and add that to the total project scope, or ask him to drop other features to accommodate it?
The basic problem is that a lot of these "additions" are clarifications as well, so it's a bit more slippery than it would be if he were adding major new features.
It's early in the project and I really want to give it the best chance of success. Any ideas would be welcome! |