04 April 2010

REQM y SAM en CMMi SVC V1.2 (4)

REQUIREMENTS MANAGEMENT

EL propósito de ‘Requirements Management’ (REQM), perteneciente al Nivel de Madurez 2, es administrar los requerimientos de los productos y de los componentes del producto del proyecto. Permite identificar las inconsistencias entre estos requerimientos y los productos de trabajo y planes del proyecto.

Los procesos de manejo de requerimientos administran todos los requerimientos recibidos o generados en el proyecto, incluyendo los requerimientos técnicos y no técnicos. Todos los requerimientos que el cliente y proveedor del servicio han aprobado son tratados en esta área de proceso. Esta área de proceso es implementada y genera requerimientos del cliente y del contrato que serán administrados por los procesos de manejo de requerimientos.

Parte de la administración de requerimientos consiste en documentar los cambios de los requerimientos y mantener la relación bidireccional de trazabilidad entre los requerimientos originales y todos los requerimientos de los componentes del producto y del producto.

Todos los proyectos tienen requerimientos. En el caso de las actividades de mantenimiento, los cambios del producto o de los componentes del producto están basados en los cambios de los actuales requerimientos, en el diseño o en la implementación. Los cambios de los requerimientos pueden ser documentados en las solicitudes de cambio del cliente o pueden tomar la forma de nuevos requerimientos recibidos del proceso de desarrollo de requerimientos.

REQM se relaciona con las siguientes áreas de proceso: SSD, SSM, CM, PMC, PP y RSKM.

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

SG 1 - Manage Requirements

SP 1.1 – Understand 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 established criteria are met. 1.1.4- Reach an understanding of requirements with requirements provider so that 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 a requirements change history including the rationale for changes. 1.3.3- Evaluate the impact of requirement changes from the standpoint of relevant stakeholders. 1.3.4- Make 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 a requirements traceability matrix.

SP 1.5 - Identify Inconsistencies between Project Work and Requirements

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

Productos de trabajo típicos

Lists of criteria for distinguishing appropriate requirements providers (SP 1.1) Criteria for evaluation and acceptance of requirements (SP 1.1) Results of analyses against criteria (SP 1.1) A set of approved requirements (SP 1.1) Requirements impact assessments (SP 1.2) Documented commitments to requirements and requirements changes (SP 1.2) Requirements status (SP 1.3) Requirements database (SP 1.3) Requirements decision database (SP 1.3) Requirements traceability matrix (SP 1.4) Requirements tracking system (SP 1.4) Documentation of inconsistencies between requirements and project plans and work products, including sources and conditions (SP 1.5) Corrective actions (SP 1.5)

SUPPLIER AGREEMENT MANAGEMENT

El propósito de ‘Supplier Agreement Management’ (SAM), perteneciente al Nivel de Madurez 2, consiste en administrar la adquisición de productos y servicios por parte de proveedores.

Esta área de proceso trata la adquisición de productos, servicios, y componentes de servicios y productos que pueden ser entregados al cliente del proyecto o incluidos en el sistema de servicio. Estas prácticas de las áreas de proceso pueden ser usadas para otros propósitos que benefician al proyecto.

SAM involucra las siguientes actividades: (1) Determinar el tipo de adquisición, (2) Seleccionar los proveedores, (3) Establecer y mantener acuerdos con los proveedores, (4) Ejecutar los acuerdos con los proveedores, (5) Monitorear los procesos de los proveedores seleccionados, (6) Evaluar los productos de trabajo de los proveedores seleccionados, (7) Aceptar la entrega de los productos adquiridos y (8) Asegurar una transición exitosa de los productos adquiridos en el proyecto.

CAM se relaciona con las siguientes áreas de proceso: SSD, PMC y REQM. Los objetivos específicos (SG), prácticas específicas (SP) y subprácticas de esta área de proceso son:

SG 1 – Establish Supplier Agreement

SP 1.1 – Determine Acquisition Type

SP 1.2 – Select Suppliers

1.2.1- Establish and document criteria for evaluating potential suppliers. 1.2.2- Identify potential suppliers and distribute solicitation material and requirements to them. 1.2.3- Evaluate proposals according to evaluation criteria. 1.2.4- Evaluate risks associated with each proposed supplier. 1.2.5- Evaluate proposed suppliers’ ability to perform the work. 1.2.6- Select the supplier.

SP 1.3 – Establish Supplier Agreements

