Report Details
Date of Checkpoint
Period Covered
8/2/23 + 8 days = 20/2/23
When the tech hub went live, we knew that there
were errors that took 8 days to fix; they passed)
9 Jan 2023 – 20 Feb 2023
Cabling delay – Tech hub delay
Document details
Version
Modifications
1
Author
Panagiot Mechilli
Date
20/2/23
Date of checkpoint
report
Approvals
This document requires the following approvals:
Name
Imran Hussain
COPY FROM
PID
<<copy from
PID>>
<<copy from
PID>>
Role
Council leader
Signature
Date
23/2/23
Next day (check
if weekend)
Version
1
<<copy from PID>>
<<copy from
PID>>
<<copy from
PID>>
<<copy from PID>>
<<copy
from PID>>
<<copy
from PID>>
<<copy from PID>>
Distribution
This document has been distributed to:
Name
Role
<<copy from PID>>
Date of
Issue
24/2/23
Version
Name
1
Kia Hails
Kia Hails
Senior Software
Engineer
Arian Malkine
Junior Software
Engineer
24/2/23
1
Arian Malkine
Emily Newell
App Developer
24/2/23
1
Emily Newell
Sophia Hurrell
Senior Network
Engineer
24/2/23
1
Sophia Hurrell
<<copy from
PID>>
<<copy from
PID>>
<<copy from PID>>
<<copy from
PID>>
<<copy from
PID>>
<<copy from
PID>>
<<copy from
PID>>
<<copy from
PID>>
<<copy from
PID>>
<<copy from PID>>
Products
Product Name
Cabling – network
infrastructure
Work Undertaken
Waited until cabling was
delivered four days later
Date Complete
6 February 2023
Could not install and configure
technical hub software
13 February 2023
In the issues
No time  Say it was just
delayed
Installing and configuring
technical hub software
Can assign task to someone else
Network
immediately shut down
and updated the scripts.
(Same date as
before because
someone else
could do it)
20 February 2023
Project Management Control (in PID)
I will provide confidence to stakeholders that I have adequate control
over the project’s outcomes and can respond effectively to change by:
Skills:
-
Time scheduling (Gantt chart)
Cost planning (Cost plan)
Resourcing (Resources list)
Risk management (Risk management plan)
Communication planning (Communications plan)
Document this in a Project Initiation Document (PID)
BECOMES
By:
-
Planning the project scheduling using a Gantt chart
Costing the project accurately and to budget using a cost plan
Resourcing the tasks efficiently and accurately using a resources list
Managing risk with a Risk Management Plan that identifies risks,
assesses each risk’s probability and severity, and mitigation methods
for each risk.
Communication planning to ensure timely and clear communication
between stakeholders using a communication plan
I will document this in a Project Initiation Document (PID) that will be approved
by the client and sponsor and distributed to the project team.
Quality Management
I provided confidence to stakeholders that I had adequate control over the
project’s outcomes and could respond effectively to change by:
-
Planning the project scheduling using a Gantt chart
Costing the project accurately and to budget using a cost plan
Resourcing the tasks efficiently and accurately using a resources list
Managing risk with a Risk Management Plan that identifies risks,
assesses each risk’s probability and severity, and mitigation methods
for each risk.
Communication planning to ensure timely and clear communication
between stakeholders using a communication plan.
I documented this in a Project Initiation Document (PID) that was approved by
the client and sponsor and distributed to the project team.
Just copy the Project Management Control section from PID and make it
past tense.
Work Package Tolerance Status
Time:
- 4 days for delay of networking (does not affect schedule)
- 10 days for illness
- 8 days for additional scripts
Due to delays and issues the project has now delayed by 16 days.
Cost:
Quality:
Add up delays in days, only what actually affected the time
scheduling
Put the actual dates from Gantt Chart
Due to the delays, the team members were paid for these extra
days at a cost of £5504
Actions were taken to ensure the quality of the deliverables met
the client’s requirements.
What aktions
Issues log
Date Raised
Raised By
9/1/23
Sarah Bailey –
Senior
Network
Engineer
23/1/23
Absent team
member
called
beforehand
8/2/23
First day of
Description
Delivery of the
cabling was delayed
by four days.
Panagiot
Mehilli Project
Manager
The Senior Software
Engineer became ill
and was off during
the second and third
week of the project.
Emily Newell
– App
developer
Security issues arose
after the network
went live
Action Taken
Installing network
infrastructure had
to be delayed for 4
days.
[TASK] had to be
delayed for [x]
days
Assigned the
installation of
technical hub
software to XXXX
Date Closed
13/1/23
this required an
immediate shut down
and updating of the
20 February
2023
Can ignore
weekend days
24 January 2023
Assigned to
someone else,
so closed the
next day
testing
Anyone who
did the task
scripts.
Lessons Learned as Project Manager, refer back to Part A ( not needed?)
Talk about: (use these words)
-
Comms planning
Risk management
Scheduling
Cost
2 positives, 2 negatives
How do I find the lessons learned:
1) Issues log, how to prevent future issues of the same type from happening
Issue 1: cabling delay
-
I learned that there should be more contingency time in a
project schedule (Gantt chart) so that if a project resource is
unavailable for any reason, the project completion is not
delayed.
(Contingency Time)
-
I learned that I should have backup resources so they can take
on the role if something happens to the original resource,
should they be unavailable for any reason.
-
I learned that it is important to have a contract with suppliers
in case that the equipment is not delivered on time, that there
are consequences for the supplier. For example, compensation.
(reference from suppliers, reviews of previous projects)
-
I learned that the supplier used for the network infrastructure
was not reliable, and we will not continue to use them in future
projects.
-
I learned that the resource allocated to security, Arian Malkin,
did not have the necessary skills to ensure that the security of
the network was adequate. (e.g. meeting security standards of
CIA – confidentiality, integrity and availability, access control is
correct). And in future projects, I should train resources in
advance.
-
I learned that the resource allocated to security, Arian Malkin,
did not have enough time needed to complete the security
-
tasks to the required standard, and in future projects, I will
ensure that Function Point
I learned that the resource allocated to security, Arian Malkin,
did not have the necessary support during the project needed,
and in future projects, I will ensure that my communications
plan has more frequent communication opportunities with key
resources during vital tasks so that if issues arise, they can be
dealt with more promptly.
Positive lessons learned – Look at PID, risks that did not come up
Scheduling
- A lesson that I learned that if I could plan contingency time
into my project schedule, then issues that arose that caused
delays in the completion of tasks during the project, did not
delay the final handover of the project. I will ensure that I plan
in contingency time for expected, but also unexpected events.
Comms plan
- A lesson that I learned was that when communications
between stakeholders are planned in advance and occurs at the
necessary frequency,
as I did in my communications plans, then events such as staff
illness are flagged immediately and can be dealt with quickly
and effectively. This ensures that the project stays on task.
-
-
A lesson that I learned was that when I accurately and
efficiently cost and resource project with a contingency budget
(for situations whether the project accrues additional costs due
to additional resourcing or equipment costs).
Iron triangle