09 February 2007

REQM y PP en CMMi DEV v1.2 (2)

Requirements Management (REQM)

Esta AP, perteneciente al Nivel de Madurez 2, se ocupa de administrar los requerimientos de los productos del proyecto y de los componentes del proyecto. Permite identificar las inconsistencias entre estos requerimientos y los productos de trabajo y planes del proyecto. Describe las actividades que obtienen y controlan los cambios de los requerimientos; y suministra trazabilidad respecto de los requerimientos del cliente y del componente producto-producto. Esta AP asegura que los cambios de los requerimientos son reflejados en los planes del proyecto, actividades y productos de trabajo. Este ciclo de cambios puede afectar todas las AP de Ingeniería. Esta AP es fundamental para el proceso de diseño de Ingeniería.

REQM se relaciona con las siguientes AP: RD (Requirements Development), TS (Technical Solution), PP (Project Planning), CM (Configuration Management), PMC (Project Monitoring and Control) y RSKM (Risk Management).

Los objetivos específicos (SG), prácticas especificas (SP) y subprácticas de esta AP son:

SG 1 - Manage Requirements

SP 1.1 Obtain an Understanding of Requirements

1.1.1- Establish criteria for distinguishing appropriate requirements providers. 1.1.2- Establish objective criteria for the evaluation and acceptance of requirements. 1.1.3- Analyze requirements to ensure that the established criteria are met. 1.1.4- Reach an understanding of the requirements with the requirements provider so that the project participants can commit to them.

SP 1.2 Obtain Commitment to Requirements

1.2.1- Assess the impact of requirements on existing commitments. 1.2.2- Negotiate and record commitments.

SP 1.3 Manage Requirements Changes

1.3.1- Document all requirements and requirements changes that are given to or generated by the project. 1.3.2- Maintain the requirements change history with the rationale for the changes. 1.3.3- Evaluate the impact of requirement changes from the standpoint of relevant stakeholders. 1.3.4- Make the requirements and change data available to the project.

SP 1.4 Maintain Bidirectional Traceability of Requirements

1.4.1- Maintain requirements traceability to ensure that the source of lower level (derived) requirements is documented. 1.4.2- Maintain requirements traceability from a requirement to its derived requirements and allocation to functions, interfaces, objects, people, processes, and work products. 1.4.3- Generate the requirements traceability matrix.

SP 1.5 Identify Inconsistencies between Project Work and Requirements

1.5.1- Review the project’s plans, activities, and work products for consistency with the requirements and the changes made to them. 1.5.2- Identify the source of the inconsistency and the rationale. 1.5.3- Identify changes that need to be made to the plans and work products resulting from changes to the requirements baseline. 1.5.4- Initiate corrective actions.

Los productos de trabajo de las SP son: (1) Lists of criteria for distinguishing appropriate requirements providers (SP 1.1), (2) Criteria for evaluation and acceptance of requirements (SP 1.1), (3) Results of analyses against criteria (SP 1.1), (4) An agreed-to set of requirements (SP 1.1), (5) Requirements impact assessments (SP 1.2), (6) Documented commitments to requirements and requirements changes (SP 1.2), (7) Requirements status (SP 1.3), (8) Requirements database (SP 1.3), (9) Requirements decision database (SP 1.3), (10) Requirements traceability matrix (SP 1.4), (11) Requirements tracking system (SP 1.4), (12) Documentation of inconsistencies including sources, conditions and rationale (SP 1.5) y (13) Corrective actions (SP 1.5)

Project Planning (PP)

Esta AP, perteneciente al Nivel de Madurez 2, incluye establecer y mantener los planes que se definen en las actividades del proyecto. La planificación comienza con los requerimientos que definen el producto y el proyecto. La planificación del proyecto abarca varios proyectos y actividades de desarrollo efectuadas en el proyecto. En el proyecto se revisan otras planificaciones que puedan afectar el proyecto y se establecen confirmaciones respecto del mismo. PP se relaciona con las siguientes AP: RD (Requirements Development), REQM (Requirements Management), RSKM (Risk Management) y TS (Technical Solution).

Los objetivos específicos (SG), prácticas especificas (SP) y subprácticas de esta AP son:

SG 1 - Establish Estimates

