Cintipation Corp. CORINTHIAN PROJECT Policy for Requirements Management

Transcription

1 Samples of Level 2 Policies Policy for Requirements Management The purpose of Requirements Management is to establish a common understanding between the customer, Cintipation senior management, and the CORINTHIAN development team concerning the requirements that will be addressed by the software project. Requirements Management involves establishing and maintaining this understanding over the life of the project. To promote this, the CORINTHIAN project team will manage the requirements in such a way as to ensure their proper documentation, thorough review, and consistency with all project activity. This approach covers both the technical and non-technical (e.g., delivery dates) requirements related to the CORINTHIAN project. In support of this the following activities are hereby endorsed by CORINTHIAN project management and Cintipation senior management as points of policy for Requirements Management conduct. 1. All requirements relevant to CORINTHIAN will be documented. 2. System requirements allocated to CORINTHIAN will be controlled to establish a baseline for software engineering and management use. 3. Software plans, products, and activities will be kept consistent with the system requirements allocated to software. 4. CORINTHIAN software project management will establish responsibility for analyzing the system requirements and allocating them to hardware, software, and other system components. 5. CORINTHIAN software project management will make sure that adequate resources and funding have been provided for managing the allocated requirements. 6. As necessary, members of CORINTHIAN s software engineering group (and other software-related groups) will be trained to perform their requirements management activities. 7. CORINTHIAN s software engineering group will review the allocated requirements before they are officially incorporated into the software project. 8. CORINTHIAN software project management will use the allocated requirements as the basis for all software plans, work products, and activities. 9. The CORINTHIAN project team will review any changes to the allocated requirements before they are incorporated into the software project.

2 10. CORINTHIAN software project management will take defined measurements throughout the course of the project to determine the status of the activities for managing the allocated requirements. 11. CORINTHIAN s software project management will review the activities for managing the allocated requirements with Cintipation senior management on a periodic basis. 12. CORINTHIAN s software project management will review the activities for managing the allocated requirements with the general project manager on both a periodic and event-driven basis. 13. CORINTHIAN s software project management will facilitate reviews and/or audits by the software quality assurance group on the activit ies and work products for managing the allocated requirements and will receive compliance reports from the SQA effort. CORINTHIAN Software Project Management CORINTHIAN Project Management DRAFT December 10, 2000 Page 2

3 Policy for Requirements Management The purpose of Requirements Management is to establish a common understanding between the customer, Cintipation senior management, and the CORINTHIAN development team concerning the requirements that will be addressed by the software project. Requirements Management involves establishing and maintaining this understanding over the life of the project. To promote this, the CORINTHIAN project team will manage the requirements in such a way as to ensure their proper documentation, thorough review, and consistency with all project activity. This approach covers both the technical and non-technical (e.g., delivery dates) requirements related to the CORINTHIAN project. In support of this the following activities are hereby endorsed by CORINTHIAN project management and Cintipation senior management as points of policy for Requirements Management conduct. 1. All CORINTHIAN requirements will be documented. 2. CORINTHIAN requirements will be approved by the software managers and impacted groups before any project commitments are made. 3. Software plans and activities for CORINTHIAN will be kept consistent with any changes to the requirements. CORINTHIAN Software Project Management CORINTHIAN Project Management DRAFT December 10, 2000 Page 3

4 Policy for Software Project Planning The purpose of Software Project Planning is to establish reasonable plans for performing the software engineering and managing the software project. Software Project Planning involves first establishing the commitments to be delivered under the work and then developing estimates for the work to be performed and defining the plan to perform the work. To promote this, the CORINTHIAN project team will manage software project planning in such a way as to ensure the use of approved requirements as the basis for all planning, provide for the review of all commitments and development plans, and facilitate the proper control of the plan over the course of the CORINTHIAN project. In support of this, the following activities are hereby endorsed by CORINTHIAN project management and Cintipation senior management as points of policy for Software Project Planning conduct. 1. Before project planning begins an approved Statement of Work will exist for the project. 2. Software estimates developed for use in planning and tracking the software project will be documented. 3. Software project activities and commitments will be documented. 4. Groups and individuals that are impacted by established project commitments will agree to their commitments prior to work. 5. CORINTHIAN project management will appoint a software project manager who will be responsible for negotiating commitments and developing the project's software development plan. 6. CORINTHIAN software project management will be sure to allow for adequate resources and funding for planning the software project. 7. Software managers, software engineers, and other individuals involved in CORINTHIAN software project planning will be trained in the estimating and planning procedures applicable to their areas of responsibility. 8. The CORINTHIAN software engineering group will participate on the project proposal team. 9. CORINTHIAN project management will initiate software project planning in the early stages of, and in parallel with, the overall project planning. 10. CINTIPATION senior management will review software project commitments made to individuals and groups external to the organization prior to commitment approval. DRAFT December 10, 2000 Page 4

