TASKS:

4. Project-Specific Process Plans This section of the Project Management Plan specifies the project-specific process, for this unique project. This section defines the underlying processes, the project management methodology, the infrastructure for this project, and the agreed-to criteria for project acceptance. 4.1 Project Specific Processes Define the relationships among major project work activities and supporting processes. Describe the flow of information and work products among activities and functions. Specify the timing of work products to be generated. Identify the reviews to be conducted. Specify the major milestones to be achieved. Define the baselines to be established. Identify the project deliverables to be completed. Specify the required approvals within the duration of the project. In the process model for the project, include project initiation and project closure activities. Use a combination of graphical and textual notations to describe the project approach for this specific project. Indicate any tailoring of your organization's standard process model, or an industry-accepted model for a project.

4.2 Methods, Tools, and Techniques

Specify the development methodologies, programming languages and other notations, and the processes, tools and techniques to be used to specify, design, build, test, integrate, document, deliver, modify and maintain the project deliverable and non-deliverable work products. Specify the technical standards, policies, and procedures governing development and/or modification of the work products. 4.3 Infrastructure Specify the plan for establishing and maintaining the development environment (hardware, operating system, network and software), and the policies, procedures, standards, and facilities required to conduct the Project. These resources may include workstations, local area networks, software tools for analysis, design implementations, testing, and project management, desks, office space, and provisions for physical security, administrative personnel, and janitorial services. Describe the supporting tools and infrastructure for the project team members (e.g., MS-Project scheduling tool, web-based collaboration tools, project information server, use of Blackberry communication devices, etc.). 4.4 Project and Work Product Acceptance Specify the plan for stakeholder and/or end user (customer) acceptance of the deliverables generated by the Project. Specify objective criteria for determining acceptability of the deliverables.

Reference a formal agreement of the acceptance criteria signed by stakeholders and/or end user representative (and agreed-to by the Project Manager and Project Sponsor). Specify any technical processes, methods, or tools required for deliverable acceptance, such as testing, demonstration, analysis and inspection. Describe the project acceptance criteria, agreed-to by the Project Sponsor and the stakeholders during the Initiation of the project.

5. Project-Supporting Process Plans This section of the Project Management Plan specifies the specific processes supporting the success of this project. This section defines configuration management of the work products; verification and validation steps and approach; project documentation; project quality assurance; project reviews and audits; problem resolution; and the selection and management of the project subcontractors. 5.1 Configuration Management Specify or reference the configuration management plan for the Project, providing the information identified in the following lines. Specify the methods that will be used to perform the following activities: configuration identification, configuration control, status accounting, evaluation, and release management. Specify the processes of configuration management including procedures for the following activities: initial baselining of work products, logging and analysis of change requests, change control board procedures, tracking of changes in progress, and procedures for notification of concerned parties when baselines are established or changed. Identify the automated configuration management tools used to support the configuration management process. 5.2 Verification and Validation

verification of the project work product). Use the bullets as guidelines for completing this section summary.> Specify or reference the verification and validation plan (could be a part of the Project Quality Management Plan) for the project, providing the information identified in the following lines. Specify the scope, tools, techniques and responsibilities for the verification and validation work activities. Specify the organizational relationships and degrees of independence between development activities and verification and validation activities. Specify the use of verification techniques such as traceability, milestone reviews, progress reviews, peer reviews, prototyping, simulation and modeling. Specify the use of validation techniques such as testing, demonstration, analysis and inspection. Identify the automated tools to be used in verification and validation. 5.3 Documentation Specify the plans for generating non-deliverable and deliverable project documentation. Specify the organizational entities responsible for providing input information, and for generating and reviewing the project documentation. Specify the following information or object identification: list of documents to be prepared, controlling template or standard for each document, who will prepare each document, who will review each document, due dates for review copies, due dates for initial baseline versions, and

a distribution list for review copies and baseline versions and quantities required 5.4 Work Product Quality Assurance Specify or reference the quality assurance plan for the Project, containing the information identified in the following lines. Specify the plans for assuring that the Project fulfills its commitments to the IM/IT process and the IM/IT product as specified in the requirements specification, the Project Management Plan, supporting plans and any standards, procedures, or guidelines to which the process or the product must adhere. As applicable, specify the quality assurance procedures to be used, such as analysis, inspection, review, audit, and assessment. Indicate the relationship among the quality assurance, verification and validation, review, audit, configuration management, system engineering, and assessment processes. 5.5 Project Reviews and Audits Specify the schedule, resources, and processes, and procedures to be used in conducting project reviews and audits. Specify the plans for joint customer-project reviews, management progress reviews, developer peer reviews, quality assurance audits, and customer-conducted reviews and audits. List the external agencies that approve or regulate any project deliverable.

5.6 Problem Resolution Specify the resources, methods, tools, techniques and procedures to be used in reporting, analyzing, prioritizing and processing problem reports generated during the project. Indicate the roles of development, configuration management, the change control board, and verification and validation in problem resolution. Provide for separate tracking of effort expended on problem reporting, analysis and resolution, so that rework can be tracked and process improvement accomplished. 5.7 Subcontractor Management Specify or reference the plans for selecting and managing any subcontractors that may participate in or contribute to the Project. Specify the criteria for identifying a need for a subcontractor and then selecting the appropriate subcontractor. Generate a separate management plan for each subcontract, using a tailored version of this Project Plan, and include all items necessary to ensure successful completion of each subcontract as follows: requirements management, monitoring of technical progress, schedule and budget control product acceptance criteria, risk management procedures, additional topics as needed to ensure successful completion of the subcontract, and a reference to the official subcontract and subcontractor/prime contractor points of contact.