Hi Bernard, > In a CMM context, the customer does not have the > choice of applying or not the CMM recquired > process. The "CMM documentation" stories are not > submitted to their appreciation. You can consider > that their value is so high, that they are mandatory.
Well, you seem to be shifting the goal posts. And we don't appear to be using the words "stories" or "value" in quite the same way... From your initial post, I thought you were in a consultant role, recommending that for an XP team to become XYZ compliant, one should just add process documentation stories. Personally, I would not recommend that at all. I would ask Why? five times, and attempt to demonstrate how XP already covers the requirement, albeit in a different way. If not I would seek an XP-ish, automatic way. Secondly, if there is no choice about doing the process documentation, as now appears to be the case, I would definitely not consider it to be stories. In XP, stories provide value to the Customer, and it is the Customer's right to prioritize them. If you are not giving the Customer any choice, it ain't stories. Regards, Dominic Williams http://www.dominicwilliams.net ---- To Post a message, send it to: [EMAIL PROTECTED] To Unsubscribe, send a blank message to: [EMAIL PROTECTED] ad-free courtesy of objectmentor.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/extremeprogramming/ <*> 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/