SP 1.1 Estimate the Scope of the Project 1.1.1- Develop a WBS based on the product architecture. 1.1.2- Identify the work packages in sufficient detail to specify estimates of project tasks, responsibilities, and schedule 1.1.3- Identify product or product components that will be externally acquired. 1.1.4- Identify work products that will be reused.

SP 1.2 Establish Estimates of Work Product and Task Attributes

1.2.1- Determine the technical approach for the project. 1.2.2- Use appropriate methods to determine the attributes of the work products and tasks that will be used to estimate the resource requirements 1.2.3- Estimate the attributes of the work products and tasks.

SP 1.3 Define Project Life Cycle

SP 1.4 Determine Estimates of Effort and Cost

1.4.1- Collect the models or historical data that will be used to transform the attributes of the work products and tasks into estimates of the labor hours and cost. 1.4.2- Include supporting infrastructure needs when estimating effort and cost. 1.4.3- Estimate effort and cost using models and/or historical data.

Los productos de trabajo de las SP son: (1) Task descriptions (SP 1.1), (2) Work package descriptions (SP 1.1), (3) WBS (Work Breakdown Structure) (SP 1.1), (3) Technical approach (SP 1.2), (4) Size and complexity of tasks and work products (SP 1.2), (5) Estimating models (SP 1.2), (6) Attribute estimates (SP 1.2), (7) Project lifecycle phases (SP 1.3), (8) Estimation rationale (SP 1.4), (9) Project effort estimates (SP 1.4) y (10) Project cost estimates (SP 1.4)

SG 2 - Develop a Project Plan

SP 2.1 Establish the Budget and Schedule

2.1.1- Identify major milestones. 2.1.2- Identify schedule assumptions. 2.1.3- Identify constraints 2.1.4- Identify task dependencies. 2.1.5- Define the budget and schedule. 2.1.6- Establish corrective action criteria.

SP 2.2 Identify Project Risks

2.2.1- Identify risks. 2.2.2- Document the risks. 2.2.3- Review and obtain agreement with relevant stakeholders on the completeness and correctness of the documented risks. 2.2.4- Revise the risks as appropriate.

SP 2.3 Plan for Data Management

2.3.1-Establish requirements and procedures to ensure privacy and security of the data. 2.3.2- Establish a mechanism to archive data and to access archived data. 2.3.3- Determine the project data to be identified, collected, and distributed.

SP 2.4 Plan for Project Resources

2.4.1- Determine process requirements. 2.4.2- Determine staffing requirements. 2.4.3- Determine facilities, equipment, and component requirements.

SP 2.5 Plan for Needed Knowledge and Skills

2.5.1- Identify the knowledge and skills needed to perform the project. 2.5.2- Assess the knowledge and skills available. 2.5.3- Select mechanisms for providing needed knowledge and skills. 2.5.4- Incorporate selected mechanisms into the project plan.

SP 2.6 Plan Stakeholder Involvement

SP 2.7 Establish the Project Plan

Los productos de trabajo de las SP son: (1) Project schedules (SP 2.1), (2) Schedules dependencies (SP 2.1), (3) Project budget (SP 2.1), (4) Identified risks (SP 2.2), (5) Risk impacts and probability of occurrence (SP 2.2), (6) Risk priorities (SP 2.2), (7) Data management plan (SP 2.3), (8) Master list of managed data (SP 2.3), (9) Data content and format description (SP 2.3), (10) Data requirements lists for acquirers and for suppliers (SP 2.3), (11) Privacy requirements (SP 2.3), (12) Security requirements (SP 2.3), (13) Security procedures (SP 2.3), (14) Mechanism for data retrieval, reproduction, and distribution (SP 2.3), (15) Schedule for collection of project data (SP 2.3), (16) Listing of project data to be collected (SP 2.3), (17) WBS work packages (SP 2.4), (18) WBS task dictionary (SP 2.4), (19) taffing requirements based on project size and scope (SP 2.4), (20) Critical facilities / equipment list (SP 2.4), (21) Process / workflow definitions and diagrams (SP 2.4), (22) Program administration requirements list (SP 2.4), (23) Inventory of skill needs (SP 2.5), (24) Staffing and new hire plans (SP 2.5), (25) Databases (SP 2.5), (26) Stakeholder involvement plan (SP 2.6) y (27) Overall project plan (SP 2.7)

