Document Name Process for Project Management Revision History # 1 2 Version 1.0 1.

1 Date 25-Mar-04 10-Sep-04 Rationale for change Initial Version Pre-Assessment Audit

Doc.ID Version No. Date

PM 1.1 10-Sep-04

Change Description

Traceability from Customer Requirement to Test Cases, Traceability from ReWork to Test Report, Competency Matrix and Guidelines for Effort Estimation were included

3 4 5 6 7 8 9

Author Siva Kumar S. G

Reviewed and Approved by Vamsi Chelluri

Page 1 of 14

Document Name Process for Project Management

Doc.ID Version No. Date

PM 1.1 10-Sep-04

Table Of Contents PROCESS SUMMARY.......................................................................................................................3 REFERENCES.....................................................................................................................................3 DEFINITIONS AND ACRONYMS...................................................................................................3 PROCESS INPUTS.............................................................................................................................4 ENTRY CRITERIA.............................................................................................................................4 PROCEDURE......................................................................................................................................4 VALIDATION CRITERIA...............................................................................................................13 QUALITY RECORDS......................................................................................................................13 PROCESS DELIVERABLES...........................................................................................................13 MEASUREMENT AND ANALYSIS...............................................................................................13 EXIT CRITERIA...............................................................................................................................13 ANNEXURE.......................................................................................................................................13

Author Siva Kumar S. G

Reviewed and Approved by Vamsi Chelluri

Page 2 of 14

Document Name Process for Project Management

Doc.ID Version No. Date

PM 1.1 10-Sep-04

Process Summary The Process for Project Management deals with planning and monitoring all project-related activities. Monitoring helps to ensure that the project is being executed within the estimated efforts, scope and time. Project Management includes within its scope the Software Development Plan, the Quality Control checkpoints and the Process Plan. Project planning involves a number of processes and the extent of planning should be commensurate with the scope of the project and the usefulness of the information developed. Planning is an ongoing effort throughout the lifecycle of the project. Project planning will be done at a granular level based on the information available at the time of preparation. References
CMMI Process Area

Project Planning Project Monitoring and control Integrated Project Management Quantitative Project Management Supplier Agreement Management Risk Management

ISO 9001:2000 Clause Major Clause Name

7.1, 7.3.1, 7.3.4, 8.2.3, 8.2.4 Product Realization; Measurement analysis and Improvement

Definitions and Acronyms WBS Work Break Down Structure. A deliverable-oriented grouping of project elements that organizes and defines the total work scope of the project. Each descending level represents an increasingly detailed definition of the project work. SM PM - Senior Management - Project Manager Author Siva Kumar S. G Reviewed and Approved by Vamsi Chelluri Page 3 of 14

Document Name Process for Project Management PL TT MR CR SPP - Project Lead - Technical Team - Management Representative - Customer Representative - Software Project Plan

Doc.ID Version No. Date

PM 1.1 10-Sep-04

Process Inputs 1. Guidelines for Effort Estimation 2. Records from past project performances

Entry Criteria 1. Approved Project Initiation Form from Senior Management. 2. Customer Service Request Procedure
1. Project planning

1.1. Get the Project Initiation form for kick starting the Project. (PM) 1.2. Provide Detailed Summary of the Project. (PM) 1.3. Identify the type/model of the project. Document the scope of the project. 1.4. Map the project-process (PM) 1.4.1. Decide on the processes applicable for the project, DAR can be used in selecting Processes based on criticality of the projects processes needs. Select the processes and tailor the process to suit projects specific needs (Ref: Process For Process Development, Tailoring process). contribute to organizations process assets. If required, project specific process can be drafted and followed. . These processes will

Author Siva Kumar S. G

Reviewed and Approved by Vamsi Chelluri

Page 4 of 14

Document Name Process for Project Management

Doc.ID Version No. Date

PM 1.1 10-Sep-04

1.4.2. Decide on the applicable procedures and guidelines that will be followed through the course of the project. 1.4.3. Decide on, whether the Project is going to be done by a single team or multiple teams and set the responsibilities in the beginning of the Project. It should be communicated to all the members of the team(s). 1.4.4. Decide on the Assets and repositories to be used in the project. Identify the repositories like Risk repository, Defect repository, Test case repository, Metrics repository, effort repository and training repository for the project. 1.4.5. Until the System study is over, the Project Plan need not be freeze.

