Software Team Development in the Capability Maturity Model
Eugene G. McGuire
Abstract
Open-access reader
Eugene G. McGuire
Abstract
Open-access reader
As software development organizations become more process-oriented they usually discover that they must address people and team development in an expanded and more systematic manner. The software Capability Maturity Model (CMM®) developed by the Software Engineering Institute specifies in great detail what needs in the system development life cycle; how it is done is greatly dependent on people and teams. This paper discusses team development issues for organizations to consider as they pursue higher maturity levels.
OpenAlex reports 1 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
As software development organizations become more process-oriented they usually discover that they must address people and team development in an expanded and more systematic manner. The software Capability Maturity Model (CMM®) developed by the Software Engineering Institute specifies in great detail what needs in the system development life cycle; how it is done is greatly dependent on people and teams. This paper discusses team development issues for organizations to consider as they pursue higher maturity levels.
Key concepts: Capability Maturity Model, Software development process, Personal software process, LeanCMMI, Software development, Maturity (psychological), Team software process, Systems development life cycle