The Real Purpose of CMMI for Development
Junior Dev: What does CMMI stand for ?
CMMI Fans: CMMI stands for "Capability Maturity Model Integration"
Junior Dev: What does it mean and what is the relationship with software development?
CMMI Fans: It's a model that describes characteristics of effective processes to deliver software that is needed, on time, and on budget.
Senior Dev: Actually, it will bloat the software construction process and totally against agile methodologies. It is only useful for marketing purposes.
CMMI Fans: CMMI is meant to help engineering development organizations improve on their capability to consistently and predictably deliver the products their customers want, when they want them and at a price they're willing to pay.
Senior Dev: Why do I feel the opposite way? I think it's a burden and useless.
CMMI Fans: The Software Engineering Institute was funded by US Department of Defense to identify what the successful projects had in common, and the result is CMM. The SEI defined a "successful project" in terms of a project's ability to meet cost, schedule and quality objectives.
Senior Dev: Ok, it's enough. You have repeat that 3 times.
CMMI Fans: Yeah, that's the real purpose of CMMI. If you feel the other way, than there should be something wrong. CMMI also can be applied with agile methodology by mapping correctly the CMMI specific goals with suitable agile practices, i.e: "Manage Requirement" goal could be mapped with "Product and Sprint backlogs", "Establish Estimates" goal could be mapped with "Sprint Planning".
Senior Dev:Ok, I agree that CMMI is made to be a useful guide for software development. But I still think that it's to bloated and we can be more effective by following some part of CMMI and not the whole of it. Every project is unique and we can not easily repeat previous success project using magic recipes called CMMI.
CMMI Fans:Who said that CMMI is magic recipes? CMMI is collection of best practice found in many successful software projects. We can not say that it's useless. Use it wisely as a guidance to deliver successful projects, not as a bunch of mandatory documents which burden the software construction process. Never thought that CMMI just for marketing tools, it supposed to be used to improve process for developing software.
Senior Dev:I think I need to learn more about CMMI. I want to know more about marrying CMMI with agile methodology. Can you give me some resource about that?
CMMI Fans: Have you ever heard about google?
Source:
http://www.entinex.com/WhatIsCMMI_page1.cfm
http://www.cmmifaq.info/
http://www.agilecmmi.com/2006/08/keys-to-enabling-cmmi.html
CMMI Fans: CMMI stands for "Capability Maturity Model Integration"
Junior Dev: What does it mean and what is the relationship with software development?
CMMI Fans: It's a model that describes characteristics of effective processes to deliver software that is needed, on time, and on budget.
Senior Dev: Actually, it will bloat the software construction process and totally against agile methodologies. It is only useful for marketing purposes.
CMMI Fans: CMMI is meant to help engineering development organizations improve on their capability to consistently and predictably deliver the products their customers want, when they want them and at a price they're willing to pay.
Senior Dev: Why do I feel the opposite way? I think it's a burden and useless.
CMMI Fans: The Software Engineering Institute was funded by US Department of Defense to identify what the successful projects had in common, and the result is CMM. The SEI defined a "successful project" in terms of a project's ability to meet cost, schedule and quality objectives.
Senior Dev: Ok, it's enough. You have repeat that 3 times.
CMMI Fans: Yeah, that's the real purpose of CMMI. If you feel the other way, than there should be something wrong. CMMI also can be applied with agile methodology by mapping correctly the CMMI specific goals with suitable agile practices, i.e: "Manage Requirement" goal could be mapped with "Product and Sprint backlogs", "Establish Estimates" goal could be mapped with "Sprint Planning".
Senior Dev:Ok, I agree that CMMI is made to be a useful guide for software development. But I still think that it's to bloated and we can be more effective by following some part of CMMI and not the whole of it. Every project is unique and we can not easily repeat previous success project using magic recipes called CMMI.
CMMI Fans:Who said that CMMI is magic recipes? CMMI is collection of best practice found in many successful software projects. We can not say that it's useless. Use it wisely as a guidance to deliver successful projects, not as a bunch of mandatory documents which burden the software construction process. Never thought that CMMI just for marketing tools, it supposed to be used to improve process for developing software.
Senior Dev:I think I need to learn more about CMMI. I want to know more about marrying CMMI with agile methodology. Can you give me some resource about that?
CMMI Fans: Have you ever heard about google?
Source:
http://www.entinex.com/WhatIsCMMI_page1.cfm
http://www.cmmifaq.info/
http://www.agilecmmi.com/2006/08/keys-to-enabling-cmmi.html
Thnx linknya....jadi penasaran
Posted by
dwi ardi irawan |
June 09, 2009 8:27 PM