Hi Michael, Additional to the good points already raised by Mathias (which I agree to in really every item), my opinion on this:
The general idea is: Involve people early, not after it's done and integrated. Nobody can oversee *everything* alone, and if you ask other stakeholders, they might have something important to contribute. In this case, Uwe would have told you that various documentation would need to be updated, to keep the product consistent (The fact that the current help is ... sub-optimal doesn't mean we're allowed to make it worse, by out-dating it knowingly.) Other people - from QA - might have expressed interest to get their fingers on the CWS before it's integrated, to add the new feature to their existing tests. Other people could have told you that integrating the CWS on 2006-11-06, one day after the UI freeze, could cause trouble with translation (I don't think it did it this case). Yet other people could have told you that there in fact is an existing specification for the quickstarter, which claims that's a Windows-only feature. Now also this specification is out-of-date (which makes specifications effectively useless, on the long run). As yoou can see, the idea of involving different people with different competences (that's the idea behind an iTeam) *early* is not an end in itself - it's about delivering a self-contained, consistent product to our users, and about preventing trouble in other parts of this huge project. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
