Reference no: EM133063260
PPMP20010 Executing and Closing Projects - Central Queensland University
Project Status and Exception Reports
Based on the real-life case study
Part 1 - Project Status Report using EVA
Project status reporting is the act of collecting, analysing, and distributing project information. Project information is distributed to many groups of stakeholders and should be adapted to provide information at an appropriate level, format, and detail for each type of stakeholder (PMBOK Guide, 2017, Section 10.2.2.5). Project status reports are time-based reports.
Case Study (Project) - Queensland health payroll system
WBS Codes Main Tasks & Sub-Tasks
1 Project Initiation
1.1 Business case& project procedures
1.2 Business Requirements, technical requirements & solution scope
2 Project realization blueprint
2.1 Project management plan
2.2 Organizational change management
2.3 Develop system environment set-up
3 Execution
3.1 System configuration
3.2 System development
3.3 Integration testing & quality check
4 Final Preparation
4.1 Testing & quality check (i.e. User Acceptance Test)
4.2 Training
5 Go Live & support
5.1 Production support
5.2 Project End
5.3 Project Documentation
2 GANTT CHART
This chart represents the original baseline plan for the project. The vertical shaded column between May.2008and Jun. 2008 is the current date (31stMay2008) for the status report.
3 VARIANCE ANALYSIS
This table contains the Planned Value (PV), Earned Value (EV), and Actual Cost (AC) values. Costs given in the table below are fictitious and in millions of dollars for assignment purpose ONLY.
Calculate Schedule Performance Index (SPI = EV/PV) and Cost Performance Index (CPI = EV/AC) in percentages (%) for each main task and their sub-tasks. Also calculate overall CPI and SPI as of 31stMay2008and interpret these values in terms of project status (cost-wise and schedule-wise) on 31st May 2008.
Calculate overall SPI &CPI here and comment on the status of the project (cost and schedule wise) as of 31st May 2008. As per the Gantt chart above, add PVs till 31st May 2008 only.
4 ESTIMATE AT COMPLETION (EAC)
Estimate at Completion (EAC) is the expected total cost of the completing all work expressed as the sum of the actual costs to date and the estimate to complete (see PMBOK 2017 Table 7-1 Page 267).
Calculate EAC and interpret the result in terms of cost-overruns etc. Please mention whether re-baselining of the project is required and the impact on project cost. Provide discussion and support your arguments with evidence from the given data.
Provide the calculations and your commentary here
5 TO-COMPLETE PERFORMANCE INDEX (TCPI)
TCPI is a measure of cost performance that is required to be achieved with the remaining resources in order to meet specified management goals.TCPI is expressed as a ratio of the cost to finish outstanding work to the remaining budget (see PMBOK 2017 Table 7-13 and section 7.4.2.3).
Calculate TCPI and provide your commentarybased on TCPI value.
Provide the calculations and your commentary here
6 COST SUMMARY
Summarise the impact of the costs on the project tasks and explain if there is a need to re-define the risks (see PMBOK 2017 Chapter 11).
Provide commentary (i.e. over/underbudget) on every task listed in Section 1 above including re-fining any risks (you can make assumptions about the risks related the case study).
Provide commentaryabout here
7 FORECAST COMPLETION DATE
Even though a more accurate forecast completion date is derived from the updated schedule, the forecast duration could also be derived from the Schedule Performance Index (SPI) and can help forecasts the end date of the project (see AS 4817-2006 pp.13-15 Section 2.3.2).
Calculate the forecast completion date of the case study (project) using the overall SPI calculated in Section 3 above.
State whether re-baselining of the project is required and the impact on the project schedule.
8 MILESTONE REPORT
Milestones are events on a schedule which marks the completion of a key activity (Managing PRINCE2 (2017) Page 113 & 155).
Describe issues (if any) for the cost-overruns and schedule-delays for the tasks listed in Section 1 above and based on the data provided in Section 3 above.
Part 2 - Project Exception Report
1. PROJECT INFORMATION
An exception report is produced when a stage plan or project plan is forecast to exceed tolerance levels set. It is prepared by the project manager to inform the project board or the executive committee of the situation, and to offer options and recommendations for the way to proceed. (Managing Successful Projects with PRINCE2, 2017, Section A.10).
An exception report is event driven and is compiled by the project manager as soon as tolerances are to be exceeded. This report is to follow the PRINCE2 (2017) format for the exception reports, as described in Appendix A.10.
Please find a real issue (cost-overrun, behind-schedule etc.) from the case study (Queensland health payroll system) provided on Moodle and complete thisexception report template.
2. ESTABLISH THE NEED FOR AN EXCEPTION REPORT
Provide the motivation to compile and raise the exception report to the project board along with appropriate reasons for your decision.
3. EXCEPTION REPORT
Complete the report with all relevant and necessary information as per Appendix A.10 in the Managing Successful with RINCE2 (2017). Carefully study the derivation (inputs), format and presentation and quality criteria sections in Appendix A.10.
Describe the possible consequences in the context of the case study(project), its stakeholders'expectations, and challenges.
3.1 Exception title
An overview of the cost-overrun or behind-scheduleor an other exception being reported
3.2 Causes of the exception A description of the causes of a deviation from the current plan
3.3 Consequences of the deviation What the implications are if the deviation is not addressed for:
3.3.1the project
3.3.2the corporate, programme managementand the customer
3.4 Available Options
What 2-3 options are available to address the deviation (exception) and the effect of each option on the business case, risks, and tolerances.
3.5 Recommendation
Of the available options, which one is recommended, and why?
3.6 Lessons
What lessons can be learnt from this exception which might potentially be beneficial for this project or future project?
Note: Assessment 1 need to be done
Attachment:- Executing and Closing Projects.rar