Talk:Extreme programming practices

Risk

I know that the risk analysis here is just an example, and everyone views this differently. But, according to this example, developers develop the relatively complete, unchanging and simple stories before the complete, unchanging and complex stories. Isn't it a better practice to do the complex stuff first? Or is it completely subjective? DRogers 14:38, 8 August 2007 (UTC)[reply]

I was stuck with that at first too. I think what they are getting at, is at a given level of importance to the project, do the simplest first. So You'll do the must have parts of the project first. But you'll create the easy to code must haves first.

Why not do the hard must haves first? Well XP calls for quick releases, so the difficult topics might not be able to be coded while a lot of other stuff is going on. As well, a lot of the risk weighting will be in the category, of "requirements not completely known", and "highly volatile", so time is better spent doing the simple stuff. The requirements, and the volatility very well might disappear after a few interations.

Another reason for it, would be if the project gets dumped you at least have some of the functionality already coded, which presumablity could be used later on (if it is a must have, the functionality will have to go somewhere). MikeG 216.16.232.115 17:29, 1 October 2007 (UTC)[reply]