5 11. The CORINTHIAN software development plan (SDP) will be created according to a documented procedure. 12. Estimates for the size of the software work products, the cost and effort of the project, needed computer resources, project timeline, and any related risks will all be documented and derived according to a documented procedure. 13. CORINTHIAN software project management will record and save all software planning data. 14. CORINTHIAN software project management will take periodic measurements to determine the status of the software planning activities. 15. CORINTHIAN software project management will review the activities for software project planning with CINTIPATION senior management on a periodic basis. 16. CORINTHIAN software project management will review the activities for software project planning with the CORINTHIAN project manager on both a periodic and event-driven basis. 17. CORINTHIAN software project management will allow reviews or audits by the software quality assurance group on the activities and work products for software project planning and will receive reports on the results. Project Management CORINTHIAN Software Management CORINTHIAN Project DRAFT December 10, 2000 Page 5

6 DRAFT December 10, 2000 Page 6

7 Policy for Software Project Planning The purpose of Software Project Planning is to establish reasonable plans for performing the software engineering and managing the software project. Software Project Planning involves first establishing the commitments to be delivered under the work and then developing estimates for the work to be performed and defining the plan to perform the work. To promote this, the CORINTHIAN project team will manage software project planning in such a way as to ensure the use of approved requirements as the basis for all planning, provide for the review of all commitments and development plans, and facilitate the proper control of the plan over the course of the CORINTHIAN project. In support of this, the following activities are hereby endorsed by CORINTHIAN project management and Cintipation senior management as points of policy for Software Project Planning conduct. 1. Only approved requirements will be used as the basis for CORINTHIAN project planning 2. The project's commitments on CORINTHIAN will be negotiated between project management, the software managers, and other impacted managers. 3. Affected groups will review the software size estimates, effort and cost estimates, schedules, and other commitments prior to approval. 4. Senior management will reviews all commitments made to external organizations regarding CORINTHIAN. 5. The CORINTHIAN Software Development Plan will be managed and version controlled. Project Management CORINTHIAN Software Management CORINTHIAN Project DRAFT December 10, 2000 Page 7

8 Policy for Software Project Tracking and Oversight The purpose of Software Project Tracking and Oversight is to provide adequate visibility into the actual activities and progress on CORINTHIAN so that management can take effective actions when performance deviates significantly from the software plans. Software Project Tracking and Oversight involves tracking and reviewing the software accomplishments and results against documented estimates, commitments, and plans, and adjusting these plans based on the actual accomplishments and results. This is accomplished through continuous inter-team communications and reviews. In support of this, the following activities are hereby endorsed by CORINTHIAN project management and Cintipation senior management as points of policy for Software Project Planning conduct. 1. CORINTHIAN software project management will track actual results and performances against the software plans. This tracking will include the size of the software work products, the project s effort and costs, the critical computer resources, the schedule and the project risks. take corrective actions as necessary based on the tracking data. 2. Software project management will take corrective actions and manage to closure when actual results and performance deviate significantly from the software plans. 3. Software project management will obtain agreement to changes to CORINTHIAN software commitments from the affected groups and individuals. 4. Software project management will use the approved CORINTHIAN software development plan as the basis for managing the CORINTHIAN project. 5. The software project manager will explicitly assign responsibility for software work products and activities to be delivered by the CORINTHIAN team. 6. Software project management will be sure to provide adequate resources and funding for tracking the software project. 7. Software managers, as needed, will be trained in managing the technical and personnel aspects of the CORINTHIAN software project and first-line software managers will receive, as needed orientation in the technical aspects of the software project. 8. Software project management will revise the CORINTHIAN software development plan according to a documented procedure. DRAFT December 10, 2000 Page 8

