Brilliant. That sort of decision runs by whole teams, I would imagine. Why doesn't anyone speak up? I would imagine that folks on the apple side saw that, also.
I see your point, but without a "spokesperson" customer you'll be designing the software by committee. Maybe one customer is too xtreme--but allowing many more customers (cooks) to talk to the developers will add more confusion.
Also, the way I understand xp is that you gather the requirements, then the developers estimate the time it takes to complete each task. During this process developers break each chunk of functionality into small chunks and estimate times on those. This shows the customer the complexity of any given piece of the app and helps them determine the priorities or where they can scale back.
I really like the idea of having a single customer on hand to work with the programmers--although I wouldn't sit them any where near them, just make sure they are always available during the developement cycle.
It's also important that the single customer is informed of the requirements of their peers and is empowered to make the business decisions to decide priorities.
Now have I actually done any of this in practice? Not explicitly, but am trying to find a version of this that works in practice.
Slashdot Mirror
Brilliant. That sort of decision runs by whole teams, I would imagine. Why doesn't anyone speak up? I would imagine that folks on the apple side saw that, also.
Also, the way I understand xp is that you gather the requirements, then the developers estimate the time it takes to complete each task. During this process developers break each chunk of functionality into small chunks and estimate times on those. This shows the customer the complexity of any given piece of the app and helps them determine the priorities or where they can scale back.
I really like the idea of having a single customer on hand to work with the programmers--although I wouldn't sit them any where near them, just make sure they are always available during the developement cycle.
It's also important that the single customer is informed of the requirements of their peers and is empowered to make the business decisions to decide priorities.
Now have I actually done any of this in practice? Not explicitly, but am trying to find a version of this that works in practice.