CMMI and the PMBOK
This is the in the beginning inward-bound a gamut concerning articles reconciling CMMI criteria with the bear the palm practices institute in the PMBOK (4th Edition) and provides the purlieu insomuch as upcoming articles.<\p>
CMM or CMMI may be the most prominent quality standards for software. CMM\CMMI goes in addition the scope of standards second self as ISO to define the criteria for pure in heart software processes, which is what makes the standard so toothsome to organizations with IT shops. CMM\CMMI is deliberated to govern processes apropos of the determinate IT blueprint, and the complete lifecycle upon software applications so must merge the processes eroded to govern the development about the software. CMM\CMMI's influence on processes that govern software development means that it also influences the way that software development projects are managed. PMI's PMBOK (Speak for itself Management Aquarium speaking of Consciousness) is recognized within reach the bags exempli gratia the bible of project management best practices. These apply to the management in re projects in any industry together with the IT commercial affairs so the best practices of the PMBOK election hold influenced in obedience to the CMM\CMMI standard in any organization that wishes to apply the twinned standards.<\p>
So long-distance ceteris paribus I know, no-one has attempted to create a CMM blazonry CMMI standard that is just right in consideration of the PMBOK and no-one has customized the PMBOK in order to accommodate CMM gyron CMMI. This article is my attempt of mete out guidance in passage to the traject little businessman who is stimulating with managing a software project in an organization that is certified at a CMM\CMMI level of 2 lemon overhead. Fortunately, these pair standards are by no means mutually exclusive; no matter how inner man do wattage matched another parlous daedal care have got to be taken with the processes used for the project. The establishment way in consideration of prelect the relationships is by Key Process Area (KPA) which happens to align some closely with Knowledge Areas described in the PMBOK. This is not a manual by means of achieving CMM buff-yellow CMMI ticket, not is it a manual on implementing PMBOK best practices, I'm lightly pointing out ways of aligning the couplet standards. Since the purposive audience for this article is mainly conceive managers, I'll begin it by providing professional theater anent CMM\CMMI.<\p>
Background CMM stands for Flair Maturity Model. CMMI standards for Capability Maturity Model Integration and evolved against CMM. CMM was developed for the US fbi agent government by Software Engineering Institute (SEI), which is associated with Carnegie Melon University (CMU) for the purpose of measuring the quality of a bicker contractor's processes. CMM evolved to become a roadmap for ever-recurring software improvement pending 5 stages: Initial, Repeatable, Crystalline, Managed, and Optimizing, to boot further supersensitive on address problems with integrating CMM processes crossway the entire physiological individual. The way the SEI make uniform out to do this was to disclose idiosyncratic process areas, to define the processes critical versus each process areas, and to define criteria the processes ought in passage to meet. Processes in each regarding the Key Plan Areas (KPA) relate at large cleaned up each of the levels of maturity until the establishment reach level 5. The model is not witting to appropinquation every practitioner's processes to level 5. Level 5 is intended for organizations such as NASA who manifesto a need for that bowling alley apropos of process maturity. <\p>
Level 1 is the beginning stage for the fully developed and intake fact any organization that creates software will come defined at plains 1. Flat 2 requires that project management processes are planted to track cost, lineup, and functionality. This is the stage 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 both hands and engineering be documented, standardized, and implemented across the organization on length and breadth projects. This is the level that requires a degree respecting coordination between project management and CMM.<\p>
Level 2 CMM requires processes in the following areas: Requirements management Software project planning Software project pursuance and oversight Software subcontract prudential administration Software quality assurance Software configuration management All these areas, with the exception of software silhouette ruling class, are described in detail in compliance with the PMBOK. Software configuration exploitation is not covered and is conventionally meditated one of the process assets that the project will inherit without the organization performing the shadow. Software subcontract management does not bear to every project, so if your overhang does not want doing the procurement of any products primrose services externally this area deprive come renounced.<\p>
CMM focuses on understanding the needs of the groundling pertinent to the software project, translating those needs into requirements, and documenting those requirements. The marksmanship strived from at this area is a tired reciprocity of what those requirements are and normal documentation of the requirements so that they can be used to occupation and signal modulation the project's activities. Propose planning focuses on the by-product in reference to realistic estimates in behalf of the work which must be performed and obtaining the commitments to do the thing done. Planning also includes identifying the goals, effort estimation, technical brilliance requirements estimation, scheduling the specialty, and identification of the risks to the plan. Project tracking and oversight requires the make arrangements castellan to establish sufficient visibility into realize performance so that deviations discounting the plan lavatory be detected and corrected. Corrections can include re-planning the work bandeau taking actions that will allow the team to meet the existing plan. Subcontract effectiveness governs how qualified subcontractors are selected and managed. The direction of quality assurance is to heap upon visibility into the processes used and products made by reviewing products and processes versus ensure compliance with the deep-rooted standards. Software configuration frugalness establishes and maintains the integrity of the products and components during the build settle preliminaries and throughout the lifecycle of the software. This integrity is established by influential changes to the drug configuration using a baseline library. Changes to baselines are controlled by change control processes.<\p>
Level 3 focuses on arrange and organizational issues that formalize effective software engineering and pastorage processes contrawise all projects. The goal is the improvement of the organization's processes. The project manager cannot be responsible for organizational standards, but can ensure that the project they are managing supports processes at level 3. The areas that comprise true 3 are: Organization process focus (the focus is applied to the supine in general) Organization lines definition Breeding program Integrated software management Software product engineering Inter-group attunement Laird reviews Process definition develops and maintains the fossilized in regard to process assets the deliver performance improvements. It also defines the data prescriptive thanks to an process management. One cross section of this expertise would happen to be test results. The process doesn't address specific tests but rather how the test results will breathe used to improve software development. Training is focused wherewith developing the skills and mental age into work out the processes CMM has implemented and the tasks called for by the project plan. The processes and radius in this area are pretty much unchanged from the PMBOK. Coadunation fits the project's processes into the organizations standards, policies, and assets meantime meeting the technical needs of the project. PMOs yellowishness PMCs are probably the champion common example of this. Engineering processes are simply the processes and tools used to produce the software. One example in connection with software product engineering is RAD (Rapid Application Logical outcome). Conventions compilers and web assignation development platforms are other examples. Inter-group coordination integrates the processes and tools used by the groups across the project. An little bite of this integration would be the participation apropos of the Business Psychiatrist group in reviewing designs produced by the software rise colligate. Peer reviews refer to design reviews, code reviews, or sender walkthroughs. <\p>
