RE: Managing Extreme Programming

> These are "real" requirements I'm working on today...

Yup, that's what I understood. What I sent were my "real" reactions 
to them. :)

> [>] Goals? Close the T&L system everyday and get the numbers into the EV
> system for use on my desk at the beginning of business the next day. Do
> this everyday until I say stop ;>)

Those are *your* goals. They're important too.

> [>] Yea that's interesting. Our typical approach is to build some kind
> of "junk yard dog" UI get it going (so we can get paid) and move one...

Well, that's rather close to the "spartan user interface" notion.

What I'm getting at is that I don't see, in this admittedly small and 
admittedly unfamiliar sample of user stories, any indication that the 
dialogue between the project's "desire" and "possibilities" side 
can't be as fruitful as on any project suitable for XP - that is, 
"discover" more value than would be the case if you went for BDUF. 
They don't sound like there's any strong external constraint ensuring 
that 90% of the requirements will be "frozen" on day 1. But I may 
just be missing something.

Cheers,

-[Morendil]-
My reality check just bounced.



------------------------ 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/