SG 3 - Obtain Commitment to the Plan

SP 3.1 Review Plans that Affect the Project

SP 3.2 Reconcile Work and Resource Levels

SP 3.3 Obtain Plan Commitment

3.3.1- Identify needed support and negotiate commitments with relevant stakeholders. 3.3.2- Document all organizational commitments, both full and provisional, ensuring appropriate level of signatories. 3.3.3- Review internal commitments with senior management as appropriate. 3.3.4- Review external commitments with senior management as appropriate. 3.3.5- Identify commitments on interfaces between elements in the project, and with other projects and organizational units so that they can be monitored.

Los productos de trabajo de las SP son: (1) Record of the reviews of plans that affect the project (SP 3.1), (2) Revised methods and corresponding estimating parameters (SP 3.2), (3) Renegotiated budgets (SP 3.2), (4) Revised schedules (SP 3.2), (5) Revised requirements list (SP 3.2), (6) Renegotiated stakeholder agreements (SP 3.2), (7) Documented requests for commitments (SP 3.3) y (8) Documented commitments (SP 3.3)

Prácticas Genéricas por Objetivo de REQM y PP

Solo Representación Continua

GG 1 - Achieve Specific Goals

The process supports and enables achievement of the specific goals of the process area by transforming identifiable input work products to produce identifiable output work products.

GP 1.1 - Perform Specific Practices

Perform the specific practices of the project planning process to develop work products and provide services to achieve the specific goals of the process area.

Representación Continua y por Etapas

GG 2 - Institutionalize a Managed Process

The process is institutionalized as a managed process.

GP 2.1 - Establish an Organizational Policy

Establish and maintain an organizational policy for planning and performing the project planning process.

GP 2.2 - Plan the Process

Establish and maintain the plan for performing the project planning process.

GP 2.3 - Provide Resources

Provide adequate resources for performing the project planning process, developing the work products, and providing the services of the process.

GP 2.4 - Assign Responsibility

Assign responsibility and authority for performing the process, developing the work products, and providing the services of the project planning process.

GP 2.5 - Train People

Train the people performing or supporting the project planning process as needed.

GP 2.6 - Manage Configurations

Place designated work products of the project planning process under appropriate levels of control.

GP 2.7 - Identify and Involve Relevant Stakeholders

Identify and involve the relevant stakeholders of the project planning process as planned.

GP 2.8 - Monitor and Control the Process

Monitor and control the project planning process against the plan for performing the process and take appropriate corrective action.

GP 2.9 - Objectively Evaluate Adherence

Objectively evaluate adherence of the project planning process against its process description, standards, and procedures, and address noncompliance.

GP 2.10 - Review Status with Higher Level Management

Review the activities, status, and results of the project planning process with higher level management and resolve issues.

Solo Representación por Etapas

GG3 and its practices do not apply for a maturity level 2 rating, but do apply for a maturity level 3 rating and above.

Representación Continua – Solo Niveles de Madurez 3 -5

GG 3 Institutionalize a Defined Process

The process is institutionalized as a defined process.

GP 3.1- Establish a Defined Process

Establish and maintain the description of a defined project planning process

GP 3.2 - Collect Improvement Information

Collect work products, measures, measurement results, and improvement information derived from planning and performing the project planning process to support the future use and improvement of the organization’s processes and process assets

Solo Representación Continua

GG 4 - Institutionalize a Quantitatively Managed Process

The process is institutionalized as a quantitatively managed process

GP 4.1 - Establish Quantitative Objectives for the Process

Establish and maintain quantitative objectives for the project planning process, which address quality and process performance, based on customer needs and business objectives.

GP 4.2- Stabilize Subprocess Performance

Stabilize the performance of one or more subprocesses to determine the ability of the project planning process to achieve the established quantitative quality and process-performance objectives.

Solo Representación Continua

GG 5 - Institutionalize an Optimizing Process

The process is institutionalized as an optimizing process.

GP 5.1 - Ensure Continuous Process Improvement

Ensure continuous improvement of the project planning process in fulfilling the relevant business objectives of the organization.

GP 5.2 - Correct Root Causes of Problems

Identify and correct the root causes of defects and other problems in the project planning process.