RE: Managing Extreme Programming
"Dinwiddie, George" <[email protected]>
| Newsgroups | gmane.comp.programming.extreme-programming.adoption |
|---|---|
| Message-ID | <[email protected]> |
Dan Rawsthorne said: > Of course, having a BCWS means that you know what work you have scheduled. > It requires a scope. So, you have fixed budget and a fixed scope up front > in order to have a BCWS and do this kind of calculation. Right away we know > that this won't apply to XP, as XP assumes scope and cost are independent > variables, and the existence of a BCWS makes them dependent on each other... You can have an assumed scope and assumed budget as a starting point. You can validate this later, but when you start a project, I think you're always pulling numbers out of the air. > > In order to measure progress, you have to break the work up into smaller > > pieces and distribute the value over these pieces. Let's say for easy > > visualization that you do this down to the level of the User Stories. > > This works if we have all the estimation points done up front, and we have > a stable velocity.... I didn't say this was a good way of distributing the value to the story level. It's just an easy one to imagine. Coming up with a good way is a much harder job. First, I want to validate my understanding of the picture, then proceed with identifying and developing strategies for the rough spots. - George ------------------------ 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/