Project Notification Form
Project Status and Control Report
Name of Project
PPMP XXXXXXXXXXAssessment 1
Part A
Project Status Report
(
Project
s
tatus
eport 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 sponso
steering committee. The report
is based on
Section 14.13 Status Reporting in
Kerzner (201
7
)
and Section XXXXXXXXXXin PMBoK
(2017)
.
Please complete the report for
the case study
provided
within the Assessments section
in Moodle.
All g
uidance boxes
,
including
this
one,
must
be deleted when you have
completed the report.
How to delete: P
osition the cursor on the borde
, left click when a cross
appears,
then
press delete
.
)Project Information
Project name: A
ief name to describe the project
Date: Date of the cu
ent 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.
(
Gantt Chart
This chart represents the original baseline plan for the project. The
shaded column between
June and July
is the cu
ent date
(30
th
June)
.
)Gantt Chart
WBS #
Task & Subtask
Months
Jan
Fe
Ma
Ap
May
Jun
Jul
Aug
Sep
Oct
1
A
———————
2
B
———————
2.1
B1
———
2.2
B2
——
3
C
—————
4
D
————————
5
E
—————————————
5.1
E1
—————
5.2
E2
——————
6
F
————————
6.1
F1
—————
6.2
F2
—
7
G
—
(
This table contains the Planned Value (PV), Earned Value (EV), and Actual Cost (AC) values. Calculate Schedule Performance Index (SPI = EV/PV) and Cost Performance Index (CPI = EV/AC) in percentages.
)Variance Analysis (cost in thousands)
Task & Subtask
Milestone Status
PV
EV
AC
Performance Index %
Schedule
Cost
A
Completed
50
50
50
B
Completed
100
100
125
B1
Completed
50
50
50
B2
Completed
50
50
75
C
Completed
80
80
70
D
Completed
50
50
55
E
In progress
140
80
220
E1
Completed
60
60
100
E2
In progress
80
20
120
F
Not started
100
0
0
F1
Not started
40
0
0
F2
Not started
60
0
0
G
Not started
10
0
0
Task Totals
(PMBoK, 2017, p.267)
(
E
stimate
A
t
C
ompletion (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 201
7
Table 7-1
Page 267
).
)Estimate at Completion (EAC)
(
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
C
hapter 11).
)Cost Summary
(
Forecast
c
ompletion
d
ate
is derived from the Schedule Performance Index (SPI) and forecasts the end date of the project
(see AS XXXXXXXXXXp
p
.13-
15
S
ection 2.3.2)
.
Calculate the forecast completion date
.
Al
so
s
tate whether re
-
aselining
of the project
is required and the impact.
)Forecast Completion Date
(
Milestones are
event
s
on a schedule which marks the
completion of a key activity
(Managing PRINCE2 (20
17
)
Page 113 & 155
)
.
)Milestone Report
Milestone Task
Scheduled Completion
Projected Completion
Actual Completion
Issues
A
B
C
D
E
F
G
(
M
ajor events that the stakeholders should be made aware of
are reported here (see
Guidance for Effective R
isk
M
anagement
in
Section 10.3
of
Managing PRINCE2 (20
17
)
.
) Exception (Issues) Report
Cu
ent Issue
Potential Impact
Co
ective Action
PPMP XXXXXXXXXXAssessment 1
Part B
(
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 achieved, 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 co
ective actions.
Controls are established and then activated either by an event occu
ing or a timeframe being met. Reports are generated
as a consequence
that then become
c
ontrollable items managed by the project team. These items are classified as
Deliverables,
Status
Reports
, Logs, and Issues
.
Communication between the project team and the project board or change management authority is made through the controls reports and authorisations or advice managed.
The report is based on the contents of:
Managing Successful Projects with PRINCE2
(2017),
A Guide to the Project Management Body of Knowledge (PMBOK Guide) 6
th
Edition
XXXXXXXXXXand
Kerzner H.,
Project Management: A Systems Approach to Planning, Scheduling and Controlling
(2017).
Please complete the report in the context of the case study provided within the Assessments section on the unit Moodle website.
)Project Controls Report
1. Project Information
Project name: A
ief name to describe the project
Date: Date of the cu
ent 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.
2. Controllable Categories
(
Managing PRINCE2
Chapter 11 and Appendix A identify that the following management products are used to establish and maintain the project’s controls for issues
,
changes
etc
. The lists of controllable categories consist of deliverables, project status
eports
, logs, and issue items.
Break each category down further according to the advice contained in
Managing PRINCE2
Chapter 11 and the
PMBOK Guide
Part 1 Chapter XXXXXXXXXXand each section in the
PMBOK Guide
that deals with Controls
from
c
hapter
4
to 13, for example 5.6 Control Scope, 6.7 Control Schedule, 7.4 Control Cost, etc.
Identify what those category items are for the project
(case study)
in the table below.
)
Controllable Category
Item Description
Applicable PMBOK Knowledge Area(s)
1.
Deliverables
1.1
1.2
1.3
2.
Status Reports
2.1
2.2
2.3
3.
Logs
3.1
3.2
3.3
3. (
Event
d
iven
c
ontrols are control mechanisms that are assigned to control items because 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 the 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
Section
2 above. Provide a short explanation of how your event driven control will affect the item.
)Event Driven Controls
Controllable Category
Item & Explanation
PMBOK Knowledge Area
Inputs
Tools & Techniques
Outputs
1. Deliverable
1.1
Explain how the control will affect this item.
1.2
Explain how the control will affect this item.
1.3
Explain how the control will affect this item.
2. Status Reports
2.1
Explain how the control will affect this item.
2.2
Explain how the control will affect this item.
2.3
Explain how the control will affect this item.
3. Logs
3.1
Explain how the control will affect this item.
3.2
Explain how the control will affect this item.
3.3
Explain how the control will affect this item.
4. Time Driven Items
(
Time
d
iven
c
ontrols 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
Section
2 above. Provide a short explanation of how your time driven control will affect the item.
)
Controllable Category
Item & Explanation
PMBOK Knowledge Area
Inputs
Tools & Techniques
Outputs
1. Status Reports
1.1
Explain how the control will affect this item.
1.2
Explain how the control will