Sent w/o the signature this time
Common sense, simplicity and clarity rule or at least they should. Identify the problem or need, define the solution and keep it practical, simple, reliable, intuitive, scaleable and cheap! Buy or build is another topic. Part of working the solution is looking at frameworks (ITIL CMMI, COBIT, Six Sigma, etc), taking what the need calls for and discarding the rest, never loosing sight of the fact that what you do take must be tweaked to your organizations needs. ITIL clearly states that you may not need all of the processes. Processes included in the frameworks most definitely have value. The monster you want to control is complexity. Frameworks are nothing more than a summary of RECOMMENDATIONS by those who have been down that road before and are useful in that it saves one from having to completely reinvent the wheel. Personally, I'm happy to consider any advice that may reduce my time to market and enhance my probability of success. The best process is one that is used, don't discourage your stakeholders. What processes do you need and how granular do they need to be? Pete _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
smime.p7s
Description: S/MIME cryptographic signature