1.5. Development Strategy 1.5.1. Decide on the development environment 1.6. Estimation 1.6.1. Use the organizations process assets and Measurement repository for estimating and planning the projects activities 1.6.2. Identify the specific activities that should be performed to produce the various project deliverables. (PM) 1.6.3. Sequence the activities and clearly identify the interdependencies among the activities. (PM) 1.6.4. Arrive at a Work Breakdown Structure to the leaf levels at which control will be exercised. (PM) 1.6.5. Estimate the size of the project. (PM) 1.6.6. Check for infrastructure, if needed estimate for each activity and procure the materials. Refer Process for Purchase. (PM)

Author Siva Kumar S. G

Reviewed and Approved by Vamsi Chelluri

Page 5 of 14

Document Name Process for Project Management 1.6.7.

Doc.ID Version No. Date

PM 1.1 10-Sep-04

Estimate the effort and cost for the work products and tasks based on estimation rationale. (PM)

1.7. Develop a Project Plan 1.7.1. Establish and maintain projects budget and schedule. (PM) 1.7.2. Plan the Human, Non- human resources and support environment needs for software development and project Management.(PM) 1.7.3. Plan for the knowledge and skills needed for the project. Establish training needs and achieve them as mentioned in section 1.14 (procurement). (PM) 1.7.4. Document the roles, responsibilities, and reporting structure in the Project Plan. (PM)

1.7.5. Plan for the involvement of identified stakeholders. (PM). 1.7.6. Establish and maintain the overall project plan content. (PM).

1.8. Data management: 1.8.1. Identify the work products and documents from the project. List the need of the work product. 1.8.2. Identify the method and tools to be used for data management. Identify the forms of data and their accessibility details. 1.8.3. Plan day-to-day data management activities, and back up activities. 1.8.4. Plan the data synchronizing activities. 1.8.5. Establish the project data Management in Project plan and monitor them as per plan.

1.9. Communication Planning 1.9.1. Decide the communication plan inside the team and document all the internal communication. (PM) 1.9.2. Decide on mode of communication. (PM) 1.9.3. Determine who needs what information (PM) and provide them at right time. Author Siva Kumar S. G Reviewed and Approved by Vamsi Chelluri Page 6 of 14

Document Name Process for Project Management

Doc.ID Version No. Date

PM 1.1 10-Sep-04

1.9.4. Perform Status review and produce status review report containing status, progress, and forecasting of the Project. (PM) 1.9.5. Identify the point of contact at the customers side and let the team members be explained the mode of communication and try to form a core communications team which can handle discussions with the customer 1.10. Quality Planning 1.10.1. . Establish and maintain the projects quality and process performance objectives. (PM, SM) 1.10.2. Select the sub processes that compose the projects defined process based on historical stability and capability data for statistical management. (PM, SM ) 1.10.3. Monitor the project to determine whether the projects objectives for quality and process performance will be satisfied, and identified corrective action as appropriate. (PM, SM) 1.10.4. Select the measures and analytic techniques to be used in statistically management of the selected process and sub processes. (PM,SM ) 1.10.5. Establish and maintain an understanding of the variation of the selected sub processes using the selected measures and analytic techniques. (PM, SM) 1.10.6. Monitor the performance of the selected sub processes to determine the capability to satisfy the quality and process performance objectives and identify corrective action as necessary. (PM, SM) 1.10.7. Record statistical and quality management data in the organizations measurement repository. ( PM, SM)

1.11.

Schedule Management Create the project schedule by analysing the activity sequences, activity duration and resource requirements i.e., WBS. (PM)

1.11.1.

1.11.2. (PM, PL) 1.11.3.

Decide on the major milestones and deliverables at each milestone.

Set the target dates for reaching the milestones. (PM)

Author Siva Kumar S. G

Reviewed and Approved by Vamsi Chelluri

Page 7 of 14

Document Name Process for Project Management 1.11.4.

Doc.ID Version No. Date

PM 1.1 10-Sep-04

Decide on when and how the project status will be reviewed and

set frequency of Project Review meetings. (PM)

1.12.

Risk Management (Ref: Process for Risk Management) Identify all major Risks in the Project Determine Mitigation Plan for all the identified risk Initiate Process for Risk Management Process

1.12.1. 1.12.2. 1.12.3.

1.13.Configuration Management (Ref: Process for Software Configuration Management) 1.13.1. 1.13.2. items. 1.13.3. Initiate Process for Software Configuration Management. Identify the Configuration Items from the work products of the project. Decide on the procedure that will be followed to track the identified

