RE: Managing Extreme Programming

Glen,

> Yes the requirements are the interfaces can and do change, but they
> are not "discovery" requirements in the manner suggested by many XP
> authors - where the user has no a clue as to what she wants and XP
> provides adaptive development process. 

I sense a misunderstanding here of what XP claims to be, or do. I've 
never read anywhere that XP applies where the user doesn't know what 
she want - quite the contrary.

Rather, we assume the user has a thorough understanding of the non-
technology issues that need to be adressed, and the team's job is to 
translate that understanding into a technological medium.

It seems that in many cases, this process of translating involves 
substantial reformulation of the non-technical issues.

Glen, could you post up an example - a disguised or a made-up one if 
for security reasons a real example won't do - of the requirements 
that your are susceptible to get on a project where 90% of the 
requirements are fixed up front ? I mean that at the smallest 
possible level, "user story" or feature request level.

Cheers,

-[Morendil]-
We are like sailors who have to rebuild their ship on the open sea,
without ever being able to dismantle it in dry-dock and reconstruct
it from the best components.
Otto Neurath



------------------------ Yahoo! Groups Sponsor ---------------------~-->
Turn flat surfaces into speakers with the Soundbug.
http://us.click.yahoo.com/QWAVSC/onCFAA/xGHJAA/nhFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/