Nocturnal Dialysis Conversion Project Status

PROJECT STATUS AND CONTROL REPORT
NAME OF PROJECT
PPMP20010- Assignment 1
Part A
Project Status Report
1 PROJECT INFORMATION
The Project Status Report is a tool used throughout the life of a project to supply
information on how the project is proceeding. The report is a vital communication tool
aimed at the sponsor/steering committee. The report is based on the Monthly Project
Report that Kerzner (2013) displays in figure 15-24 page 786.
Please complete the report for the case study (Nocturnal Dialysis Conversion Project)
provided within the Assessments section in the Moodle.
Guidance boxes like this should be deleted when you have finished with the contents: position the cursor on the
border, left click when a cross appears and press delete
Project name: A brief name to describe the project

Date: Date of the current status report
Project ownership: Area responsible for the project
Prepared by: Name and position
Distribution list: List of those receiving the report, their positions and role in
the project.
ENTER YOUR NAME WITH STUDENT ID PAGE 1

NAME OF PROJECT
2 GANTT CHART
Gantt Chart.
This chart represents the original baseline plan for the project. The shaded column between weeks 6 & 7 is the
current date.
WBS Task &

# Subtask 1 2 3 4 5 6 7 8 9 10
1 A ————
1.1 A1 —
1.2 A2 —
1.3 A3 —
2 B ————
3 C ————————
4 D ————————————
4.1 D1 —————
4.2 D2 ——————
5 E —————
6 F ——
7 G —
8 H —
3 VARIANCE ANALYSIS (COST IN THOUSANDS)
Variance Analysis.
The table contains the Planned Value (PV), Earned Value (EV), and Actual Cost (AC) values. Calculate
Schedule Variance (SV%) and Cost Variance (CV%) using formulas given in Australian Standards (see AS
4817-2006 pp.32).
Task & Milestone Variance %

Subtask Status PV EV AC Schedule Cost
A Completed 100 100 100
A1 Completed 25 25 25
B Completed 50 50 55
C Completed 50 50 40
D In progress 70 40 110
D1 Completed 30 30 50
D2 In progress 40 10 60
E Not started 90 0 0
F Not started 40 0 0
G Not started 50 0 0
H Not started 5 0 0
Task Totals 455 240 305

NAME OF PROJECT
4 ESTIMATE AT COMPLETION (EAC)
1 EAC.
The 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 2013 p224 Table 7-1).
EAC =
5 COST SUMMARY
Cost summary.
Summarise the impact of the costs on the project and whether there is a need to redefine the risks (see PMBOK
chapter 11).
6 S CURVE
S Curves
Please add S Curves for PV, EV & AC for the project.
7 FORECAST COMPLETION DATE

Forecast Completion Date
A Forecast Completion Date is derived from the Schedule Performance Index (SPI) and forecasts the end date
of the project (see AS 4817-2006 pp.13-15 section 2.3.2). State whether re-baselining is required and the
impact.
Forecast completion date =
8 MILESTONE REPORT
Milestone.
Milestones are an event on a schedule which marks the completion of a key activity (Managing PRINCE2 (2009)
p. 70-71).
Milestone Scheduled Projected Actual

Task Completion Completion Completion Issues
A
B
C
D
E
F
G
H

