{"id":8017807,"date":"2015-08-07T11:39:54","date_gmt":"2015-08-07T18:39:54","guid":{"rendered":"https:\/\/test-agilealliance.pantheonsite.io\/?post_type=aa_research_paper&p=8017807"},"modified":"2023-08-29T07:49:14","modified_gmt":"2023-08-29T14:49:14","slug":"lean-cmmi-an-iterative-and-incremental-approach-to-cmmi-based-process-improvement","status":"publish","type":"aa_research_paper","link":"https:\/\/agilealliance.org\/resources\/research-papers\/lean-cmmi-an-iterative-and-incremental-approach-to-cmmi-based-process-improvement\/","title":{"rendered":"Lean CMMI: An Iterative and Incremental Approach to CMMI-Based Process Improvement"},"content":{"rendered":"

Software Process Improvement (SPI) projects incorporate organization transition risks which may cause many process improvement initiatives to fail. To mitigate these risks, an iterative and incremental approach called \u2018Process Increments\u2019 is used to manage the SPI project.<\/p>\n

In this paper, the Configuration Management process area is used as a case study to show the improvement results difference when the \u2018Process Increments\u2019 approach is used. Results are compared with similar projects which didn\u2019t use an incremental approach. This approach shifts the focus from adopting new techniques to achieving value-add for the organization and shows excellent results in effective and efficient implementation of Software Configuration Management.<\/p>\n

Through our proposed process increment model, we could reach a significant increase in the performance of the software process improvement.<\/p>\n\n\n

\n
\n

Amr Noaman Abdel-Hamid<\/strong>
Agile Academy
Cairo, Egypt
amr@agileacademy.co<\/p>\n<\/div>\n\n\n\n

\n

Alaa El-deen Hamouda
<\/strong>Systems and Computers Engineering
Al-Azhar University
Cairo, Egypt
alaa.hamouda@azhar.edu.eg<\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Software Process Improvement (SPI) projects incorporate organization transition risks which may cause many process improvement initiatives to fail. To mitigate these risks, an iterative and incremental approach called \u2018Process Increments\u2019 […]<\/p>\n","protected":false},"author":6000331,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","categories":[],"tags":[],"content_source":[186],"class_list":["post-8017807","aa_research_paper","type-aa_research_paper","status-publish","hentry","content_source-agile2015"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_research_paper\/8017807","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_research_paper"}],"about":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/types\/aa_research_paper"}],"author":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/users\/6000331"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=8017807"}],"version-history":[{"count":0,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_research_paper\/8017807\/revisions"}],"wp:attachment":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media?parent=8017807"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=8017807"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=8017807"},{"taxonomy":"content_source","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/content_source?post=8017807"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}