I heard from a colleague that project classification needs to be done to be compliant to the Project planning processes. Which Project Planning Specific Practice (SP) refers to project classification?
I am not sure what you mean by project classification. Do you mean application domain? Or project size? Or something else entirely?
My best advice to you is not to listen to colleagues who may not be CMMI experts, but instead work with a CMMI consultant or SEI-certified Lead Appraiser. They will provide you with the best information and CMMI interpretations.
The CMMI does not state that you must classify projects for Project Planning (PP). That is why you are having difficulty determining the applicable Specific Practice.
Showing posts with label Specific Practice SP. Show all posts
Showing posts with label Specific Practice SP. Show all posts
Friday, April 10, 2009
Friday, March 27, 2009
Objective Evidence vs. Typical Work Products
Would you please explain the relationship between Objective Evidence and Typical Work Products?
This is an interesting question, and one that can be easily answered by reading the CMMI Glossary, a little used part of the model. Most answers to questions can be found by first reading the Glossary definitions.
From the CMMI Glossary, the definition of Objective Evidence: As used in CMMI appraisal materials, documents or interview results used as indicators of the implementation or institutionalization of model practices. Sources of objective evidence can include instruments (questionnaires), presentations, documents, and interviews.
Typical Work Products are one of the topics contained in the Informative Component. All model components are important because the Informative Component helps you understand the Expected and Required Components. It is best to take these model components as a whole. If you understand all three types of information, then you can understand how everything fits together to form a framework that can benefit your organization.
From the CMMI Glossary, the definition of Typical Work Products: An informative model component that provides sample outputs from a specific practice. These examples are called typical work products because there are often other work products that are just as effective but are not listed.
So, in a nutshell, a Typical Work Product is an example of a tangible output that might be produced by performing a Specific Practice. The Objective Evidence are the actual work products and other items produced by performing the organization’s documented processes. So the Objective Evidence provided in an appraisal might or might not match the items listed as Typical Work Products.
This is an interesting question, and one that can be easily answered by reading the CMMI Glossary, a little used part of the model. Most answers to questions can be found by first reading the Glossary definitions.
From the CMMI Glossary, the definition of Objective Evidence: As used in CMMI appraisal materials, documents or interview results used as indicators of the implementation or institutionalization of model practices. Sources of objective evidence can include instruments (questionnaires), presentations, documents, and interviews.
Typical Work Products are one of the topics contained in the Informative Component. All model components are important because the Informative Component helps you understand the Expected and Required Components. It is best to take these model components as a whole. If you understand all three types of information, then you can understand how everything fits together to form a framework that can benefit your organization.
From the CMMI Glossary, the definition of Typical Work Products: An informative model component that provides sample outputs from a specific practice. These examples are called typical work products because there are often other work products that are just as effective but are not listed.
So, in a nutshell, a Typical Work Product is an example of a tangible output that might be produced by performing a Specific Practice. The Objective Evidence are the actual work products and other items produced by performing the organization’s documented processes. So the Objective Evidence provided in an appraisal might or might not match the items listed as Typical Work Products.
Wednesday, April 9, 2008
CMMI for Acquisition Process Areas
There are 6 CMMI for Acquisition (CMMI-ACQ) Process Areas (PAs) unique to this new constellation: Agreement Management (AM), Acquisition Requirements Development (ARD), Acquisition Technical Management (ATM), Acquisition Validation (AVAL), Acquisition Verification (AVER), and Solicitation and Supplier Agreement Development (SSAD). AM, ARD, and SSAD are Maturity Level 2 PAs and ATM, AVAL, and AVER are Maturity Level 3 PAs.
In addition to these six new PAs, there are other changes at the Specific Practice level in Project Planning (PP), Project Monitoring and Control (PMC), Integrated Project Management (IPM), and Organizational Process Definition (OPD).
PP SP 1.1 - Establish and maintain the acquisition strategy
PP SP 2.7 - Plan transition to operations and support (the addition of this SP makes the old SP 2.7 now SP 2.8)
PMC SP 1.8 - Monitor transition to operations and support
OPD SP 1.7 - Establsh and maintain organizational rules and guidelines for the structure, formation, and operation of integrated teams
IPM SP 1.6 - Establish and maintain integrated teams
The difficult concept to understand if your background is in the CMMI for Development (CMMI-DEV)is that every core PA is interpreted in the context of the acquirer's processes.
When looking at the Continuous Representation for CMMI-ACQ the category Acqusition replaces the category Engineering from the CMMI-DEV constellation. And the other change is that Requirements Management (REQM) is now included in the Project Management category.
And on a final note, it is possible to perform a blended appraisal CMMI-DEV and CMMI-ACQ.
Subscribe to:
Posts (Atom)