NAME OF PROJECT
9 EVENT REPORT
Event Report.
Current Problem Potential Impact Corrective Action
Major events that the stakeholders should be made aware of are reported here (see risk management
procedures 8.3.5 in Managing PRINCE2 (2009).

NAME OF PROJECT
Part B
Project Controls Report

The Project Controls Report is a tool used to explain to the stakeholders of a project how
the goals and objectives of the project will be met and important items or deliverables will
be captured, managed and not lost by the project. The report is a vital communication tool
that is used as the basis for anticipating and averting problems through the proper
corrective actions. Controls are established and then activated either by an event
occurring or a timeframe being met. Outputs are generated as a consequence that then
becomes controllable items managed by the project team. These items are classified as
deliverables, configuration items, project status accounts, daily logs, and issue items.
Communication between the project team and the project board or change authority is
made through the control outputs and authorisations or advice managed.
The report is based on the contents of Managing Successful Projects with PRINCE2
(2009), A Guide to the Project Management Body of Knowledge (PMBOK Guide) 5 th
Edition (2013) and Kerzner Project Management: A Systems Approach to Planning,
Scheduling and Controlling (2013).
Please complete the report for the case study (Nocturnal Dialysis Conversion Project)
provided within the Assessments section in the Moodle.
Guidance boxes like this should be deleted when you have finished with the contents: position the cursor on the
border, left click when a cross appears and press delete
10 PROJECT INFORMATION
Project name: A brief name to describe the project
Date: Date of the current status report
Project ownership: Area responsible for the project
Prepared by: Name and position
Distribution list: List of those receiving the report, their positions and role in
the project.

NAME OF PROJECT
11 CONTROLLABLE CATEGORIES
Controllable Categories.
Managing PRINCE2 page 92 identifies that the following management products are
used to establish and maintain the project’s controls for issues, changes and
configuration management. The lists of controllable categories consist of
deliverables, configuration items, project status accounts, daily logs, and issue
items. The PMBOK Guide deals with control in each of the Knowledge Area
chapters (4-13) according to the summary that is contained in section 3.6 Monitoring
and Controlling Process Group.
Break each category down further according to the advice contained in Managing
PRINCE2 chapter 9 and the PMBOK Guide chapter 4.4-4.5 and each section in the
PMBOK Guide that deals with control in chapters 5 to 13, i.e. 5.6 Control Scope, 6.7
Control Schedule, Control Cost, etc. …
Identify what those category items are for the project in the table below. Adjust by
adding extra rows or columns the table as required to show the items in each of the
category.
Delete this guidance box when you have finished with the contents.
Controllable Item Applicable PMBOK

Category Knowledge Area(s)
1. Deliverables 1.1
1.2
1.3
2. Configuration 2.1
2.2
2.3

NAME OF PROJECT
3. Status 3.1
accounts
3.2
3.3
4. Logs 4.1
4.2
4.3
5. Issues 5.1
5.2
5.3
12 CONFIGURATION PROCEDURAL OUTPUTS
Configuration Procedural Outputs.

Managing PRINCE2 page 94 identifies that there are typically five core activities
that manage deliverables, configuration management, planning, identification,
control, status accounting, verification and audit. Additional information about
configuration items can be found in the indexes of PRINCE2, the PMBOK, and
Kerzner in section 11.33.
Identify the procedural outputs for those procedures where each category item
corresponds to your table in section 2 above. You may wish to write a short answer
as a paragraph to explain what is required, rather than list each item. Adjust by
adding extra rows or columns or merging cells in the table as required to show the
items in each of the categories.

NAME OF PROJECT
Configuration Procedural Outputs

Item Configuration Coding Baseline Status Verification
Control Level System Used in Accounting and Audit
Used this Periodicity Review
project Period and
Level of
Detail
1.1
1.2
1.3
2.1
2.2
2.3
13 EVENT DRIVEN CONTROLS
Event Driven Controls.

Event Driven Controls are control mechanisms that are assigned to control items as a
consequence of events that occur within a project. The management of the events are
governed by taking inputs, applying tools and techniques and generating or updating
outputs. Each knowledge area in the PMBOK identifies a specific set of controls, some
of which may be event driven.
Identify the inputs, tools and techniques and outputs that apply to each event driven
controllable category item that you have identified in table 2 above. Provide a short
explanation of how your event driven control will affect the item.
PMBOK Knowledge Area

Controllable Item & Tool &
Category Explanation Input Technique Output
1. Deliverable 1.1
Write the explanation of the event driven control in this cell and
delete this text afterwards. You may use as many words as you
require but brevity and succinctness is preferable.
1.2
1.3
2.2

NAME OF PROJECT
2.3
3. Status 3.1
Accounts Write the explanation of the event driven control in this cell and
3.2
3.3
4. Logs 4.1
4.2
4.3
5. Issues 5.1
5.2
5.3
14 TIME DRIVEN ITEMS
Time Driven Controls.

Time Driven Controls are control mechanisms that are assigned to control items at set
times that occur within a project. The management of the time events are governed by
taking inputs, applying tools and techniques and generating or updating outputs. Each
knowledge area in the PMBOK identifies a specific set of controls, some of which may
be time driven.
Identify the inputs, tools and techniques and outputs that apply to each time driven
controllable category item that you have identified in table 2 above. Provide a short
explanation of how your time driven control will affect the item.
PMBOK Knowledge Area

NAME OF PROJECT
Controllable Item & Tool &

Category Explanation Input Technique Output
1. Deliverable 1.1
Write the explanation of the time driven control in this cell and delete
this text afterwards. You may use as many words as you require but
brevity and succinctness is preferable.
1.2
1.3
2.2
2.3
3. Status 3.1
Accounts Write the explanation of the time driven control in this cell and delete
3.2
3.3
4. Logs 4.1
4.2
4.3
5. Issues 5.1
5.2
5.3

NAME OF PROJECT

Nocturnal Dialysis Conversion Project Status

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Nocturnal Dialysis Conversion Project Status

Загружено:

Авторское право:

Доступные форматы

PROJECT STATUS AND CONTROL REPORT

Project Status Report

Project name: A brief name to describe the project

ENTER YOUR NAME WITH STUDENT ID PAGE 1

WBS Task &

3 VARIANCE ANALYSIS (COST IN THOUSANDS)

Task & Milestone Variance %

ENTER YOUR NAME WITH STUDENT ID PAGE 2

4 ESTIMATE AT COMPLETION (EAC)

7 FORECAST COMPLETION DATE

Forecast completion date =

Milestone Scheduled Projected Actual

ENTER YOUR NAME WITH STUDENT ID PAGE 3

ENTER YOUR NAME WITH STUDENT ID PAGE 4

Project Controls Report

ENTER YOUR NAME WITH STUDENT ID PAGE 5

Controllable Item Applicable PMBOK

ENTER YOUR NAME WITH STUDENT ID PAGE 6

12 CONFIGURATION PROCEDURAL OUTPUTS

Configuration Procedural Outputs.

ENTER YOUR NAME WITH STUDENT ID PAGE 7

Configuration Procedural Outputs

13 EVENT DRIVEN CONTROLS

Event Driven Controls.

PMBOK Knowledge Area

ENTER YOUR NAME WITH STUDENT ID PAGE 8

14 TIME DRIVEN ITEMS

Time Driven Controls.

PMBOK Knowledge Area

ENTER YOUR NAME WITH STUDENT ID PAGE 9

Controllable Item & Tool &

ENTER YOUR NAME WITH STUDENT ID PAGE 10

ENTER YOUR NAME WITH STUDENT ID PAGE 11

Вам также может понравиться