1.3.1- Revise the requirements (e.g., product requirements, service level requirements) to be fulfilled by the supplier to reflect negotiations with the supplier when necessary. 1.3.2- Document what the project will provide to the supplier. 1.3.3- Document the supplier agreement. 1.3.4- Periodically review the supplier agreement to ensure it accurately reflects the project’s relationship with the supplier and current risks and market conditions. 1.3.5- Ensure that all parties to the supplier agreement understand and agree to all requirements before implementing the agreement or any changes. 1.3.6- Revise the supplier agreement as necessary to reflect changes to the supplier’s processes or work products. 1.3.7- Revise the project’s plans and commitments, including changes to the project’s processes or work products, as necessary to reflect the supplier agreement.

Productos de trabajo típicos

List of the acquisition types that will be used for all products and product components to be acquired (SP 1.1) Market studies (SP 1.2) List of candidate suppliers (SP 1.2) Preferred supplier list (SP 1.2) Trade study or other record of evaluation criteria, advantages and disadvantages of candidate suppliers, and rationale for selection of suppliers (SP 1.2) Solicitation materials and requirements (SP 1.2) Statements of work (SP 1.3) Contracts (SP 1.3) Memoranda of agreement (SP 1.3) Licensing agreement (SP 1.3)

SG 2 – Satisfy Supplier Agreements

SP 2.1 – Execute the Supplier Agreement

2.1.1- Monitor supplier progress and performance (e.g., schedule, effort, cost, technical performance) as defined in the supplier agreement. 2.1.2- Conduct reviews with the supplier as specified in the supplier agreement. 2.1.3- Conduct technical reviews with the supplier as defined in the supplier agreement. 2.1.4- Conduct management reviews with the supplier as defined in the supplier agreement. 2.1.5- Use the results of reviews to improve the supplier’s performance and to establish and nurture long-term relationships with preferred suppliers 2.1.6- Monitor risks involving the supplier and take corrective action as necessary

SP 2.2 – Monitor Selected Supplier Processes

2.2.1- Identify the supplier processes that are critical to the success of the project. 2.2.2- Monitor the selected supplier’s processes for compliance with requirements of the supplier agreement. 2.2.3- Analyze the results of monitoring the selected processes to detect issues as early as possible that may affect the supplier’s ability to satisfy the requirements of the supplier agreement. 2.2.4- Determine and document actions needed to resolve detected issues

SP 2.3 – Evaluate Selected Supplier Work Products

2.3.1- Identify the work products that are critical to the success of the project and that should be evaluated to help detect issues early. 2.3.2- Evaluate the selected work products. 2.3.3- Determine and document actions needed to address deficiencies identified in the evaluations.

SP 2.4 – Accept the Acquired Product

2.4.1- Define the acceptance procedures. 2.4.2- Review and obtain agreement from relevant stakeholders on the acceptance procedures before the acceptance review or test. 2.4.3- Verify that the acquired products satisfy their requirements. 2.4.4- Confirm that the nontechnical commitments associated with the acquired products are satisfied. 2.4.5- Document the results of the acceptance review or test. 2.4.6- Establish an action plan and obtain supplier agreement to take action to correct acquired products that do not pass their acceptance review or test. 2.4.7- Track action items to closure.

SP 2.5 – Ensure Transition of Products

2.5.1- Ensure that there are facilities to receive, store, integrate, and maintain the acquired products, as appropriate. 2.5.2- Ensure that appropriate training is provided for those involved in receiving, storing, integrating, and maintaining acquired products. 2.5.3- Ensure that acquired products are stored, distributed, and integrated according to the terms and conditions specified in the supplier agreement or license.

Productos de trabajo típicos

Supplier progress reports and performance measures (SP 2.1) Supplier review materials and reports (SP 2.1) Action items tracked to closure (SP 2.1) Product and documentation deliveries (SP 2.1) List of processes selected for monitoring or rationale for nonselection (SP 2.2) Activity reports (SP 2.2) Performance reports (SP 2.2) Performance curves (SP 2.2) Discrepancy reports (SP 2.2) List of work products selected for evaluation or rationale for nonselection (SP 2.3) Activity reports (SP 2.3) Discrepancy reports (SP 2.3) Acceptance procedures (SP 2.4) Acceptance review or test results (SP 2.4) Discrepancy reports or corrective action plans (SP 2.4) Transition plans (SP 2.5) Training reports (SP 2.5) Support and maintenance reports (SP 2.5) Descriptions of how ongoing support obligations, such as warranties and licenses, will be satisfied (SP 2.5)