9 9. Software project management will review software project commitments and changes to commitments made to individuals and groups external to the organization with senior management according to a documented procedure. 10. Software project management will communicate approved changes to commitments that affect the software project to the members of the software engineering group and other software-related groups. 11. Software project management will record actual measurement data and planning data for the software project. 12. Software project management will conduct periodic internal reviews and scheduled formal reviews to address the accomplishments and results of the software project at selected project milestones according to a documented procedure. 13. CORINTHIAN software project management will review the activities for software project tracking with CINTIPATION senior management on a periodic basis. 14. CORINTHIAN software project management will revie w the activities for software project tracking with the CORINTHIAN project manager on both a periodic and event-driven basis. 15. CORINTHIAN software project management will allow reviews or audits by the software quality assurance group on the activities and work products for software project tracking and will receive reports on the results. CORINTHIAN Software Project Management CORINTHIAN Project Management DRAFT December 10, 2000 Page 9

10 Policy for Software Project Tracking and Oversight The purpose of Software Project Tracking and Oversight is to provide adequate visibility into the actual activities and progress on CORINTHIAN so that management can take effective actions when performance deviates significantly from the software plans. Software Project Tracking and Oversight involves tracking and reviewing the software accomplishments and results against documented estimates, commitments, and plans, and adjusting these plans based on the actual accomplishments and results. This is accomplished through continuous inter-team communications and reviews. In support of this, the following activities are hereby endorsed by CORINTHIAN project management and Cintipation senior management as points of policy for Software Project Planning conduct. 1. A Software development Plan (SDP) is maintained as the central tool for tracking the project. 2. The project manager (PM) is kept informed (by all subgroup and team managers) of the project's status and issues. 3. Adjustments to the SDP or to the project team are made when the SDP is not being achieved. 4. Changes to the SDP are reviewed by all impacted groups before the changes are implemented. 5. Senior management reviews all changes to the SDP that impacts commitments to external groups. CORINTHIAN Software Project Management CORINTHIAN Project Management DRAFT December 10, 2000 Page 10

11 DRAFT December 10, 2000 Page 11

12 Policy for Software Configuration Management The purpose of Software Configuration Management is to establish and maintain the integrity of the work products for CORINTHIAN throughout the project's software life cycle. Software Configuration Management involves identifying the configuration of the software (i.e., selected software work products and their descriptions) at given points in time, systematically controlling changes to the configuration, and maintaining traceability of the configuration throughout the life cycle. The work products placed under software configuration management include the software products that are delivered to the customer (e.g., the software requirements document and the code) and the items that are identified with or required to create these software products (e.g., the compiler). In support of this, the following activities are hereby endorsed by CORINTHIAN project management and Cintipation senior management as points of policy for Software Project Planning conduct. 1. All SCM activities for CORINTHIAN will be documented; this CORINTHIAN SCM plan will be created according to a documented procedure and the plan will be used as the basis for performing all SCM activities. 2. CORINTHIAN SCM will control changes to identified software work product and inform affected groups and individuals of the status and content of evolving work products and software baselines. 3. CORINTHIAN project management will establish a board having the authority for managing the project's software baselines (i.e., a software configuration control board - SCCB) and will appoint a group to be responsible for coordinating and implementing SCM for the project (i.e., the SCM group). 4. CORINTHIAN project management will establish a configuration management library system as a repository for the software baselines. 5. CORINTHIAN project management will provide adequate resources and funding for performing SCM activities. 6. Members of the SCM group, as necessary, will be trained in the objectives, procedures, and methods for performing their SCM activities, as will members of the software engineering group and other software-related groups. 7. CORINTHIAN SCM will control changes to baselines according to a documented procedure. 8. CORINTHIAN SCM will create products from the software baseline library and control their releases according to a documented procedure. DRAFT December 10, 2000 Page 12

