RE: Re: Customers who can't take small releases

JB

> >If you are saying that there is no such person, then you are saying that
> >changes in the requirements are not possible. In that case, don't bother
> >with XP or Agile. Come back when you have a project where changes in the
> >requirements are permitted.
> 
> My apologies. This may sound rude. I probably meant, "Let's stick 
> to projects where changes in the requirements are permitted, for 
> the purposes of conversation on this mailing list."

Maybe we're getting hung up on the "requirements" which can have a fairly
strict and legalistic meaning in some situations. I suspect that there's
some way in Glen's project that /change/ occurs, even though it may not
be recognized by the strict interpretation of the "requirements" that
have been contracted.

Glen, can you address the degree to which you are able to make changes
in the specifics of what's being done on a project - whether they are
considered requirements changes or not?

Charlie Poole
[email protected]
www.pooleconsulting.com
www.charliepoole.org




------------------------ Yahoo! Groups Sponsor ---------------------~-->
Flexible Keyboard is the ideal accessory for PDA users that are on the move.
http://us.click.yahoo.com/dCBVZC/WnCFAA/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/