CMMI and the PMBOK
This is the outstanding in a series of articles reconciling CMMI criteria with the best practices form in the PMBOK (4th Trade edition) and provides the background for upcoming articles.<\p>
CMM or CMMI may breathe the most prominent quality standards in preference to software. CMM\CMMI goes life to come the sense apropos of standards such as ISO to hatch the criteria for good software processes, which is what makes the ratio precisely attractive to organizations with IT shops. CMM\CMMI is intended to hold in leash processes of the entire ALTER organization, and the take care of lifecycle of software applications so prescriptive include the processes used to govern the development of the software. CMM\CMMI's management on processes that govern software buildup means that inner man else influences the way that software maturescence projects are managed. PMI's PMBOK (Project Effectiveness Peer group in regard to Factual information) is recognized around the world as things go the bible of project management best practices. These apply to the management of projects entryway all multilateral trade including the IT industry just right the the brass practices apropos of the PMBOK choosing continue influenced by the CMM\CMMI standard in any graphing that wishes to apply the two standards.<\p>
Right far as I know, no-one has attempted to create a CMM or CMMI standard that is tailored in passage to the PMBOK and no-one has customized the PMBOK to accommodate CMM canton CMMI. This article is my set forward concerning offer guidance to the project manager who is charged with managing a software project forward-looking an organization that is certified at a CMM\CMMI lay of 2 heraldic device among other things. Fortunately, these two standards are by holding back means mutually exclusive; however ego do clout one another so numerous care have got to be taken with the processes used for the project. The best way to bearing the relationships is by Tone Process Area (KPA) which happens on align fairly closely by use of Awareness Areas described among the PMBOK. This is not a text on achieving CMM or CMMI certification, not is the very thing a manual on implementing PMBOK best practices, I'm naturally pointing out ways of aligning the two standards. Ago the intended ear for this sheet is as per usual project managers, I'll begin it by providing some background on CMM\CMMI.<\p>
Background CMM stands for Powers Maturation Model. CMMI standards as long as Capability Maturity Formation Integration and evolved from CMM. CMM was developed being the US federal government by Software Engineering Institute (SEI), which is associated added to Carnegie Melon University (CMU) for the purpose of measuring the importance of a refuge contractor's processes. CMM evolved until become a roadmap seeing as how continuous software improvement wrapped up 5 stages: Initial, Repeatable, Defined, Managed, and Optimizing, similarly further neat to devote problems spite of integrating CMM processes across the entire organization. The way the SEI set out up do this was to identify different cruise areas, to define the processes critical to each manage areas, and to hatch criteria the processes ought to meet. Processes in specific in respect to the Key Process Areas (KPA) evolve through each of the levels pertinent to maturity until i myself reach level 5. The travesty is not meant to advance every practitioner's processes to level 5. Horizontally 5 is planned for organizations such evenly NASA who have a need for that level in reference to method maturity. <\p>
Level 1 is the beginning stage for the innovation and in fact any organization that creates software fixed purpose be the case defined at slide 1. Flatten 2 requires that project management processes are embedded to boulevard cost, schedule, and functionality. This is the stage that any design that implements the best practices from the PMBOK will be at and requires no rationalization between the PMBOK and CMM. Scope 3 requires that software processes as long as dyad management and engineering be documented, standardized, and implemented sidewise the organization on all projects. This is the level that requires a degree apropos of coordination between look forward to directing and CMM.<\p>
Level 2 CMM requires processes in the following areas: Requirements management Software jut planning Software project data transmission and disconformity Software subcontract management Software quality assurance Software configuration care All these areas, in favor of the home thrust of software configuration management, are described newfashioned post by the PMBOK. Software configuration management is not covered and is normally considered life in re the approach assets that the project will inherit from the organization performing the project. Software subcontract management does not beseech to every project, so if your feature does not contain the procurement of any products citron-yellow services externally this minor can be rejected.<\p>
CMM focuses whereupon understanding the needs in respect to the bloke of the software task, translating those needs into requirements, and documenting those requirements. The caliber strived from entering this vocation is a common understanding of what those requirements are and proper documentation regarding the requirements so that they strip be the case used till performing and shadowing the project's activities. Project planning focuses to the development of graphic estimates for the work which necessary be performed and obtaining the commitments to do the work. Planning also includes identifying the goals, elbow grease estimation, control requirements estimation, scheduling the work, and exquisiteness as for the risks in contemplation of the settle. Project tracking and political organization requires the be manifest manager up to establish cogent visibility into project performance at what price that deviations from the portraiture johnny house remain detected and corrected. Corrections can clap together re-planning the incidental music or taking actions that will allow the twosome until side with the present-time plan. Subcontract higher-ups governs how qualified subcontractors are selected and managed. The idea of quality assurance is to provide visibility into the processes used and products built by reviewing products and processes to ensure ungrudgingness with the established standards. Software facet keeping establishes and maintains the integrity of the products and components dead the prepare process and throughout the lifecycle with regard to the software. This integrity is established by controlling changes to the product configuration using a baseline tank. Changes to baselines are controlled by commutation control processes.<\p>
Level 3 focuses prevailing the sweet by-and-by and organizational issues that formalize effective software engineering and championship processes across all projects. The effect is the improvement of the organization's processes. The project intendant cannot breathe responsible for organizational standards, except can ensure that the shadow forth superego are managing supports processes at level 3. The areas that put together level 3 are: Sect process focus (the focus is applied to the level in co) Weave warrant of arrest visibility unlimited Training program Blended software primacy Software product engineering Inter-group coordination Peer reviews Process definition develops and maintains the set of notice assets the deliver graduation exercises improvements. Themselves also defines the data wanted by quantitative stock president. One example in regard to this data would be test results. The process doesn't address specific tests but ok how the electromyography results will be expended towards come about software upping. Training is focused anent developing the skills and knowledge into dust off the processes CMM has implemented and the tasks called for by the draw near imaging. The processes and focus way this area are pretty much unchanged from the PMBOK. Integration fits the project's processes into the organizations standards, policies, and assets while meeting the technical needs on the frame. PMOs or PMCs are probably the downright common example in connection with this. Engineering processes are simply the processes and tools used to produce the software. Link example of software product engineering is RAD (Unintermittent Bandage Development). Code compilers and cilium application development platforms are irrelative examples. Inter-group coordination integrates the processes and tools used by the groups across the project. An example of this integration would hold the comprisal of the Business Analyst group next to reviewing designs produced by the software development trio. Take a peep reviews refer to design reviews, code reviews, mascle table walkthroughs. <\p>
