tag:blogger.com,1999:blog-5135517.post108748856758452937..comments2023-11-05T03:54:44.710-08:00Comments on Making it stick.: Misinterpreting the CMMPatrick Loganhttp://www.blogger.com/profile/02088461489050417591noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5135517.post-1093492290848074262004-08-25T20:51:00.000-07:002004-08-25T20:51:00.000-07:00I don't think Andy is really misrepresenting CMM, ...I don't think Andy is really misrepresenting CMM, he is just reacting to a common misperception of CMM. Business people want SW Dev. to be an assembly line, and looking at CMM misleads some into thinking this is possible. People often see what they want to see, after all.<br /><br />C.J.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5135517.post-1089780904378635522004-07-13T21:55:00.000-07:002004-07-13T21:55:00.000-07:00Yes, I believe Hunt does misinterpret it. In a way...Yes, I believe Hunt does misinterpret it. In a way, even with making movies all movies do follow a process, in that they have the script written first, followed by review and storyboarding and so on... it's a repeatable and time tested process. <br /><br />What CMMi and RUP is asking of us, is to have the same with s/w development. <br /><br />But at times, the template model does help cross the first hurdle of setting thing up easily. After that, as you mentioned, it's an iterative process of honing everything to individual project requirements. <br /><br />Here's a link that gives a perspective to the template approach: <br /><br />http://www.digite.com/download/cmmi.htmNavneethttps://www.blogger.com/profile/07308567122976306703noreply@blogger.com