DOC-Module -7
DOC-Module -7
MODULE 7 NOTES
Project Management
CONTENTS
1. Introduction 3
2. Closing a project 3
3. Decommissioning a project 4
4. Identifying follow-on actions 5
5. Project evaluation review 5
6. Analysing project risks 7
7. Process of closing out 8
8. Wrap-up 9
DISCLAIMER: The information contained in this document is accurate at the time of printing. However, factors beyond Damelin’s control (such as environmental, regulatory, or technical changes) may cause the contents
of this document and/or of the programme to change. In the event of any such change, Damelin will attempt to formally notify current students. All possible measures will be taken to minimise inconvenience to students.
PROJECT MANAGEMENT | MODULE 7 NOTES | A SUCCESSFUL PROJECT IS ADMINISTRATIVELY CLOSED OUT
DAMELIN HET – Damelin (Pty) Ltd is registered with the Department of Higher Education and Training as a Private Higher Education Institution under the Higher Education Act No. 101 of 1997 and its higher education programmes are accredited by the
Council on Higher Education (CHE). Registration Number: 2001/HE07/009. DAMELIN FET – Damelin (Pty) Ltd is provisionally registered with the Department of Higher Education and Training as a private college under the Continuing Education and
© DAMELIN 2022 2
Training Act No. 16 of 2006. Registration Certificate No: 2008/FE07/089. Damelin (Pty) Ltd is also provisionally accredited by Umalusi, the Quality Council for General and Further Education and Training. Damelin (Pty) Ltd is further accredited by the
Quality Council for Trades and Occupations (QCTO).
PROJECT MANAGEMENT
1. INTRODUCTION
The purpose of the closing out process is to execute a controlled close to your project. The process covers
your task (as project manager) to wrap up your project, either at its end or premature close. Most of your work
is to prepare a report to your project board, to obtain its confirmation that your project may close.
The objectives of closing a project are, therefore, to:
• Check the extent to which your objectives or aims set out in your project initiation document (PID) have
been met
• Confirm the scope of the fulfilment of PID and your customer’s satisfaction
with the deliverables
• Obtain formal acceptance of your deliverables
• Confirm to what extent all expected products have been handed over and
accepted by your customer
• Confirm that maintenance and operation arrangements are in place (where appropriate)
• Make any recommendations for follow-on actions
• Capture lessons resulting from your project and complete the lessons learnt report
• Prepare an end-of-project report
• Notify your host organisation of the intention to disband your project
organisation and resources
2. CLOSING A PROJECT
In this stage, you must ensure that you bring the project to its proper closure. The closure phase is
characterised by a written formal project review report, containing the following components: a formal
acceptance of the final product by the client, and matching the initial requirements specified by your client
with the final delivered project. Included at this stage is the necessary rewarding of your team, a list of lessons
learnt, releasing project resources, and a formal project closure notification to higher management.
Your project must be closed down in an orderly and firm manner. The end of a project may arise when all the
planned work is complete, and the deliverables finished and signed off, as having met their stated quality
criteria. Alternatively, you can bring a project to a premature close because of changes to requirements,
removal of resources, or unacceptable slippage of time, effort or costs. Most of the work involved in this major
process is concerned with the preparation of information for your project board, to make the decision to close
the project, or not.
Rather like project initiation and stage initiation, this process provides a decision support structure; closing a
project aims to:
• Ensure that the objectives of your project have been met
• Confirm that your customer is satisfied with the outcome
• Obtain formal acceptance of your project products or deliverables
• Confirm that all products or deliverables have been handed over to the customer and that these have
been accepted
• Ensure that where ongoing support, enhancement, and maintenance is appropriate (and required), you
have made suitable provision
• Identify any recommendations for follow-on actions and document
• Capture “lessons learned” and publish these in a suitable report for your project board
• Prepare an “end project report” for sign-off by your project board; and
• Notify your customer, sponsor, or host organisation, as appropriate, of the intention to close your project,
disband your project organisation and release the resources
Obviously, it will be difficult to close down a project in an orderly manner, if the expectations and criteria for
completion and close-down have not been agreed at the outset, and this will normally have been done, and
the final acceptance criteria included within the project initiation document. Provide project staff and managers
with as much notice as possible for them to plan their return to normal operations. A ‘thanks’ to those parties
who have contributed to the project are also in order (Bradley, 2005).
3. DECOMMISSIONING A PROJECT
The main aim of this process is to bring the project to an orderly close, ensuring that your
customer is happy with the outcome and demonstrates this by providing a customer
acceptance sign-off.
Assurance that the outcome is supported and that a proper audit trail exists for your project documentation,
should it be needed in the future, must also be forthcoming.
Key features of this part of closing out a project are:
1. Check that all project issues have been addressed
2. Check that all products have been completed, documented and handed over
3. Confirm that your customer’s specification has been addressed
4. Confirm that the outcome can be supported, operationally
5. Archive all your project documentation mainly for audit purposes
6. Notify all concerned that your project is coming to a conclusion and that resources will be returned
This process is primarily your responsibility as the project manager, as it marks the conclusion of the work
performed, over what will often be, a considerable period. There will be a need for close contact between you
and project board members, to ensure that there are no surprises at the final meeting, where your project will
be formally closed (Bradley, 2005).
The follow-on recommendations will provide the basis for project mandates, for any future
projects which may arise from the recommendations made (Bradley, 2005).
This review addresses your project and its outcome, rather than the outcome itself, which will
be the subject of a post-project review.
The lessons learnt report (log) is a prime input to this process, along with the various logs needed to provide a
comprehensive view of the performance of your project.
The outputs are:
As a project manager, you have the responsibility to produce these analyses and will present them to your
project board (Bradley, 2005). Closing a project provides the “housework” tasks, to properly complete the
process. Your project board can only give authority for closure. The process is essential for an orderly and
effective shut down of the project.
You must be prepared to manage within the guidelines, policies, procedures, rules and directives of the parent
organisation. The production of the business must continue as normal, and uninterrupted. After all, this is where
the funds are generated. Remember that having one successful project does not mean a successful company,
or future projects, will be successful. It is especially true where success has come about through formal
authority and executive interference. A strong commitment to project management must exist.
It is assumed that direct costs increase linearly, as activity time is reduced from the normal time (NT). Cost to
crash is measured per period (one week) and is calculated as follows:
Where NT is normal time, NC is normal cost; CT is crash time and CC is crash cost.
Naturally, your objective is to minimise the cost. Determining the minimum project duration can be done
through using the crash periods of each activity for scheduling purposes, but costs might be prohibitive. The
minimum-cost schedule has to receive priority.
The minimum-cost schedule has to receive priority. There are three steps involved;
1. determine critical path
2. find activities on the critical path with lowest crash cost
3. reduce the time for this activity as much as possible
It might be that another path becomes critical due to the time reduction. Project managers have to be careful
that the cost of crashing does not exceed the benefit thereof. Repeat the steps until the increase in direct cost
is larger than the savings generated by shortening the project.
When calculating the probability for each activity, the analysis thereof will determine the likelihood of the entire
project being delivered on time. To do this, calculate the sum of the duration times and variances along the
critical path. Also, calculate a probability distribution for the critical path. The central limit theorem is applied.
It states that “the sum of a group of independent, identically distributed random variables,
approaches a normal distribution, as the number of variables increases” (Krajewski et al., 2016).
To analyse the probabilities of completing a project by a particular date, using the normal distribution, use the
following formula:
Where “T” is the due date for the project.
NORMAL DISTRIBUTION.
Step 1
The first step in the course of closing out is to get formal sign-off, from your customer. Analyse the project,
the risks mitigated and that success parameters are achieved. It has to be formally acknowledged by your
customer before you can consider the project as complete. Before the resources and teams are dispersed, the
customer must sign-off the closure.
Step 2
The next step in project closure is the final analysis of the product scope. It includes a measurement of the
scope, achieved from the original project plan.
Step 3
Once sign-off has been obtained from your customer, and the scope measured against your original
specifications and scope, your resources can be released. These resources can be absorbed back into
the organisation or moved to another project. Part of releasing the resources is to close all contractual
arrangements and notify all sub-contractors.
Step 4
Project files have to be indexed and given to key stakeholders. Together with the file, compile a “lessons learnt”
document. Such a document will be of value in future projects. Use the lessons learnt document to avoid
duplication during follow-up projects. It should contain all changes requested during the project, corrective
actions taken, and the best methodologies developed.
Step 5
At the closure of a project, debrief project team members, and obtain input about their perception of the
project. Input from your team members could provide valuable feedback included in the lessons learnt
document. Reward team members adequately for contributions made and should leave the project feeling
fulfilled and fairly treated.
8. WRAP-UP
A project is an interrelated set of activities, with a definite starting and ending point, which can be complex and
challenging. The objective is to break the complexity into smaller, simpler tasks to be executed efficiently until
the sum of all the tasks completes the project. A project will typically require a multi-disciplinary team as it will
usually permeate every department in an organisation. The goal is to finish the project according to customer
specifications, within budget, and on time, meeting the deadline.
Various resources are allocated to achieve successful closure of the project. These include human resources,
funds, plant and equipment, and materials. The structure of the business will determine your relationship with
your team. There are three structures considered; pure project, functional and matrix, which is a combination
of the first two. Like with the product or company lifecycle, a project is completed in phases, and a lifecycle
applies. The project lifecycle also consists of four phases, namely initiation, planning, execution, and closure.
Conduct scheduling through the work breakdown structure (WBS), which is a statement of all activities that
will, collectively, complete the project. It is important that every single activity required is in the WBS. Major
work components are broken down into smaller units. Upon the road to closure, a network diagram can be
used to depict the project process and to show the interrelated activities visually. It is done to enable you to
identify and organise the interrelationships between activities. It also provides a forum for managers of different
functional areas, to discuss the nature of the various activities and resources required. It allows for a clearer
understanding of completion time and shows priority activities and possible delays that could occur.
The success of a project is measured through the completion of your project within the constraints of time,
cost and performance. These parameters have been expanded to include acceptance of the customer,
minimum scope changes, production of the company undisturbed, and leaving the corporate culture
unchanged. The time-span of the project is determined by the critical path which is the longest path of the
project. The earliest starting time and finishing time, and the latest starting time and finishing time, must be
calculated, to manage the execution of the project according to timelines.
Where required, your project can be crashed or expedited through various techniques, such as double shifts,
additional workers or extra equipment. Justify the cost of crashing through the cost saving on finishing earlier
and avoiding penalty costs. The objective is to complete the project at minimum cost within the deadline, and
according to customer requirements. To achieve the objectives, risks have to be analysed and managed. A
risk-management plan is drawn up through the examination of four categories, namely strategic fit, product
attributes, team capabilities, and operations. Tools and techniques used for risk assessment are a simulation,
statistical analysis, and analysing probabilities.