Project Execution Plan                                              BPOz




    Sample Client Project Execution Plan

   ...
Project Execution Plan                                                                                                    ...
Project Execution Plan                                                                              BPOz




   1. Project...
Project Execution Plan                                                                 BPOz



        Roles              ...
Project Execution Plan                                                                    BPOz



   b. Status Reporting

...
Project Execution Plan                                                                                 BPOz


    Escalati...
Project Execution Plan                                                                     BPOz




   3. SLA Management
 ...
Project Execution Plan                                                                      BPOz


   4. Change Management...
Upcoming SlideShare
Loading in...5
×

Projection Execution Plan

1,115

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,115
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
39
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Projection Execution Plan"

  1. 1. Project Execution Plan BPOz Sample Client Project Execution Plan Document No BPOZ/2003-2004/6817 Version. 1.0 Authorized by Date Sep 12, 2003 Schedule # Project # 1
  2. 2. Project Execution Plan BPOz Table of Content: .....................................................................................................................................................................................1 TABLE OF CONTENT:........................................................................................................................................................2 1.PROJECT MANAGEMENT.................................................................................................................................................3 a.Roles and Responsibilities:..................................................................................................................................3 b.Status Reporting ..................................................................................................................................................5 c.Issue Management...............................................................................................................................................5 d.Escalation Mechanism.........................................................................................................................................5 ................................................................................................................................................................................6 2.RISK MANAGEMENT......................................................................................................................................................6 3.SLA MANAGEMENT ....................................................................................................................................................7 4.CHANGE MANAGEMENT.................................................................................................................................................8 2
  3. 3. Project Execution Plan BPOz 1. Project Management The project plan, which is prepared during the initial stages of the project, describes all the details that are relevant to the successful execution of the project. It is prepared by the Project Manager and is reviewed by the Delivery Manager and/or Business Manager at BPOz. The remainder of this section mentions some of the crucial aspects of the project execution, which are essential elements of the project plan. Formation of a well-structured project team is critical to the success of the project. The number of resources and each role will be decided by our Client based on the life cycle stage of the project. The team size will increase or decrease based on the phase of the sourcing/re- engineering. Client Location Offshore - BPOz Program Manager Program Manager Client BPOz Client Project Manager Offshore Project Manager - BPOz BPOz Module Leads Technical Analysts Business Analysts Reporting Hierarchy of BPOz Teams Critical Communication Channels Quality Professionals a. Roles and Responsibilities: We recognize that strong project management is key to the success of this project and propose an organization of clearly defined roles and responsibilities accordingly. The following defines the roles and responsibilities of the proposed team members from Client and BPOz: 3
  4. 4. Project Execution Plan BPOz Roles Responsibilities BPOz Client Project  Responsible for managing the Client initiatives Manager  Offshore support coordination  Handle issue escalation and resolution  Project Scheduling and Task allocation  Project monitoring and Status reporting  Review project standards and all work products  Quality metrics collection and reporting  Project related interfaces BPOz offshore Project  Responsible for managing the PERS initiatives Manager  Offshore support coordination  Handle issue escalation and resolution  Project Scheduling and Task allocation  Project monitoring and Status reporting  Review project standards and all work products  Quality metrics collection and reporting  Project related interfaces  Quality Assurance of deliverables Module Leads  Requirements understanding and analysis  Detailed design  Participate in design discussions  Code and Test major enhancements  Perform deliverable reviews  Running the test cases  Rectifying the deliverables in case of defects  Documentation  Support the application during acceptance testing Technical Analysts  Provide effective tech support to the team  Prototype & test concepts/ hypothesis  Participate in design discussions  Perform code reviews  Mentor business analysts Business Analysts  Prepare functional and detailed design documents  Research  Defect rectification  Participate in deliverable reviews  Prepare / Modify deliverables  Support the acceptance testing Quality Professionals  Assist in checklists implementation, system and integration test plans  Quality Documentation  Perform group reviews  Organize Test cases and reviews with BPOz Developers 4
  5. 5. Project Execution Plan BPOz b. Status Reporting Weekly status report will be submitted with  Milestones achieved for the week  Milestones missed for the week  Milestones planned next week  Issues c. Issue Management BPOz team would maintain an ‘Issue Tracker’ that would have details of all the issues. For every issue raised, it would have following data:  Issue number  Issue details/description,  Issue raised by,  Issue-raised date,  Issue priority,  Issue resolution initiation date,  Issue resolution targeted end date, and  Issue resolution actual end date. The BPOz Project Manager will present the status-report at periodic meetings enumerating the issues resolved, issued taken up for resolution and the current status of each. The BPOz Client Project Manager will resolve all project-related issues in agreement with client. In case a satisfactory response is not obtained from either side, issues may be escalated according to a predefined escalation hierarchy. One of the preliminary activities in the initial stage would be to identify escalation hierarchies and thresholds for issue escalations to the next level for each of the key interfaces in the project. d. Escalation Mechanism BPOz Onsite Coordinator will resolve all project-related issues after discussing these with the Program Manager. In case a satisfactory response is not obtained from either side, issues may be escalated according to a predefined escalation hierarchy defined below.The following tables give the levels of people in Client and BPOz to whom issues may be escalated. 'Unresolved period' indicates the time that has elapsed since an issue was first raised. Escalation Procedure (Client to BPOz) Level Unresolved period BPOz Program Manager 2 days BPOz Account Manager/ BPOz Business Development Manager 5 days 5
  6. 6. Project Execution Plan BPOz Escalation Procedure (BPOz to Client) Level Unresolved period Client Program Manager 2 days PERS SSP Project Sponsor 5 days 2. Risk Management Detailed risk identification, monitoring and mitigation plan will be put together as part of project planning. This will encapsulate the risks (measured for their impact & severity) faced by the project at any point in time as well as the steps identified to mitigate those risks. The Risk Management Plan will be dynamic in nature. The risks faced by the project keep changing with time; new risks emerge, the severity of identified risks may increase or decrease, and so on. Therefore, the Risk Management Plan cannot be static. It has to be continually modified to reflect the changing realities of the project. Risk management has the following steps  Risk Assessment:  Risk identification  Risk prioritization  Risk Control  Risk Monitoring Risk identification, prioritization and planning are done during project initiation. Risk monitoring is done during project execution. Risk Mitigation Strategy Availability of Client personnel Client may make multiple analysts / business users with domain knowledge to ensure smooth transfer of knowledge and testing of final programs Non-availability of manpower due to leave and Leave requirements of team members will be holidays identified and detailed schedule prepared accordingly Test data may not be available in time OSC / Offshore Project Manager to co-ordinate with client and make information available offshore well in advance Inter-dependency between multiple initiatives Scope Management within the client organization Roles and Responsibilities Matrix Defects in existing system Identify bugs during analysis and inform client. Treat these as separate requests if bug fix required by the client. Person dependency Cross training will be used as a tool to mitigate risk and also enable support team to handle crests and troughs in workload apart from emergency situations. 6
  7. 7. Project Execution Plan BPOz 3. SLA Management BPOz will be responsible for tracking and measuring all the relevant SLAs during the execution of the project. SLA data will be tracked on monthly basis. The cumulative SLA score will then be calculated every quarter to assess SLA adherence and determine the amount of penalty or bonus to be applied. By default, at the end of every six months, we and our client will together review the SLA trends over the past six months, and, if necessary, changes in SLA parameters, measures and targets will be incorporated. Although the default interval between such reviews will be six months, BPOz or Client may initiate a review exercise even before six months if necessary. Following diagram depicts the BPOz SLA governance framework. Each of the identified SLA performance indicator measures will be assigned a weight as given above. A range of “Normal Level” values will also be specified for each SLA performance indicator measure. The Normal Level defines the expected or targeted level of service, and if achieved, will be considered as “performance at par”. Failing to achieve the Normal Level of service will be considered as “Floor Level” performance or “performance below par”. Achieving service levels higher than Normal Level will be considered as “Quality Level” performance or “performance above par”. During the monthly Metrics/Milestone Analysis, we ensure the following activities: • Root cause analysis to identify root causes will be conducted • Detailed level action plan to prevent recurrence of commonly caused defects will be prepared and shared with Client If root cause analysis reveals a factor outside BPOz’s control as the cause, then the particular SLA Measure would be considered to have been met, after discussing the same with Client management in appropriate forum. 7
  8. 8. Project Execution Plan BPOz 4. Change Management A typical change management process flow is explained here. Changes once identified will be logged. A detailed analysis for impact on the project will be done. The impact will be measured in terms of impact on timeline and cost. A risk assessment is also done. Based on all these factors and amount of impact, a change request form will be submitted to the program office for approval. Change requests that are approved will be attached to the project contract. Minor changes would take not more than two person day’s effort, will become part of the project effort. This threshold is typically defined as part of project execution terms and conditions. Major changes would have a financial impact on the project. Such changes will have to be formally approved. To minimize impact on the project schedule, we recommend that these approvals be obtained within five days after the change request is submitted. Cost will be determined based on the effort and on approval of the cost and time estimates, the change request is incorporated into the project plan. Requirement changes may occur at any point during the project execution stage. It is important to identify a process for requirements change management. The following diagram depicts the actions that are normally performed when requirements change: Log the Analyze Plan for incorporating requirement change Impact changes Apply changes to work Obtain Customer Evaluate Project products Sign off Cost The BPOz team will use the change request process for new requirements, changes to work in progress or for changes to deliverables that have been accepted by Client. The template indicated here will be used to log and monitor changes during the lifecycle of the project. Request number Description of change Impact on the project a. Schedule b. Effort c. Cost Status of the change Date requested Date approved/rejected Date to be delivered by Date completed Comments Signatures BPOz Program Manager CLIENT Program manager Name Name Signature & Date Signature & Date 8

×