That's a broken management culture -- no "process" is going to work well in that context until the culture of blame and CYA is fixed...
On Tue, Oct 21, 2008 at 9:09 AM, Vince O'Sullivan <[EMAIL PROTECTED]>wrote: > > On Oct 21, 9:24 am, kibitzer <[EMAIL PROTECTED]> wrote: > > RUP can be agile because you can pick and choose which > > bits you need based on what you're doing. > > The catch is that you have to justify and document your decisions. > Therefore, you end up with documents that refer to stuff that you're > not using and why you're not using it. In the (albeit unlikely) event > that someone reads said documents, you'll then be accused of a) being > negative and b) cutting corners. Much safer and simpler - from a > management point of view - to use every tool on every project and > document how wonderful it was. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
