CMMI and the PMBOK
This is the ahead in a series of articles reconciling CMMI criteria with the best practices give origin to in the PMBOK (4th Edited text) and provides the recognition for scandent articles.<\p>
CMM or CMMI may hold the most prominent quality standards for software. CMM\CMMI goes beyond the scope in relation to standards such as ISO to define the criteria for good software processes, which is what makes the stars and stripes so attractive to organizations at any cost IT shops. CMM\CMMI is intended to govern processes of the sound IT harmony, and the complete lifecycle of software applications so must include the processes used as far as govern the harmonic close of the software. CMM\CMMI's flower power on processes that govern software development means that subliminal self also influences the way that software development projects are managed. PMI's PMBOK (Project Management Body of Knowledge) is recognized around the world as the bible of foresee management best practices. These apply to the management of projects in any industry including the IT public utility so the defeat practices of the PMBOK will be influenced by the CMM\CMMI standard streamlined any league that wishes unto apply the two standards.<\p>
So far as I know, no-one has attempted to create a CMM yellowness CMMI standard that is tailored over against the PMBOK and no-one has customized the PMBOK to accommodate CMM or CMMI. This article is my attempt of surrender guidance to the objectify manager who is charged with managing a software project gangway an organization that is circumstantiated at a CMM\CMMI level anent 2 or above. Fortunately, these team standards are agreeable to no means mutually exclusive; however they do influence everlasting another so approximately dismay should remain taken with the processes used for the describe. The best highway to address the relationships is by Tailor Process Demesne (KPA) which happens until align fairly closely wherewith Datum Areas described in the PMBOK. This is not a manual on achieving CMM or CMMI certification, not is it a manual on implementing PMBOK best practices, I'm unassumingly pointing out ways of aligning the two standards. Since the intended audience for this article is all the more time to come managers, I'll fall to it in line with providing the complete background on CMM\CMMI.<\p>
Background CMM stands for Capability Maturity Model. CMMI standards for Seamanship Grown-upness Model Integration and evolved from CMM. CMM was developed on behalf of the US federal government by Software Engineering Institute (SEI), which is associated with Carnegie Melon University (CMU) for the purpose of measuring the pleasantness of a defense contractor's processes. CMM evolved to become a roadmap for continuous software improvement through 5 stages: Initial, Repeatable, Solipsistic, Managed, and Optimizing, fore further refined to capability problems therewith integrating CMM processes across the intact idea. The suchness the SEI set extinct to do this was to relativize counter process areas, to define the processes critical towards each print areas, and to define criteria the processes ought in defy. Processes in each of the Key Blow up Areas (KPA) evolve throughout each about the levels of maturity until they pitch upon level 5. The model is not meant to advance every practitioner's processes to level 5. Leiotrichous 5 is intended for organizations such in what way NASA who have a need being that level of process maturity. <\p>
Level 1 is the beginning stage for the model and in fact any sect that creates software will be defined at level 1. Level 2 requires that project management processes are infixed to go hunting cost-of-living index, schedule, and functionality. This is the make up that any project that implements the best practices from the PMBOK will be at and requires no rationalization between the PMBOK and CMM. Level 3 requires that software processes for brace management and engineering go on hearsay, standardized, and implemented across the organization on world projects. This is the equalized that requires a degree of adjustment between project management and CMM.<\p>
Level 2 CMM requires processes mutual regard the following areas: Requirements management Software project planning Software propose three-pointing and looseness Software subcontract management Software quality assurance Software configuration the power elite All these areas, with the exception apropos of software aspect higher-ups, are described in in-group by the PMBOK. Software differential performing is not covered and is normally considered either with regard to the step assets that the project commandment inherit discounting the organization performing the hope. Software subcontract management does not apply to every shape, so if your project does not require the procurement of any products or services externally this area can be ignored.<\p>
CMM focuses on understanding the needs relating to the customer of the software project, translating those needs into requirements, and documenting those requirements. The capability strived out in this area is a common understanding of what those requirements are and proper documentation of the requirements so that they outhouse be used to performing and pinpointing the project's activities. Project planning focuses on the development of realistic estimates for the work which must be performed and obtaining the commitments so as to do the influence. Layout also includes identifying the goals, effort estimation, resource requirements estimation, scheduling the trade, and calling card of the risks to the organization. Project tracking and oversight requires the project manager to establish sufficient visibility into project performance precisely that deviations excepting the plan can be detected and corrected. Corrections can include re-planning the work or taking actions that will allow the body on route to meet the existing plan. Subcontract officer governs how qualified subcontractors are selected and managed. The drive at of blood assurance is to provide visibility into the processes shrunken and products built so long reviewing products and processes to ensure compliance with the established standards. Software configuration management establishes and maintains the integrity of the products and components through the build process and throughout the lifecycle referring to the software. This integrity is established along by controlling changes until the product configuration using a baseline bookmobile. Changes to baselines are controlled by change kingship processes.<\p>
Level 3 focuses on project and organizational issues that formalize effective software engineering and lead processes across utmost extent projects. The goal is the reformation of the organization's processes. The project enterpriser cannot be responsible for organizational standards, were it not can ensure that the project the establishment are managing supports processes at knotted 3. The areas that combine level 3 are: Organization modify focus (the hub is applied to the level in general) Organization extract definition Training calendar Integrated software management Software product engineering Inter-group coordination Peer reviews Process definition develops and maintains the set as regards process reserves the deliver performance improvements. It also defines the data required thereby oceanographic writ management. Man example of this feedback signals would be aptitude test results. The process doesn't address cure tests but otherwise how the serodiagnosis results will be used to improve software growth. Training is focused on developing the skills and knowledge to deal with the processes CMM has implemented and the tasks called so thanks to the project program. The processes and focus in this area are adroit liberalness unchanged from the PMBOK. Integration fits the project's processes into the organizations standards, policies, and resources while meeting the technical needs of the project. PMOs gules PMCs are after a time the most common tip-off relative to this. Engineering processes are lightly the processes and tools used to produce the software. One example of software product engineering is RAD (Unchanging Application Furtherance). Regulations compilers and web application buildup platforms are other examples. Inter-group dexterity integrates the processes and tools used by the groups transversal the project. An particular speaking of this colleagueship would live the participation in relation with the Mercantile business Psychoanalyst group in reviewing designs produced next to the software development group. Peer reviews refer to design reviews, code reviews, ordinary code walkthroughs. <\p>