1.14.Procurement 1.14.1. Identify the Procurements like human resource, non human resource, training, facilities and other needs to be achieved to carried out the Project. (PM, PL) 1.14.2. Determine the Procurement type and identify the suppliers. 1.14.3. Establish service level agreements between the project team and Suppliers. Monitor and manage the Service level agreement with the supplier. (Refer Purchasing process, Training process, Recruitment Process, Facilities Process) 1.15. Review all other Plan 1.15.1. Review all plans that affect the project to understand project commitments. (PM) 1.15.2. (PM) Reconcile the project plan to reflect available and estimated resources.

1.16 Documenting Project Plan Author Siva Kumar S. G Reviewed and Approved by Vamsi Chelluri Page 8 of 14

Document Name Process for Project Management

Doc.ID Version No. Date

PM 1.1 10-Sep-04

1.16.1 prepare the Project Plan. Specify the criteria for revising the Project Plan and the methodology by which such revisions will be incorporated and intimated to all affected groups. (PM) 1.16.2 Document the Project Plan (Ref: Document Control Process). Send the Project Plan documents for review and after the review update the review comments. (PM) 1.16.3 identify the documents that will get created during the project. Decide on the control and distribution of these documents. (PM) 1.16..4 Obtain commitment from relevant stakeholders responsible for performing and supporting plan execution. (PM)

2 Project Execution (PM, PL, PT) 2.1Conduct Formal Technical Review of the Project Plan and baseline the plan. (PM) 2.2 Conduct a Project meeting, involving all stakeholders and capture their commitment in Minutes of Meeting. 2.3 Discuss to the team members of their roles and responsibilities. (PM) 2.4 Discuss the schedules, if necessary. (PM) 2.5 Carry out the activities mentioned in the project plan. (PM) 2.6 Monitor the project at regular intervals. (PM) 3. Project Verification 3.2 Conduct Formal Technical Reviews (Ref: Process for Technical Review) of phase deliverables and incorporate the changes if raised during the review (PM, RT) 3.3 Analyse deviations, if any from the planned schedule and re -plan, if necessary. (PM, PL) 3.4 If the actual schedule is found to be way out of the planned, it is better to estimate again more realistically, looking into constraints and assumptions. (PM, PL) Author Siva Kumar S. G Reviewed and Approved by Vamsi Chelluri Page 9 of 14

Document Name Process for Project Management

Doc.ID Version No. Date

PM 1.1 10-Sep-04

3.5 Conduct Project Status Review Meetings and if any deviation found update the project plan. (PM) 3.6 Review the status of the project at planned intervals, and Monitor commitments against those identified in the project plan. 3.7 Take corrective action on the identified issues and update the project plan accordingly, and communicate to all stakeholders. (PM). 3.8 Monitor the various project activities for warning signals of a specific risk about to occur, if applicable 4. Project Tracking 4.1 Plan the Periodic Status Review meeting and Milestone review Meetings and conduct as per plan 4.2 The following has to be effectively tracked in Review meetings 4.2.1 Activity/milestones 4.2.2 Schedule & effort 4.2.3. Issues / Risks 4.2.4 Human/Non- human Resource 4.3 Report to the Senior Management about the status of the project on a regular basis. 4.4 Monitor the stakeholder involvement against the project plan. 5 Manage Corrective Action to Closure. 5.1 Collect and analyze the issues and determine the corrective actions necessary to address the issues. 5.2 Take corrective actions on identified issues. 5.3 Manage corrective actions to closure

6. Project Closure Author Siva Kumar S. G Reviewed and Approved by Vamsi Chelluri Page 10 of 14

Document Name Process for Project Management 6.1 Conduct a Project Closure Meeting. (PM, QT) 6.2 Prepare the Project Closure Report

Doc.ID Version No. Date

PM 1.1 10-Sep-04

6.3 Conduct Project Closure after the successful sign-off of the project or all the planned activities of the Project are over. 6.4 All documents related to the project shall be maintained. 6.5 Plan the installation and support activities 6.6 Contribute the process assets, measurements and lessons learned to the organization process asset repository and update other repositories also.
1. Project Planning

1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10

