The final report for your Course Project will be a formal report that you will present to the Project Sponsor (your professor). You will be using the information that you have been preparing each week of the course. You will prepare the report using excellent report writing skills and with content that would be read by an executive of an enterprise. Now is the time to organize and present the information in a way that is understandable and meaningful to your Project Sponsor.
Write the report as though the Project Sponsor is reading the planning details for the first time. You have prepared information each week during the course, and that information will form the foundation for this report. For the final report, you should augment that information with further explanations to facilitate the comprehension of what you are presenting. You will need to demonstrate in your report that you have thought through all that is required to manage your project successfully. Continued funding and resource assignments will depend on how well you have planned, estimated, and communicated all aspects of your project. You will submit your final report to the Week 8 Course Project Dropbox. See the course Syllabus for due date requirements.
Customer Care Website Implementation
Table of Contents
Executive Summary 4
Integration Management 4
Project Scope Statement: 4
Project Scope Justification: 5
Project Success: 5
Functional Area Interfaces 5
Project Team Members and Roles: 6
Project Team Reporting Structure: 6
Project Deliverables: 7
Project Closure Information 7
Scope Management 9
Scope Definition 9
Work Breakdown Structure 9
Time/Schedule Management 9
Activity List 9
Project Milestones: 12
Project Cost Management 12
Project Quality Management 14
Project Deliverable Quality Requirements 14
Project Deliverable Quality Monitoring 14
Project Deliverable Quality Reporting 15
Project Deliverable Quality Discrepancy Decisions 15
Project Human Resource Management 15
Resource Analysis 15
Resource(s) Doing the Most Work 17
Alternative Resource Assignments 17
Resource Gap Analysis 17
Optimization: 17
Communications Management 18
Project Team Communications 18
Project Team Conflict Resolution 19
Project Information to Monitor 20
How to Collect Project Information 20
Frequency for Project Information Collection 20
Project Status Information and Recipients 21
Plan and Take Adaptive Action 21
Methods to Analyze the Impact of the Status Information 21
Process/Procedures to Make Decisions that Affect the Project Schedule and Budget 21
People Who Will Be Involved in Making Project Status Decisions 22
Method to Communicate Project Status Decisions 22
Project Risk Management 23
Risk Management Plan: 23
Procurement Management 25
Conclusion 25
References 26
Executive Summary
In this project we intend to streamline and enhance our customer- user experience for his or her support related needs after or before a purchase have been made. Currently we only support a customer over the phone. At peak hours, this causes line congestion and long wait time for our customers resulting in dip in customer satisfaction level. The creation of a customer care website will allow our company to engage with the customer at multiple points including telephone which we already do. 90% of the calls we log are for general questions or are mostly order related which might not require a call in case a portal is available. This projects aims to create a customer care portal mentioned above for better customer satisfaction.
Over the last three years, our annual sales and revenues have almost tripled. While a phone support option was initially sufficient, peak hour service provision has become problematic. In case we want to go along with our existing support model, we would require to at least double our voice support specialist strength. This would result in additional recurring expenses for the company towards employee salary and equipment. The project should be able to address this issue as well and enable the company to achieve better operational excellence. Enhancement to the website will also be possible and will help us to align better with our customers.
Integration Management
Project Manager: Tyrone Labad
Project Manager- Responsibilities 1. Create project scope and get sign off from executive sponsor
2. Ensure project is implemented within budget and schedule with major functionality completed
3. Identify and manage project team to ensure successful project delivery
4. Regular and relevant project communication through reports and meetings
5. Effectively manage project risk and have proactive risk management and response plan
6. Identify and book resources that are required for project such as computers, hardware, projectors, meeting rooms
Project Manager: Mr. Sponsor, Director, Customer Care
Project Scope Statement:
The ‘Customer Care Website Implementation’ project is about the analysis, design and implementation after testing of a customer care website with the intention of maximizing customer satisfaction. The website would have functionality that would allow customers to check order status, communicate with company, log complaints and suggestions and hold the entire customer history. They would also have the ability to track the status of complaints. The project is expected to be completed within a period of 180 days and with a budget not exceeding $90,000. The current estimated budget is at around $80,000.
Project Scope Justification:
This project would significantly increase customer satisfaction and bring down the long term cost in maintaining the customer care department.
Project Success:
1. All ‘must have’ functionality implemented and working
2. Less than 5 defects for every 1000 lines of code
3. Page refresh and response times of less than 5 seconds
4. All user acceptance test cases should be successful
5. Project should comply with corporate usability and coding standards
Functional Area Interfaces
Functional Area: Interfacing Functional Area(s):
Customer Profile Order History, Messages, User Interface, Access and Authentication
Order History Customer Profile, User Interface
Messages Customer Profile, User Interface
Reporting User Interface
Dashboard User Interface, Customer Profile
User Interface All Functional Areas
Access and Authorization Customer Profile
Project Team Members and Roles:
Name Title Expertise Responsibilities
Jim Jones Senior Manager, Customer Care • Customer Care Operations
• Company business processes • Provide detailed requirements
• Review and approve functional requirements
• Provide people to perform user acceptance testing
Mitch Leary Business Analyst • Systems analysis and design
• Systems and technical documentation • Gather requirements from business users
• Document and provide functional requirements document
• Facilitate requirements clarifications
Sandra Price Software Architect • Technical design and development • Create technical design and get it approved
• Communicate design to software developers
Bob Mathew Software Developer - Lead • System development • Coding of the system
• Unit testing of system
Tim Robinson Software Tester • Manual and Automation Testing • Work with business analyst to create test scenarios
• End to end testing of the system
• Share testing results with project team
Project Team Reporting Structure:
The reporting structure for the current project is given below. The organizational level decision maker and overall responsibility for the project lies with the Project Sponsor. The Project Manager and Customer Care manager would report to the executive sponsor and would also manage and assign resources that are needed for the project. At the third level are the project team members. This is illustrated below
Project Deliverables:
Deliverable Name Description
Fully functional customer care website The company customer care website must be live and fully functional,
Requirements specification document Requirements of the system and analysis must be captured in a specifications document
System design document Technical design and implementation details must be captured in a technical design document
System testing and results Testing results and details of the approach and design of testing the system
User manuals Detailed user manuals that would be used for system maintenance and upgrades
Working code The code developed for the project
End user training Training for the team that would support the project and training to business users
Project Closure Information
Project Performance
There would be different types of information captured about the project such as
1) High level project objectives, scope and summary
2) Project plan and schedule
3) Key project learning-
4) Project issue and resolution register
5) Project retrospective.
These would be recorded in word templates created for this purpose and stored on the company intranet that would be searchable and hence help other projects that are doing similar things.
Tasks to be completed as Part of the Project Closure
The different tasks that must be completed as part of the project closure are
1) Project retrospective - All stakeholder project team meeting on what went right, what could be improved and what can be practices that should be applied to not repeat mistakes
2) Lessons learned - Meeting and then follow up document on things that were learned during the course of the project
3) Settling bills and releasing resources - Ensuring that project is closed from an administering and resourcing perspective
4) End of project report - End of project report to client and project sponsor
5) Handover to maintenance team - Hanover the website to the team that would be operationally maintaining the system
Archived Project Information
Of the information that is recorded above, there must be a level of segregation as to what is project sensitive information and hence should not be shared with other project, and on the other hand what information would be useful to others in the company from a best practices sharing and knowledge sharing perspective. High level information such as project objectives and presentations from project kick off meeting along with project retrospective and project lessons learned documents would be archived and stored on company intranet to be searchable and used by other projects.
Project Acknowledgements and Celebration
There would be an end of project meeting with all stakeholders including project sponsor to acknowledge project completion and also appreciate all the work that has been put into. There would also be a team dinner as a gesture of formal closing of the project.
Scope Management
Scope Definition
The ‘Customer Care Website Implementation’ project is about the analysis, design and implementation after testing of a customer care website with the intention of maximizing customer satisfaction. The website would have functionality that would allow customers to check order status, communicate with company, log complaints and suggestions and hold the entire customer history. They would also have the ability to track the status of complaints. The project is expected to be completed within a period of 180 days and with a budget not exceeding $90,000. The current estimated budget is at around $80,000.
Work Breakdown Structure
The Work Breakdown Structure file has been embedded below. This details the different sections and the timelines.
Time/Schedule Management
The project will be spanned over a period of 180 days. This project has six major milestones. The activity list given below provides the details of the effort estimate for each task and subtask. This schedule has been made taking into account a 5% buffer time to compensate for any unforeseen problems during the execution phase.
Activity List
Below is the activity list of the projects which shows all the Tasks and subtasks including their projected timelines
WBS Task Name Duration Start Finish
1 Customer Care Website Implementation 180 days Mon 4/30/12 Fri 1/4/13
1.1 Project Initiation and Planning 15 days Mon 4/30/12 Fri 5/18/12
1.1.1 Initial meeting with project sponsor 1 day Mon 4/30/12 Mon 4/30/12
1.1.2 Identify user groups 3 days Tue 5/1/12 Thu 5/3/12
1.1.3 Plan for resources and people required 5 days Fri 5/4/12 Thu 5/10/12
1.1.4 Create and Share project plan with team 5 days Fri 5/11/12 Thu 5/17/12
1.1.5 Project Kickoff Meeting 1 day Fri 5/18/12 Fri 5/18/12
1.2 Requirements Analysis 11 days Mon 5/21/12 Mon 6/4/12
1.2.1 Requirements meeting with users 10 days Mon 5/21/12 Fri 6/1/12
1.2.2 Requirements workshop 3 days Mon 5/21/12 Wed 5/23/12
1.2.3 Document requirements and submit 5 days Thu 5/24/12 Wed 5/30/12
1.2.4 Review of requirements 3 days Thu 5/31/12 Mon 6/4/12
1.2.5 Requirements signoff 0 days Mon 6/4/12 Mon 6/4/12
1.3 System Design 11 days Tue 6/5/12 Tue 6/19/12
1.3.1 Logical design of system 5 days Tue 6/5/12 Mon 6/11/12
1.3.2 Physical design of system 5 days Tue 6/12/12 Mon 6/18/12
1.3.3 Validate and review design document 3 days Tue 6/12/12 Thu 6/14/12
1.3.4 Discussion of design with team 1 day Tue 6/19/12 Tue 6/19/12
1.3.5 Design approval and signoff 0 days Tue 6/19/12 Tue 6/19/12
1.4 Coding and Development 80 days Wed 6/20/12 Tue 10/9/12
1.4.1 Meeting for understanding and clarifying requirements 5 days Wed 6/20/12 Tue 6/26/12
1.4.2 Coding and development 40 days Wed 6/27/12 Tue 8/21/12
1.4.3 System testing 20 days Wed 8/22/12 Tue 9/18/12
1.4.4 Code Integration and testing 15 days Wed 9/19/12 Tue 10/9/12
1.4.5 Fix any errors found during testing 10 days Wed 9/19/12 Tue 10/2/12
1.4.6 Review and inspection of fixes 5 days Wed 10/3/12 Tue 10/9/12
1.4.7 Implementation signoff 0 days Tue 10/9/12 Tue 10/9/12
1.5 User Acceptance Testing 39 days Wed 10/10/12 Mon 12/3/12
1.5.1 Identify test user groups and create test plan 3 days Wed 10/10/12 Fri 10/12/12
1.5.2 Communicate test plan to test user groups 2 days Mon 10/15/12 Tue 10/16/12
1.5.3 System demo to test users 2 days Wed 10/17/12 Thu 10/18/12
1.5.4 User pilot phase 1 - 5 users 5 days Fri 10/19/12 Thu 10/25/12
1.5.5 User pilot phase 2 - 100 users 20 days Fri 10/26/12 Thu 11/22/12
1.5.6 Retrospective stage - for addressing user queries and fix issues 5 days Fri 11/23/12 Thu 11/29/12
1.5.7 Take feedback from pilot users to incorporate in user training 2 days Fri 11/30/12 Mon 12/3/12
1.5.8 User signoff on testing 0 days Mon 12/3/12 Mon 12/3/12
1.6 System GoLive 10 days Tue 12/4/12 Mon 12/17/12
1.6.1 Make system live across company 5 days Tue 12/4/12 Mon 12/10/12
1.6.2 Review and inspection of installation 3 days Tue 12/11/12 Thu 12/13/12
1.6.3 Fix any issues during installation 2 days Fri 12/14/12 Mon 12/17/12
1.6.4 Signoff 0 days Mon 12/17/12 Mon 12/17/12
1.7 User training and Demo 9 days Tue 12/18/12 Fri 12/28/12
1.7.1 Draft and provide installation documentation and user manuals 5 days Tue 12/18/12 Mon 12/24/12
1.7.2 System demo to all users - 1 2 days Tue 12/18/12 Wed 12/19/12
1.7.3 System demo to all users - 2 2 days Thu 12/20/12 Fri 12/21/12
1.7.4 Technical training to technical users 5 days Mon 12/24/12 Fri 12/28/12
1.7.5 Signoff from users 0 days Fri 12/28/12 Fri 12/28/12
1.8 Project Closure and Handover 5 days Mon 12/31/12 Fri 1/4/13
1.8.1 Prepare thank you note for all stakeholders 2 days Mon 12/31/12 Tue 1/1/13
1.8.2 Collect feedback from all users 3 days Mon 12/31/12 Wed 1/2/13
1.8.3 Conduct project closure meeting 1 day Thu 1/3/13 Thu 1/3/13
1.8.4 Handover system to maintenance team 1 day Fri 1/4/13 Fri 1/4/13
Project Milestones:
Milestone Name and Description: Completion Date
Project Kickoff April 30th
Requirements Signoff June 4th
Design Signoff June 19th
Development Complete October 9th
Testing Signoff December 3rd
UAT Signoff and Customer Accepted January 4th
Project Cost Management
The Work Breakdown structure file attached in scope management outlines the cost of the project under different tasks. Please refer to that stage for more details.The below tables shows that data.
WBS Task Name Cost
1 Customer Care Website Implementation $80,720.00
1.1 Project Initiation and Planning $7,360.00
1.1.1 Initial meeting with project sponsor $640.00
1.1.2 Identify user groups $1,920.00
1.1.3 Plan for resources and people required $1,600.00
1.1.4 Create annd Share project plan with team $1,600.00
1.1.5 Project Kickoff Meeting $1,600.00
1.2 Requirements Analysis $5,280.00
1.2.1 Requirements meeting with users $2,400.00
1.2.2 Requirements workshop $720.00
1.2.3 Document requirements and submit $1,200.00
1.2.4 Review of requirements $960.00
1.2.5 Requirements signoff $0.00
1.3 System Design $6,000.00
1.3.1 Logical design of system $2,400.00
1.3.2 Physical design of system $1,200.00
1.3.3 Validate and review design document $2,160.00
1.3.4 Discussion of design with team $240.00
1.3.5 Design approval and signoff $0.00
1.4 Coding and Development $34,000.00
1.4.1 Meeting for understanding and clarifying requirements $5,200.00
1.4.2 Coding and development $12,800.00
1.4.3 System testing $3,200.00
1.4.4 Code Integration and testing $7,200.00
1.4.5 Fix any errors found during testing $3,200.00
1.4.6 Review and inspection of fixes $2,400.00
1.4.7 Implementation sifnoff $0.00
1.5 User Acceptance Testing $17,920.00
1.5.1 Identidy test user groups and create test plan $960.00
1.5.2 Communicate test plan to test user groups $640.00
1.5.3 System demo to test users $480.00
1.5.4 User pilot phase 1 - 5 users $2,800.00
1.5.5 User pilot phase 2 - 100 users $11,200.00
1.5.6 Retrospective stage - for addressing user queries and fix issues $1,200.00
1.5.7 Take feedback from pilot users to incorporate in user training $640.00
1.5.8 User signoff on testing $0.00
1.6 System GoLive $3,360.00
1.6.1 Make system live across company $2,000.00
1.6.2 Review and inspection of installation $720.00
1.6.3 Fix any issues during installation $640.00
1.6.4 Signoff $0.00
1.7 User training and Demo $4,560.00
1.7.1 Draft and provide installation documentation and user manuals $1,200.00
1.7.2 System demo to all users - 1 $480.00
1.7.3 System demo to all users - 2 $480.00
1.7.4 Technical training to technical users $2,400.00
1.7.5 Signoff from users $0.00
1.8 Project Closure and Handover $2,240.00
1.8.1 Prepare thank you note for all stakeholders $640.00
1.8.2 Collect feedback from all users $960.00
1.8.3 Conduct project closure meeting $320.00
1.8.4 Handover system to maintenence team $320.00
Total $80,720.00
Project Quality Management
Project Deliverable Quality Requirements
The various deliverables from the project and the required quality from each are listed below
• Fully functional customer care website - Website implemented and live with less than 10 high priority defects
• Requirements specification document - Documentation as per UML standard covering functional and technical specification
• System design document - Technical documentation with detailed description of all functional and technical modules, with low level details present
• System testing and results - Details and report on all three stages of testing stages with list of defects, status and plan for addressing open defects
• User manuals - Detailed user manual signed off by customer
• Working code - Code as per company coding and web programming standards with complete compatibility
• End user training - Training and certification of all end users
Project Deliverable Quality Monitoring
There are multiple deliverables that would be produced at various stages of the project. To ensure that the deliverables meet the quality requirements, they would be focus on quality monitoring at every stage, right from project planning, to ensure that it is given the importance that it needs. There would be a testing and quality analyst who would be part of the project, who will track quality of requirements and working code and given immediate feedback that will help the development team to rectify any defects. There would be a lot of automated tools and trackers implemented to ensure that defects are captured, identified and addressed before the product is developed. Using these two approaches, information would be collected to track and monitor and ensure that the product is of very high quality.
Project Deliverable Quality Reporting
Quality reporting would be done at two levels, the first one would be on an ongoing basis as the project is progressing and the second one is when the project has been implemented and system and user testing is being done. The ongoing quality tracking would be reported as part of the project status reporting with the action items and resolutions also discussed and reported in the weekly status report. The quality reporting that would take place at the end of the project would be reported using quality tools and trackers where the quality and testing analyst would gather information from all stakeholders and track and update quality information and report it for everyone to see.
Project Deliverable Quality Discrepancy Decisions
It is understood that there could be many instances in the project when there is discrepancy in the quality of deliverables, and in these cases decisions have to be made on what has to be done, to ensure that overall objectives of the project are not compromised. The project manager and client would be the first point of decision makers when there is a discrepancy on quality. They would decide if the discrepancy is acceptable, if it can be rectified at a later stage in the project and then take a call if it has to be rectified at the same moment of if they can go ahead with the discrepancy. In cases where the discrepancy and loss of quality if much higher, then the project stakeholder would be involved to get an approval and decision on what has to be done.
Project Human Resource Management
Resource Analysis
Task ID Material Resources Work (Human) Resources
1.1.1 Customer Care Manager, Project Manager, Project Sponsor
1.1.2 Project Manager, Customer Care Manager
1.1.3 Project Manager
1.1.4 Project Manager
1.1.5 Projector, Meeting Room Project Manager, Customer Care Manager, Business Analyst, Project Sponsor, Software Architect, Software Developer - 1, Software Developer - 2, Software Tester
1.2.1 Computer with MS Office Business Analyst
1.2.2 Business Analyst
1.2.3 Business Analyst
1.2.4 Customer Care Manager, Project Sponsor
1.2.5 Customer Care Manager, Project Sponsor
1.3.1 Business Analyst, Software Architect
1.3.2 Software Architect
1.3.3 Business Analyst, Project Manager, Software Developer - 1
1.3.4 Software Architect
1.3.5 Project Sponsor
1.4.1 Projector, Meeting Room Business Analyst, Customer Care Manager, Software Developer - 1, Software Developer - 2, Software Tester
1.4.2 Software Licenses, Computer with MS Office Software Developer - 1, Software Developer - 2
1.4.3 Computer with MS Office Software Tester
1.4.4 Software Developer - 1, Software Developer - 2, Software Tester
1.4.5 Software Developer - 1, Software Developer - 2
1.4.6 Customer Care Manager, Software Tester
1.4.7 Customer Care Manager
1.5.1 Project Manager
1.5.2 Project Manager
1.5.3 Business Analyst
1.5.4 Project Manager, Business Analyst
1.5.5 Project Manager, Business Analyst
1.5.6 Business Analyst
1.5.7 Project Manager
1.5.8 Project Sponsor
1.6.1 Software Architect, Software Developer - 1
1.6.2 Software Architect
1.6.3 Software Developer - 1, Software Developer - 2
1.6.4 Software Architect
1.7.1 Business Analyst
1.7.2 Business Analyst
1.7.3 Business Analyst
1.7.4 Business Analyst, Software Architect
1.7.5 Project Sponsor
1.8.1 Project Manager
1.8.2 Project Manager
1.8.3 Project Manager
1.8.4 Project Manager
Resource(s) Doing the Most Work
As can be seen from the above section, the project has got well defined stages with resources of different skill sets working on respective tasks. In terms of resources with a lot of workload, the business analyst has a workload of 624 hours and the two software developers have workloads of 648 hours and 584 hours. These are three critical resources who would be assigned in a dedicated fashion and engaged throughout the project and who would be involved in the conceptualization, design and development of the website.
In terms of an action plan to manage risks and dependency on the above three key resources, it is suggested that the project have a buffer resource with analysis and development who would be able to take up tasks should the resources be overloaded or if they are not able to work on their tasks due to any reason. The reason why a new resource is required and work cannot be shared with other existing project team members is due to the specialized nature of work and knowledge of IT that is required to perform their tasks effectively.
Alternative Resource Assignments
The quality analyst or testing resource is one resource that can be outsourced to an independent QA contractor who would be able to perform these tasks effectively and efficiently. Another area that can be considered for alternative resource assignments is for the User Acceptance Testing stage where other employees in the customer care division or from other departments such as sales or servicing can be approach should these be issues in getting the required number of resources for user acceptance testing.
Resource Gap Analysis
In terms of resource gaps, towards the end of the project, there is a need for a resource for release management and deployment of the software. This resource is currently not available with the company, and as a stop gap arrangement the software developer and the systems architect would be taking care of this responsibility. Should there be a need for a dedicated release and deployment manager; the project would engage an independent contractor who would be able to fulfill this role.
Optimization:
What if… Potential trade-off decision
What is another business analyst was added to the project to bring down the duration This would increase project cost, but would help manage load on the other BA, help increase quality of project documentation and help stakeholders with faster clarifications that would lead to faster project delivery
What if the project is developed in stages rather than all together at once The system could be live faster with basic features and other features added at later stages. This would add about 20% to the project cost.
What if another developer is added to help the two developers who are working on the project This would help in faster delivery across tasks that would take the longest, and also reduce project risk if any one of the developers is unavailable. This would increase project cost.
What if there are daily project updates rather than only the weekly project review meeting This would help in better project communication and more response issue resolution. However, this would lead to more management and time for non-development activities and could lead to more time for development.
Communications Management
Project Team Communications
Effective, responsive and proactive communication would be one of the key enablers for the success of this project. The various types of communication methods that would be leveraged for this project is discussed below.
Name Description Frequency Method
Project Status Reports Status report that shows work that has been done last week and work planned for next week and overall status of project Weekly E-mail
Project Status Meeting Discussion on project status report and clarification of high priority issues Weekly Meeting
Executive Sponsor Review Review of project status and seeking of project related decisions and approvals Monthly Meeting
Issue Clarifications Clarification of project related issues with project stakeholders Ad-Hoc Meeting or E-mail
Project Dashboard Key project metrics and work being performed Weekly Online
Project Team Conflict Resolution
The project team conflict resolution escalation path is shown in the diagram below. It is encouraged that the project team members openly and freely communicate to resolve issues proactively and in a responsive manner. For any reason if any issues is not being resolved at the team level, it can be escalated to the second level, were the project manager would be making a decision in consultation with the customer care manager. Any disagreements at this level would be addressed with the project sponsor making the final decision.
Collecting and Communicating Project Status Information
Project Information to Monitor
• Tasks completed against schedule and delays if any
• Cost information and cost increases is any
• Change requests asking for extra features leading to scope creep
• Project issue register to monitor issue resolution
• Key milestone completion
How to Collect Project Information
The various information described in the above section needs to be collected on an ongoing basis, in a structured and formal manner, and also in an ad-hoc manner to ensure that correct, valid and updated information is collected. The various techniques and process that would be used to collect project information are listed below
• Asking people assigned to the task on task completion status
• Asking people assigned to task on tasks that are expected to start
• Going through the issues register, and from issue resolution meeting
• Asking for a weekly mail update on task completion from all project stakeholders
• Keeping a record of all the change requests that come in
Frequency for Project Information Collection
Cost information -To be collected weekly as part of project tracking
Task completion information - To be collected weekly as part of project tracking
Project Open Issues -Ad hoc to be entered on an ongoing basis
Change Requests -Ad hoc as per customer requests
Key milestone completion - To be collected weekly as part of project tracking
Project Status Information and Recipients
The recipients of the information include the project sponsor, project team members, business stakeholders and client. The specific data that would be presented to these recipients is listed below
• Project task completion and milestone completion - All project stakeholders
• Costs and summary information - Project sponsor
• Project issues - Project team members, business stakeholders
Plan and Take Adaptive Action
Methods to Analyze the Impact of the Status Information
The various information that is collected for the tasks and costs would be entered into MS Project to get a graphical view on project progress, and to see if the project is on track or of there are major issues that need attention. Earned Value Analysis would be done for the actual and planned schedule and costs to verify how the project is performing on these indicators.
The change requests that come in would be analyzed for their effort, and impact on the schedules and timelines of the project, so that an informed decision on the change request can be taken that would ensure project goals are not affected.
In addition to this, the various open issues that are raised for clarification would be measured against the time that is taking to resolve them and based on them they would be marked as red and escalated so that there is urgency to reso
USA 
India