13 9. All CORINTHIAN software baseline audits will be conducted according to a documented procedure. 10. The CORINTHIAN configuration manager will take periodic measurements to determine the status of the SCM activities. 11. The CORINTHIAN SCM group will periodically audit software baselines to verify that they conform to the documentation that defines them. 12. The CORINTHIAN SCM group will allow software project management to review the activities for SCM (with CINTIPATION senior management) on a periodic basis. 13. The CORINTHIAN SCM group will review SCM activities for software project tracking with CORINTHIAN project management on both a periodic and event-driven basis. 14. The CORINTHIAN SCM group will allow reviews or audits by the software quality assurance group on the activities and work products for software project tracking and will receive reports on the results. CORINTHIAN Software Project Management CORINTHIAN Project Management DRAFT December 10, 2000 Page 13

14 Policy for Software Configuration Management The purpose of Software Configuration Management is to establish and maintain the integrity of the work products for CORINTHIAN throughout the project's software life cycle. Software Configuration Management involves identifying the configuration of the software (i.e., selected software work products and their descriptions) at given points in time, systematically controlling changes to the configuration, and maintaining traceability of the configuration throughout the life cycle. The work products placed under software configuration management include the software products that are delivered to the customer (e.g., the software requirements document and the code) and the items that are identified with or required to create these software products (e.g., the compiler). In support of this, the following activities are hereby endorsed by CORINTHIAN project management and Cintipation senior management as points of policy for Software Project Planning conduct. 1. Responsibility for SCM is specifically assigned for the project. 2. SCM processes are implemented throughout the project lifecycle. 3. SCM is implemented for all projects within the organization. 4. The projects are each given adequate access and resources within the SCM environment. 5. Software baselines and general SCM activities are audited by management on a regular basis. CORINTHIAN Software Project Management CORINTHIAN Project Management DRAFT December 10, 2000 Page 14

15 Policy for Software Quality Assurance The purpose of Software Quality Assurance is to provide management with appropriate visibility into the processes being used by the CORINTHIAN project to ensure quality output. Software Quality Assurance is responsible for reviewing and auditing the software products and activities from the project to verify that they comply with the applicable procedures and standards. SQA is also charged with providing software project management and other appropriate management with the results of these reviews and audits. In support of this, the following activities are hereby endorsed by CORINTHIAN project management and Cintipation senior management as points of policy for Software Project Planning conduct. 1. Appoint a group to be responsible for coordinating and implementing SQA for the project (i.e., the SQA group). 2. Provide adequate resources and funding for performing the SQA activities. 3. Train members of the SQA group to perform their SQA activities. 4. Orient the members of the software project on the role, responsibilities, authority, and value of the SQA group. 5. Plan software quality assurance activities. Prepare a SQA plan for the software project according to a documented procedure. Perform the SQA group's activities in accordance with the SQA plan. 6. Objectively verify adherence of software products and activities to the applicable standards, procedures, and requirements. 7. Inform affected groups and individuals of software quality assurance activities and results. 8. Ensure that noncompliance issues that cannot be resolved within the software project are addressed by senior management. 9. Have the SQA group participate in the preparation and review of the project's software development plan, standards, and procedures. 10. Have the SQA group review the software engineering activities to verify compliance. 11. Have the SQA group audit designated software work products to verify compliance. DRAFT December 10, 2000 Page 15

16 12. Have the SQA group periodically report the results of its activities to the software engineering group. 13. Document deviations identified in the software activities and software work products and handle according to a documented procedure. 14. Have the SQA group conduct periodic reviews of its activities and findings with the customer's SQA personnel, as appropriate. 15. Make and use measurements to determine the cost and schedule status of the SQA activities. 16. Have experts independent of the SQA group periodically review the activities and software work products of the project's SQA group. CORINTHIAN Software Project Management CORINTHIAN Project Management DRAFT December 10, 2000 Page 16

17 Policy for Software Quality Assurance The purpose of Software Quality Assurance is to provide management with appropriate visibility into the processes being used by the CORINTHIAN project to ensure quality output. Software Quality Assurance is responsible for reviewing and auditing the software products and activities from the project to verify that they comply with the applicable procedures and standards. SQA is also charged with providing software project management and other appropriate management with the results of these reviews and audits. In support of this, the following activities are hereby endorsed by CORINTHIAN project management and Cintipation senior management as points of policy for Software Project Planning conduct. 1. Software quality assurance practices are in place on all projects. 2. The SQA team retains an independent channel for reporting to executive management. 3. Senior management periodically reviews SQA activities and results. CORINTHIAN Software Project Management CORINTHIAN Project Management DRAFT December 10, 2000 Page 17