Based on the Project Initiation Form, determine and document the project objectives. (PM, SM) Determine, discuss and specify the project scope and boundaries. (PM, SM) Prepare the Project Plan. Specify the criteria for revising the Project Plan and the methodology by which such revisions will be incorporated and intimated to all affected groups. (PM) State the organizational processes that are applicable to and will be complied with by the project team. (PM) Specify the major project phases and the outputs expected from each phase. (PM) Based on the schedule of deliverables committed to the customer, prepare a detailed Work Breakdown Structure for each project phase. (PM, SM, CR) Describe the Quality Assurance activities planned for the project. Specify the measurable quality objectives for the project. Indicate the Quality Control activities to be undertaken during each project phase. (PM, MR) Indicate the project team structure and its interfaces with other groups/ departments within the organization. Indicate the interfaces between the project team and groups / agencies external to the organization. (PM, SM, CR) Decide on when and how the project status will be reviewed and set frequency of Project Review meetings. (PM) Initiate review of the Project Plan (Refer to the Process for Technical Review) and after resolving review issues, obtain the consent signatures from the Group Heads of affected groups. (PM, SM, MR) Identify the individuals or groups, who are stakeholders in the project. (PM, SM)

2. Resource Selection and Roles Definition

2.1

Author Siva Kumar S. G

Reviewed and Approved by Vamsi Chelluri

Page 11 of 14

Document Name Process for Project Management 2.2 2.3 2.4 2.5 2.6 2.7

Doc.ID Version No. Date

PM 1.1 10-Sep-04

2.8

Conduct a Project Kick-off meeting, involving all team members. Appraise the team members of their roles and responsibilities. Discuss the schedules, if necessary. (PM, SD) Identify and clearly state all project deliverables expected by the customer. Identify and specify the factors that affect the project success or failure. (PM) Identify the development environment and the SDLC Model to be implemented in the project. Estimate the hardware, software and human resources required for software development and project management. (PM) Identify the roles and responsibilities of each project stakeholder. Identify the documents that will get created during the project. Decide on the control and distribution of these documents. (PM) Identify whether any product or service needs to be procured (immediately or in future) from external sources for the project. Intimate the need for procurement to all affected groups and initiate procurement (Refer to the Process for Purchase) at the appropriate time. (PM) Identify the training needs of the project team. Discuss and schedule it according to the organizational resource availability (Refer to the Process for Training). (PM) Log the information regarding performance of the project activities and the related effort expended in the Status Report to the Senior Management (PM) Monitor the performance of project activities with project team members. Initiate and conduct formal Technical Reviews (Refer to the Process for Technical Review) of phase deliverables. Conduct reviews of the work products at each phase and take action against issues, if any, identified in the review reports. (PM, SD) Review the project status periodically and produce Project Status Report containing status of the project, progress of the project and forecasting. Send Project Status Report to Senior Management. (PM, SM) Monitor the work products and determine their compliance to the stated quality objective. Identify ways to eliminate causes of Non-Conforming products. (PM) Analyze deviations, if any, from the Project Plan and revise the Plan, if necessary. (PM) Once the project activities have been performed, initiate conduct of project closure analysis meeting. (SM, PM) Collect and disseminate the performance information of the project. (PM, HR) Analyze the benefits, drawbacks, pitfalls and significant learning achieved from the project. Prepare the Project Closure Analysis Report. (PM, SM, SD, MR) Author Reviewed and Approved by Vamsi Chelluri Page 12 of 14

3. Execute & Monitor project

3.1 3.2 3.3

3.4 3.5 3.6

4. Project Closure

4.1 4.2 4.3

Siva Kumar S. G

Document Name Process for Project Management

Doc.ID Version No. Date

PM 1.1 10-Sep-04

Validation Criteria 1. Technical Review of Project Plan 2. Project Status Review 3. Project Closure Analysis Quality Records 1. Technical Review Report of Project Plan 2. Project Status Review Report 3. Project Closure Analysis Report Process Deliverables 1. Project Plan 2. Project Status Report 3. Project Closure Analysis Report Measurement and Analysis 1. 2. 3. 4. Planned Effort Vs Actual Effort Effort Deviation Planned Date of Completion Vs Actual Date of Completion Schedule Deviation Rework Effort Customer Satisfaction Index

Exit Criteria 1. Approved Project Closure Analysis Report

Annexure 1. 2. 3. 4. 5. 6. Project Initiation Note Template for Project Plan Project Closure Analysis Report Checklist for Project Plan document Customer feedback form Project Status Report Author Reviewed and Approved by Vamsi Chelluri

Page 13 of 14

Siva Kumar S. G

Document Name Process for Project Management 7. Traceability from Customer Requirement to Test Case 8. Traceability from Re-Work to Test Report 9. Competency Matrix 10. Guidelines for Effort Estimations

Doc.ID Version No. Date

PM 1.1 10-Sep-04

Author Siva Kumar S. G

Reviewed and Approved by Vamsi Chelluri

Page 14 of 14