PRM202B Study Guide 1 2021 Final
PRM202B Study Guide 1 2021 Final
Project Management 2
(PRM202B)
This module forms a compulsory core module for the following undergraduate academic
programme:
Module Purpose:.............................................................................................................. 10
Section 1: Defining Scope, Quality, Responsibility and Activity Sequence and Developing
the Schedule. ................................................................................................................... 94
Section 2: Resource Utilisation, Determining Costs, Budget and Earned Value ........... 118
Study Unit 4: Managing Risk and Closing the Project .................................................... 145
Study Unit 5 – The Project Manager and the Project Team ........................................ 165
Word of Welcome
“Operations keeps the lights on, strategy provides a light at the end of the tunnel, but
project management is the train engine that moves the organisation forward.”
- Joy Gumz
Project management is the art of managing all the aspects of a project from inception to
closure using a scientific and structured methodology. The term project may be used to define
any endeavour that is temporary in nature and with a beginning or an end. The project must
create something unique whether it is a product, service or result and must be progressively
elaborated. As the definition implies, not every task can be considered a project. It would be
worthwhile to keep this definition in mind when categorising projects and studying their role
in the success of the organisation. With the above definition of the project, one gets a clear
idea of what a project is.
The purpose of the module Project Management 2 is to assist students to be able to plan and
implement projects successfully. Students must be able to foresee or predict as many dangers
and problems regarding a project as possible, and to plan, organise and control activities so
that the project is completed as successfully as possible in spite of all the risks. The ever-
present element of risk and uncertainty means that events and tasks leading to completion
can never be foretold with absolute accuracy.
Programme Purpose
The purpose of this qualification is to provide candidates in the private, public and voluntary
sectors with comprehensive and in-depth knowledge of the principles, major theories, and
paradigms, skills, methods and technology of the science and profession of the field of
marketing, management, supply chain and project management. This, in order to:
Module Purpose:
To assist the student in acquiring a comprehensive and interrelated understanding of project
management theories and practices.
Module outcomes:
The IMM Graduate School has designed student pacers for each module. These pacers will
assist you in planning your studies to ensure you cover the entire syllabus and to schedule
your studies at manageable intervals. Distance learning requires careful planning and
scheduling of your studies and the student pacer will provide you with a guideline on how to
plan and not fall behind. Adhering to the student pacer will guide you and provide you with a
good start to achieve the targets set out for each module and to ensure you plan beforehand
to hand in your assignments before or on the due date and to ensure you have sufficient time
to study for your examination.
“First, have a definite, clear practical ideal; a goal, an objective. Second, have the necessary
means to achieve your ends; wisdom, money, materials, and methods. Third, adjust all your
means to that end.” ~ Aristotle
You are registered for this module on a distance learning basis and you are expected to work
on your own 70% of the time. However, this does not mean that you are completely on your
own. Please use the available IMM Graduate School Student Support resources to help you
during your studies.
The IMM Graduate School is committed to assisting students with all queries, and have
introduced [email protected], to answer all general queries. This is supported by a
NB: Please ensure that all module specific questions and queries are still posted on the
module specific discussion forums, available on eLearn. Do not leave your queries to the last
day before you write your examination or before the assignment submission due dates.
You are required to regularly visit eLearn as it is an essential source of information that is
continuously updated with topical material, additional guidance, messages and tutorial
letters.
• eLibrary is an excellent place for you to read additional material on your own. This tool
will be extremely valuable when conducting research for your assignments / projects /
research reports. For access to the virtual library, please follow the instructions
available on eLearn.
• Information Centres - the IMM Graduate School has libraries in all Student Support
Centres with textbooks and additional materials that could help you in your assignments
when you need to reference additional sources. For opening times at facilities please
enquire at your Student Support Centre. You have access to free Internet at the
Information Centre.
• eMasterclasses - in our on-going efforts to support our students, the IMM Graduate
School hosts online tutorials in all our modules for additional guidance and support.
Subject matter experts share their knowledge through the use of a presentation or
video conferencing addressing learning outcomes, assignment and examination
preparation, etc., giving ample opportunity for student feedback and interaction.
• eDiscussion – join group forums for discussions, to post questions and to receive
updates on specific modules.
The Journal of Strategic Marketing - the official publication of the IMM Institute of Marketing
Management, which keeps you up-to-date with the latest news and trends of what is
At this point, you should understand the learning process explained above, as well as what
Project Management 2 (PRM202B) is all about and you should be ready to start your journey
towards the successful completion of your module.
The starting point in discussing how projects should be properly managed is to first
understand what a project is and, just as importantly, what it is not.
People have been undertaking projects since the earliest days of organised human activity.
The hunting parties of our prehistoric ancestors were projects, for example, they were
temporary undertakings directed at the goal of obtaining meat for the community. Large
complex projects have also been with us for a long time. The pyramids and the Great Wall of
China were in their day of roughly the same dimensions as the Apollo project to send men to
the moon. We use the term ‘project’ frequently in our daily conversations. A husband, for
example, may tell his wife, “My main project for this weekend is to straighten out the garage.”
Going hunting, building pyramids, and fixing faucets all share certain features that make the
projects.
The relevance of a project is measured by how well the project outcomes meet the priorities
of the target group. The efficiency of a project is measured by assessing the extent to which
resources have been used cost-effectively to achieve the desired results. The project’s
effectiveness is the extent to which the project objectives are met. The sustainability of the
project and its impact on the target group are examined during the evaluation. These
measures are in addition to the traditional project success criteria measures of objectives,
time and budget.
“Being a project manager is like being an artist, you have the different coloured process
streams combining into a work of art.”
-– Greg Cimmarrusti
-– Rory Burke
“Project management is like juggling three balls – time, cost and quality. Programme
management is like a troupe of circus performers standing in a circle, each juggling-three
balls and swapping balls from time to time.”
— G. Reiss
“Project management is the art of creating the illusion that any outcome is the result of a
series of predetermined, deliberate acts when, in fact, it was dumb luck.”
– Harold Kerzner
“Project managers function as bandleaders who pull together their players each a specialist
with individual score and internal rhythm. Under the leader’s direction, they all respond to
the same beat.”
— L.R. Sayles
-– Cornelius Fichtner
After completing this study unit, you should know the following:
• Define a project, project management.
• Identify project attributes, stakeholders, elements of the project management process
and balance project constraints.
• Explain the project life cycle
• Discuss the role of the PMI, implications of global project management and the benefits
of project management.
A detailed glossary can be found at the end of the prescribed textbook. In the table below,
some of the most used concepts are explained.
The key customer who has the requirements for the project
Client (or project sponsor) initiates the project, accepts the project and will pay for the
project.
Terminating a phase or The process to formally end the work. Closing of the project
project and final hand-over to the client.
A project has distinctive attributes that distinguish it from ongoing work or business
operations. Projects are temporary in nature. They are not an everyday business process and
Projects exist to bring about a product or service that hasn’t existed before. In this sense, a
project is unique. Unique means that this is new; this has never been done before. Maybe it’s
been done in a very similar fashion before but never exactly in this way. For example, Ford
Motor Company is in the business of designing and assembling cars. Each model that Ford
designs and produces can be considered a project. The models differ from each other in their
features and are marketed to people with various needs. An SUV serves a different purpose
and clientele than a luxury car. The design and marketing, of these two models, are unique
projects. However, the actual assembly of the cars is considered an operation (i.e., a
repetitive process that is followed for most makes and models).
In contrast with projects, operations are ongoing and repetitive. They involve work that is
continuous without an ending date and with the same processes repeated to produce the
same results. The purpose of operations is to keep the organisation functioning while the
purpose of a project is to meet its goals and conclude. Therefore, operations are ongoing
while projects are unique and temporary.
A project is completed when its goals and objectives are accomplished. It is these goals that
drive the project, and all the planning and implementation efforts undertaken to achieve
them. Sometimes projects end when it is determined that the goals and objectives cannot be
accomplished or when the product or service of the project is no longer needed and the
project is cancelled.
• Cost is the budget approved for the project including all necessary expenses needed to
deliver the project. Within organisations, project managers have to balance between
not running out of money and not underspending because many projects receive funds
or grants that have contract clauses with a ‘use it or lose it’ approach to project funds.
Poorly executed budget plans can result in a last-minute rush to spend the allocated
funds. For virtually all projects, the cost is ultimately a limiting constraint; few projects
can go over budget without eventually requiring corrective action.
• The scope is what the project is trying to achieve. It entails all the work involved in
delivering the project outcomes and the processes used to produce them. It is the
reason and the purpose of the project.
• Quality is a combination of the standards and criteria to which the project’s products
must be delivered for them to perform effectively. The product must perform to provide
the functionality expected, solve the identified problem, and deliver the benefit and
value expected. It must also meet other performance requirements, or service levels,
such as availability, reliability, and maintainability, and have acceptable finish and
polish. Quality on a project is controlled through quality assurance (QA), which is the
process of evaluating overall project performance on a regular basis to provide
confidence that the project will satisfy the relevant quality standards.
• Risk is defined by potential external events that will have a negative impact on your
project if they occur. Risk refers to the combination of the probability the event will
occur and the impact on the project if the event occurs. If the combination of the
probability of the occurrence and the impact on the project is too high, you should
identify the potential event as a risk and put a proactive plan in place to manage the
risk.
• Resources are required to carry out the project tasks. They can be people, equipment,
facilities, funding, or anything else capable of definition (usually other than labour)
required for the completion of a project activity.
You may have heard of the term ‘triple constraint’, which traditionally consisted of only time,
cost and scope. These are the primary competing project constraints that you have to be most
aware of. The triple constraint is illustrated in the form of a triangle to visualise the project
work and see the relationship between the scope/quality, schedule/time, and
cost/resource. In this triangle, each side represents one of the constraints (or related
constraints) wherein any changes to any one side cause changes in the other sides. The best
projects have a perfectly balanced triangle. Maintaining this balance is difficult because
projects are prone to change. For example, if scope increases, cost and time may increase
disproportionately. Alternatively, if the amount of money you have for your project
decreases, you may be able to do as much, but your time may increase.
The constraints are all dependent on each other. Think of all of these constraints as the classic
carnival game of Whac-A-Mole. Each time you try to push one mole back in the hole, another
one pops out. The best advice is to rely on your project team to keep these moles in place.
Figure 2 Whac-A-Mole
Here is an example of a project that cut quality because the project costs were fixed. The P-
36 oil platform was the largest footing production platform in the world capable of processing
180,000 barrels of oil per day and 5.2 million cubic metres of gas per day. Located in the
Roncador Field, Campos Basin, Brazil, the P-36 was operated by Petrobras.
In March 2001, the P-36 was producing around 84,000 barrels of oil and 1.3 million cubic
meters of gas per day when it became destabilised by two explosions and subsequently sank
in 3,900 feet of water with 1,650 short tons of crude oil remaining onboard, killing 11 people.
The sinking is attributed to a complete failure in quality assurance, and pressure for increased
production led to corners being cut on safety procedures. It is listed as one of the most
expensive accidents with a price tag of $515,000,000.
The following quotes are from a Petrobras executive, citing the benefits of cutting quality
assurance and inspection costs on the project.
• “Petrobras has established new global benchmarks for the generation of exceptional
shareholder wealth through an aggressive and innovative programme of cost-cutting on
its P36 production facility.”
• “Conventional constraints have been successfully challenged and replaced with new
paradigms appropriate to the globalised corporate marketplace.”
• “Elimination of these unnecessary straitjackets has empowered the project’s suppliers
and contractors to propose highly economical solutions, with the win-win bonus of
enhanced profitability margins for themselves.”
• “The P36 platform shows the shape of things to come in the unregulated global market
economy of the 21st century.”
You’ve determined that you have a project. What now? The notes you scribbled down on the
back of the napkin at lunch are a start, but not exactly good project management practice.
Too often, organisations follow Nike’s advice when it comes to managing projects when they
“just do it.” An assignment is made, and the project team members jump directly into the
development of the product or service requested. In the end, the delivered product doesn’t
meet the expectations of the customer. Unfortunately, many projects follow this poorly
When are companies going to stop wasting billions of rands on failed projects? The vast
majority of this waste is completely avoidable: simply get the right business needs
(requirements) understood early in the process and ensure that project management
techniques are applied and followed, and the project activities are monitored.
Applying good project management discipline is a way to help reduce the risks. Having good
project management skills does not completely eliminate problems, risks or surprises. The
value of good project management is that you have standard processes in place to deal with
all contingencies.
Project management is the application of knowledge, skills, tools and techniques applied to
project activities in order to meet the project requirements. Project management is a process
that includes planning, putting the project plan into action, and measuring progress and
performance.
Managing a project includes identifying your project’s requirements and writing down what
everyone needs from the project. What are the objectives of your project? When everyone
understands the goal, it’s much easier to keep them all on the right path. Make sure you set
goals that everyone agrees on to avoid team conflicts later on. Understanding and addressing
the needs of everyone affected by the project means the end result of your project is far more
likely to satisfy your stakeholders. Last but not least, as project manager, you will also be
balancing the many competing project constraints.
• Primary stakeholders are the people or groups that stand to be directly affected,
either positively or negatively, by an effort or the actions of an agency, institution,
or organisation. In some cases, there are primary stakeholders on both sides of
the equation: a regulation that benefits one group may have a negative effect on
another. A rent control policy, for example, benefits tenants but may hurt
landlords.
• Secondary stakeholders are people or groups that are indirectly affected, either
positively or negatively, by an effort or the actions of an agency, institution or
organisation. A programme to reduce domestic violence, for instance, could have
a positive effect on emergency room personnel by reducing the number of cases
they see. It might require more training for police to help them handle domestic
violence calls in a different way. Both of these groups would be secondary
stakeholders.
• Key stakeholders, who might belong to either or neither of the first two groups,
are those who can have a positive or negative effect on an effort, or who are
important within or to an organisation, agency or institution engaged in an
effort. The director of an organisation might be an obvious key stakeholder, but
so might the line staff – those who work directly with participants – who carry out
the work of the effort. If they don’t believe in what they’re doing or don’t do it
well, it might as well not have begun. Other examples of key stakeholders might
be funders, elected or appointed government officials, heads of businesses, or
Primary stakeholders
Beneficiaries or targets of the effort.
Beneficiaries are those who stand to gain something – services, skills, money, goods,
social connection, etc. – as a direct result of the effort. Targets are those who may or
Secondary stakeholders
Those directly involved with or responsible for beneficiaries or targets of the effort
These might include individuals and organisations that live with, are close to, or care for
the people in question, and those that offer services directly to them. Among these you
might find:
• Parents, spouses, siblings, children, other family members, significant others,
friends.
• Schools and their employees – teachers, counsellors, aides, etc.
• Doctors and other medical professionals, particularly primary care providers.
• Social workers and psychotherapists.
• Health and human service organisations and their line staff – youth workers,
welfare caseworkers, etc.
• Community volunteers in various capacities, from drivers to volunteer instructors
in training programs to those who staff food pantries and soup kitchens.
In short, in most cases, the earlier in the process stakeholders can be involved, the
better.
1.5.5. How do you identify and analyse stakeholders and their interests?
The first step in identifying and addressing stakeholder interests is, not surprisingly,
identifying the stakeholders. We’ve discussed in general terms the categories that
stakeholders might fall into, but the list is different for each community and each
project. It’s an important part of your job to determine who all your stakeholders are
and to try to involve them in a way that advances your goals.
Identifying stakeholders
In identifying stakeholders, it’s important to think beyond the obvious. Beneficiaries,
policymakers, etc. are easy to identify, whereas indirect effects – and, as a result,
secondary stakeholders – are sometimes harder to see. A push for new regulations on
a particular industry, for instance, might entail greatly increased paperwork or the
purchase of new machinery on the part of that industry’s suppliers. Traffic restrictions
to control speeding in residential neighbourhoods may affect commuters who use
public transportation. Try to think of as many ways as possible that your effort might
bring benefits or problems to people not directly in its path.
Given that, there are a number of ways to identify stakeholders. Often, the use of more
than one will yield the best results.
• Brainstorm. Get together with people in your organisation, officials and others
already involved in or informed about the effort and start calling out categories
and names. Part of the point of brainstorming is to come out with anything that
comes to mind, even if it seems silly. On reflection, the silly ideas can turn out to
be among the best, so be as far-ranging as you can. After 10 or 15 minutes, stop
and discuss each suggestion, perhaps identifying each as a primary, secondary
and/or key stakeholder.
• Collect categories and names from informants in the community (if they’re not
available to be part of a brainstorming session), particularly members of a
Some stakeholders may have economic concerns. Sometimes these concerns are
merely selfish or greedy – as in the case of a corporation with billions in annual profits
unwilling to spend a small part of that money to stop its factories from polluting – but
in most cases, they are legitimate.
Stakeholder analysis
Stakeholder analysis is a way of determining who among stakeholders can have the
most positive or negative influence on an effort, who is likely to be most affected by the
effort, and how you should work with stakeholders with different levels of interest and
influence.
Most methods of stakeholder analysis divide stakeholders into one of four groups, each
occupying one space in a four-space grid:
As you can see, low to high influence over the effort runs along a line from the bottom
to the top of the grid, and low to high interest in the effort runs along a line from left to
right. Both influence and interest can be either positive or negative, depending on the
perspectives of the stakeholders in question. The lines describing them are continuous,
The people we’ve described as ‘key stakeholders’ would generally appear in the upper
right quadrant.
The purpose of this kind of diagram is to help you understand what kind of influence
each stakeholder has on your organisation and/or the process and potential success of
the effort. That knowledge, in turn, can help you decide how to manage stakeholders –
how to marshal the help of those that support you, how to involve those who could be
helpful, and how to convert – or at least neutralise – those who may start out feeling
negative.
An assumption that most proponents of this analysis technique seem to make is that
the stakeholders most important to the success of your effort are in the upper right
section of the grid, and those least important area in the lower left. The names in
parentheses are another way to define the same stakeholder characteristics in terms of
how they relate to the effort.
• Promoters have both great interest in the effort and the power to help make it
successful (or to derail it).
• Defenders have a vested interest and can voice their support in the community,
but have little actual power to influence the effort in any way.
• Latents have no particular interest or involvement in the effort but have the
power to influence it greatly if they become interested.
• Apathetics have little interest and little power, and may not even know the effort
exists.
The World Bank, which is responsible for this characterisation, couches it in generally
positive terms, assuming that those in the upper right will promote the effort. In fact,
they could be either promoters or staunch opponents, and the same – with different
The interest here means one or both of two things: (1) that the individual, organisation,
or group is interested intellectually or philosophically in the effort; and/or (2) she or it
is affected by it. The level of interest, in this second sense, corresponds to how great
the effect is. A welfare recipient who stands to receive increased benefits, childcare,
and employment training from a back-to-work programme, for example, has a greater
interest in the effort than someone who simply thinks the programme is a good idea
but has no intention of being involved in it in any way.
Influence and interest can be either internal or external to the organisation or the
community. Most of the descriptions above pertain to external influence and interest,
but they could be internal as well. Organisations and institutions, as well as
communities, have official and unofficial leaders, people in positions that confer power
or influence, people with large networks, etc. In addition, those who actually carry out
the effort – usually staff people in an organisation – can have a great deal of control
over whether an effort is conducted as intended, and therefore over its effectiveness.
A big question here is whether the whole concept of stakeholder management is in fact
directly opposed to the idea of a participatory process, where everyone has a voice. In
practice, we all try to manage people constantly, from attempting to convince a
skeptical three-year-old that broccoli tastes good to motivating students and employees
to do their best.
The next step is to decide who needs the most attention. In general, the business people
who use this model would say that you should expend most of your energy on the
people who can be most helpful, i.e., those with the most power. Powerful people with
the highest interest is most important, followed by those with power and less interest.
Those in the lower right quadrant – high interest, less power – come next, with those
with low interest and low power coming last.
Another way to look at stakeholder management – and remember that all the people
and groups we’re talking about here are stakeholders, those who can affect and are
affected by the effort in question – is that the most important stakeholders are those
most dramatically affected. Some of those, at least before the effort begins, maybe in
the lower left quadrant of the grid. They may be too involved in trying to survive – either
financially or physically – from day to day to think about an effort to change their
situation.
1.5.7. Stakeholder management for marshaling support for the effort, especially for
advocacy or policy change:
• The promoters – the high influence/high-interest folks – are the most important
here. They’re the ones who can really make the effort go, and they care about and
are invested in the issue. If they’re positive, they need to be cultivated and
involved. Find jobs for them (not just tasks) that they’ll enjoy, and that contribute
substantively to the effort, so they can feel responsible for part of what’s going
on. Pay attention to their opinions, and accede to them where it’s appropriate. If
their ideas aren’t acted on, make sure they know why, and why an alternative
seems like the better course. As much as possible, make them integral parts of
the team.
When people who could be promoters are negative, the major task is to convert them.
If you can’t, they become the most powerful opponents of your effort, and could make
it impossible to succeed. Thus, they need to be treated as potential allies, and their
concerns should be addressed to the extent possible without compromising the effort.
• The latents – high influence/low interest. These are people and organisations
largely unaffected by the effort that could potentially be extremely helpful if they
could be convinced that the effort is important either to their own self-interest or
to the greater good. You have to approach and inform them, and to keep contact
with them over time. Offer them opportunities to weigh in on issues relating to
the effort, and demonstrate to them how the effort will have a positive effect on
Once again, there’s the possibility that these folks could be negative and oppositional.
If that’s the case, it might be best not to stir a sleeping dragon. If they’re not particularly
affected by or concerned about the effort, even if they disapprove of it, the chances are
that they’ll simply leave it and you alone, and it might be best that way. If they begin to
voice opposition, then your first attempt might be at conversion or neutralisation,
rather than battle. If that doesn’t work, then you might have to fight.
• The defenders – low influence/high interest. In the business model, since these
people and organisations can’t help you much, you can simply keep them
informed and not worry too much about involving them further. In health and
community building, however, they can often provide the volunteer time and
skills that an effort – particularly an advocacy initiative – needs to survive. These
are often the foot soldiers who stuff envelopes, make phone calls, and otherwise
make an initiative possible. They are also often among those most affected by an
effort, and thus have good reason to work hard for or against it, depending on
how it affects them.
• The apathetics – those with low interest and low influence. These people and
organisations simply don’t care about your effort one way or the other. They may
be stakeholders only through their membership in a group or their position in the
community; the effort may, in fact, have little or no impact on them. As a result,
they need little or no management. Keep them sporadically informed by
newsletter or some similar device, and don’t offend them, and they won’t bother
you or get in the way.
The four-cell grid is still useful here, but the attention given to those in each quadrant
will be different from that in the other model. Here, the largest amount of attention
may go to the people in the two lower quadrants, since those with little power often
have less experience in such areas as meeting and planning, and less confidence in their
ability to engage in them. They’ll definitely need information about what they’re being
invited to do, and they might need training, mentoring, and/or other support in doing
it.
A successful participatory process may require that the people in the upper right
quadrant – the promoters – understand and buy into the process fully. They can then
help to bring stakeholders in the other positions on board, and to encourage them to
participate in planning, implementing and evaluating the effort. That means working
with the promoters to explain the concept of participating fully and to convince them
Obviously, not all stakeholders in the lower two quadrants are low-income, unused to
managing things or lacking in educational and organisational skills. Some simply don’t
see themselves as much affected by the effort. Others may have no influence in this
particular situation, though they may have a great deal in other circumstances.
Very often, however, those who do lack skills and experience find themselves in those
two lower quadrants. When that’s the case, they may need training and other support
in order to participate fully. That may be one aspect of stakeholder management, and
it may help to move them into positions of more influence and teach them how to
exercise it.
The tasks of converting the negative or skeptical still exist in this situation, as does the
need to create interest among the latents – those stakeholders who could be helpful
but don’t have a strong investment in the effort. Often, the stories of those who have
or will benefit from the effort can be effective motivators for people who might
otherwise be indifferent. Such stories are particularly powerful if the listeners know the
people involved, but never suspected the difficulties they face.
If the latents become involved, their influence can help to greatly strengthen the effort.
The more people, groups, institutions, and organisations with influence that are
involved, the greater the chances are for success. The task with latents is to convince
them that they are true stakeholders and that the effort will benefit them either directly
or indirectly. If it’s not direct, the benefit in question may be as removed from them as
increasing the community’s tax base by making more people employable or creating a
more just community by eliminating discrimination.
As with anything else you do, it’s important to monitor and evaluate how well
stakeholders have been identified, understood, and involved in the course of your
effort. It’s obviously best to involve stakeholders from the very beginning, but it’s never
too late to learn from what you’ve done so that you can improve your work. Evaluation
of the stakeholder process should be an integral part of the overall evaluation of the
effort, and stakeholders themselves should be involved in developing that evaluation.
They can best tell you what did and didn’t work to pull them in and keep them engaged.
The answers to these and similar questions could both help you improve the current
effort and make a big difference the next time – and there will be a next time – you
involve stakeholders.
Stakeholders of a project are those who have a vested interest in it, either as those who
develop and conduct it or as those whom it affects directly or indirectly. Identifying and
involving stakeholders can be a large part of ensuring the effort’s success. In order to
gain stakeholder participation and support, it’s important to understand not only who
potential stakeholders are, but the nature of their interest in the effort. With that
understanding, you’ll be able to invite their involvement, address their concerns, and
demonstrate how the effort will benefit them.
As with any community-building activity, work with stakeholders has to continue for the
long term in order to attain the level of participation and support you need for a
successful effort.
Probably the biggest challenge project leaders face in managing global teams is the cultural
diversity of team members and stakeholders who are working in multiple locations. It is
common for remote teams to not have regular contact with their project manager. To
complicate issues further, language and cultural barriers can create unclear expectations for
all parties involved. As a result, challenges in effective communication and the sharing of
timely information can be stalled or hindered, thus impacting a project’s success. In many
cases, global project teams and their leaders are making critical decisions based on second-
hand or miscommunicated information.
The other challenge project leaders face in a global environment is the common application
of traditional project management techniques to their global reality. In general, traditional
project management methodologies focus on planning and tracking the details of timelines,
specifications, and costs. The methods of communication and sharing of information tend
not to be formalised and are left up to individual project management practitioners to employ
their own style of communication among stakeholders. Traditionally, project managers were
fortunate to have primarily local face-to-face interactions with their teams and
customers. However, with the globalisation of business, the luxury of face-to-face
communication among project teams and their stakeholders is limited. Long-distance
In part, the significant cause of this miscommunication can be attributed to the use of
communication and documentation tools that are not easily accessible and difficult to share
among dispersed teams. The unstructured exchange of project information living in emails
and documents on people’s desktops make it difficult to keep all project stakeholders
effectively on the same page in terms of a project’s progress, issues and process. The fact is
global project teams demand a communication and project management platform that will
centralise information and create the necessary face-to-face benefits teams are leveraging
among local project teams.
The Project Management Institute, Inc. (PMI) is the project management industry's non-profit
standards body. With almost 270 project chapters and 500,000 members worldwide, PMI is
the largest project management membership group. PMI is a volunteer organisation that
supports and drives our industry forward.
PMI, in conjunction with its volunteer membership, developed A Guide to the Project
Management Body of Knowledge (PMBOK® Guide), which is the agreed upon book of
standard language, terminology and principles governing project management.
In the past, project managers 'fell' into the role. There was no formal degree in project
management. PMI has been instrumental in creating the Project Management Professional
(PMP) certification, which professionalised the career of project management. Now, project
managers worldwide have been studying the agreed upon principles and passing the PMP
examination. The PMP certification is formalising and validating the profession.
Project management is not rocket science, yet it often gets dressed up that way. At its
foundation lies a bedrock of basic organisational skills, which – come to think of it – might as
well be rocket science the way some managers grapple with the concept.
And finally, the production team benefits because without the production team the
project wouldn’t get started in the first place, much less finished. Additionally, the
production team is able to take a stake in something, work with it and see a project
through from start to finish.
So right off the bat you have the trinity of Project Management: manager, client and
worker collaborating for the common good. In fact, it’s this very application of
knowledge, skills, tools and techniques that ultimately will meet or exceed a
stakeholder’s needs and/or expectations on any given project.
Time to do a progress check to determine whether you have gone through all the required
content and completed all the exercises.
Did you complete all the relevant revision exercises and check your answers
against the answers provided?
Project: Planned set of interrelated tasks to be executed over a fixed period and within
certain cost and other limitations.
Project attributes:
• Clear objective
• End product or deliverable, schedule and budget
The project manager is in charge of creating the stakeholder register. The document is
the basis for developing the stakeholder management strategy. Such a strategy defines
an approach to be used to minimise potential negative impacts of the identified
stakeholders. The project manager uses the strategy and the stakeholder analysis
matrix to determine the stakeholder impacts, identify the level of participation and
involvement, and get a representation of stakeholder groups.
• Identifying project stakeholders
• Planning communications and distributing information
• Managing stakeholder expectations
• Reporting communication performance
Global projects involve team members from various cultures and organisations, spread
in locations across countries and time zones, and speaking different native languages
(Exhibit 1). Each of these dimensions can contribute to the success of the team and the
quality of the project deliverables, while adding challenges to project and programme
managers, PMOs, and the team members.
Multicultural teams can increase the level of innovation, when various standpoints are
fostered and harvested. Experienced project managers can organise very rich
brainstorming sessions to collect different ideas and to assess their risks and
opportunities. Similar strategies can be applied for problem-solving situations and when
identifying international strengths and weaknesses from social, economic, political,
environmental, religious, and technical perspectives. However, most global project
managers would have already faced some form of misunderstanding generated by
conflicting views on values or behaviours. Very often, these conflicts can take precious
time and energy to get under control.
Team members from different organisations can have access to a more affluent set of
tools, knowledge, facilities, raw materials, intellectual properties and equipment. They
may also bring their own processes, standards, procedures, and corporate objectives,
which must be perfectly aligned or synchronised for the execution of the project work
packages within the time, scope, cost and quality constraints.
Most team members are allocated to projects according to their knowledge and
availability. Global projects allow these team members to work together independently
of their geographical situation, without the added costs and time needed for relocation.
On the other hand, meetings across locations can generate many misunderstandings,
as they rely mostly on verbal communication, losing an important part of the content
that could be exchanged by visual cues.
Some projects can also benefit from the ‘around-the-clock’ effect for activities that
require 24-hour support. Teams spanning various time zones can perform long
sequential activities, such as executing a series of tasks that require supervision during
15 non-interrupted hours, starting with a team in Australia and handing off to a team in
Spain for completion. The different time zones can also facilitate maintenance work,
And do you believe that English is the universal business language? Perhaps, but is this
accepted in diverse countries such as France, Italy, Russia, and China? This is often a
controversial discussion, but assuming that you get a common agreement that English
(or any other language) is the ‘official’ project language during meetings and for
documentations, what are the levels of understanding from stakeholders around the
globe in that language? Can they understand technical terms, measurement units,
jargon and slang? Are they able to have informal discussions – very important for
teambuilding activities – outside their native language? Only a few projects can benefit
from having multilingual team members to translate requirements and communication
in order to increase the commitment from specific stakeholders.
Global projects have clear advantages, and also challenges. It is very important to
consider them carefully during project initiation, and put in place a set of good practices
that will guarantee effective implementation.
This section covers Chapter 2 and 3 of Gido, Clements & Harinarain (2018).
The purpose of the initiating a project process is to understand the work that needs to be
done to deliver the required products. This understanding is needed before deciding to
continue with the project. Like any project there are a number of important items to discover,
and so there are a number of questions to ask about the project, such as:
• What are the reasons for doing the project and the benefits and risks?
• Scope: What is to be done and what will not be included?
• When can the products be delivered?
• How can it be ensured that quality will be achieved?
• How are risks, issues and changes identified and followed up?
• How the project progress is monitored and who needs to be informed and how often?
Let us put initiating a project into context and look at what it really does for the project. The
Starting up a project process checks if the project is viable, while initiating a project is about
building a correct foundation for the project so that all stakeholders are clear on what the
project will achieve.
The alternative would be to allow projects to start after the starting up a project process
without knowing any of the following: planning, milestones, cost and level of quality. It is a
bit like building a house on little or no foundation.
Initiating a project can be a big investment for a company but it’s a necessary investment to
plan and run the rest of the project. During initiating a project, the Project Manager will be
creating a collection of management products to show: how the project will be managed, the
cost, how quality will be checked, planned, how communication will be done, etc.
Project selection is the first important part of project management. The responsibility is with
the leadership team of the organisation. Typically, they establish a steering committee that
overlooks the process of selecting projects, including project monitoring, and directly
reporting to the CEO – if the CEO is not a member of that steering committee already.
We assume that the organisation has a strategy in place that covers the next three to ten
years, depending on the type of business the organisation is in. This strategy identifies areas
where the organisation:
• needs to improve or change in terms of organisational structure, research and
development capacity, development of products, office space, manufacturing capacity,
etc.,
• wants to serve customers in order to earn money.
Then, our leading question for the selection of projects turns into:
"How can we make sure that we are doing only projects that supportour strategy in these
two areas?"
Answering this question for the first area leads to investment projects; for the second area it
leads to customer projects.
All these projects need resources partially or fully provided by the organisation itself. Since
these resources are limited not all of the projects we would like to pursue can be staffed or
funded adequately. So, projects in different areas will compete with each other in order to
get support of the organisation in terms of staffing and funding.
These methods require a certain minimum level of ‘planning’ for each one of the
projects to be evaluated. We need to know
• project life cycle duration, in number of accounting periods,
• expected project cost per accounting period,
Usually, we do this whole evaluation in definition or early planning phase. Then, we only
have estimates of those values and should make sure that the estimation accuracies are
comparable.
The Net Present Value (NPV) of a project is defined as the difference between present
value of cash inflow (revenue, PV in) and present value of cash outflow (cost, PV out) of
that project over the project life cycle time. Here is the formula to calculate the present
value (PV) for given future value (FV), interest rate (r), and number of accounting
periods (n):
If we would have to choose between project ‘Blue’ and project ‘Red’ we would choose
the one with the higher NPV, i.e. project ‘Blue’.
Another evaluation method uses the concept of Internal Rate of Return (IRR). The
internal rate of return of a project is defined as the interest rate at which the net present
value of that project equals zero. Here, we spare you the mathematical details of
calculating IRR's, and give you the results for the two examples, projects ‘Blue’ and
‘Red’, obtained by trial and error with a simple MS Excel sheet.
In project selection, we usually account for an overall view of benefits and costs of
proposed projects, trying to express all benefits and all costs in monetary terms of
present values at given interest rates. This is the concept of the benefit cost ratio (BCR).
Here is the formula:
If we only consider cash inflow as benefits and cash outflow as costs, we end up with
our familiar decision to choose project ‘Blue’.
With the concept of opportunity cost (OC) we consider that choosing one option means
to give up other options we might have. In our example, we choose project ‘Blue’
(because of the higher NPV or IRR or BCR) and give up project ‘Red’, at an opportunity
cost of NPV = R2,066.00.
Using the method of payback period (PP) gives us the simplest approach. We have the
following formula.
We decide in favour of the project with the shorter payback period, and our choice
would be project ‘Blue’. Notice that we do not apply present values explicitly.
In general, we emphasise that the methods using Net Present Value (NPV), Internal Rate
of Return (IRR), Benefit / Cost Ratio (BCR), or Opportunity Cost (OC), are all based upon
the calculation of present values of estimated future cash inflows and outflows. In a
mathematical sense, they usually lead us to the same project selection results. Typically,
application of one of these methods is enough.
If available, we can take initial risk assessments into consideration of the evaluation of
project proposals. The following chart shows an example of this comparative analysis.
Remarks:
The examples used above are rather simple and therefore, the corresponding results
suggest equivalent selection decisions.
From the perspective of a project owner (for an internal project the organisation is the
project owner as well, and partially even the supplier):
• Acceptance of feasibility studies
• Request for proposal (RFP) or request for quotation (RFQ)
• Vendor selection/signature of contract
• Design freeze/approval of detailed planning documents
• Preliminary acceptance
• Final acceptance.
This way, an organisation can monitor all their projects by ‘standardised’ project
management reviews.
Final remark: The whole organisation should have a clear understanding about when to
terminate a project. Like in project selection, the criteria are similar: If a project cannot
fulfil expectations in terms of strategy support or originally estimated figures like net
project value (NPV), payback period (PP), etc. it should be terminated.
The final section of the project charter is the approvals section. The project manager and
project sponsor (or the person who kicked off the work, if a longer-term sponsor has yet to
be appointed) should sign and date the document. Today, that’s likely to be via email, so keep
a copy of the email authorisation in your project files in case you need to refer back to it.
The RFP typically contains a section, sometimes called a statement of work (SOW),
defining the scope of work or the scope of service(s) to be provided. This section
discusses the tasks to be performed by the winning bidder and a timeline for providing
deliverables.
The request for proposal also includes guidance to bidders on how to prepare a
proposal. This section will provide the details on the proposal format, as well as
instructions on how the RFP response is to be constructed and organised.
A solicited proposal is when customers ask for a proposal. They may ask verbally or they may
issue a written Request for Proposal (RFP). An unsolicited proposal is when you send them a
proposal they haven’t even asked for because you think they should buy from you or take
some action.
Solicited proposals are usually sent to customers who issue an RFP. When customers want
something that is too complicated to pick up at the store or order from a vendor, they often
Sometimes you will make a suggestion to a potential customer and they will ask you to submit
a proposal so that they can consider your suggestion. This counts as a solicited proposal
because they are expecting it and you have a chance to talk to the customer and gain an
understanding of their needs.
An unsolicited proposal is sent to a customer who has not requested it. Unsolicited proposals
must be especially convincing since the customer has not anticipated, planned, or budgeted
for the proposal. With an unsolicited proposal you run the risk that the customer won't even
bother to read it, since they didn't ask for it. However, the lack of competitive pressure with
an unsolicited proposal often makes up for the risk.
If you send the same unsolicited proposal to a bunch of customers, what you really have is a
brochure and not a proposal. A proposal should take into consideration the customer's
specific environment, needs and concerns. Proposals have a much higher win rate than
brochures, because they better align what you offer with what matters to the customer.
Included in each section are also a few tips and examples to help you produce a proposal
that is clear, accurate and focused.
Project background
Explain what needs/problems you are trying to solve, and why these needs/problems
are worth solving. You should also provide a brief setting and history behind the project.
This section should be no more than a page. Include references to supporting
documentation, such as research papers and articles. This information can be placed in
the index at the end.
Project objectives
State explicitly what goals the project is aiming to achieve.
• Objective 1
• Objective 2
• Objective 3.
Project methodology
This section details the plan for how the project objectives will be achieved. It usually
starts with a description of the overall approach. Then it provides details on
methodology, the population being addressed, and how anticipated problems will be
managed.
Project deliverables
Make a list of the project ‘deliverables’. (These are the products, information, reports,
etc. that will be delivered to the client at the end and throughout the duration of the
project). Make sure to include a description of the deliverable and an estimated delivery
date.
• Risk management plan: This is the detailed plan of action to minimise and contain
any risk factors that may come up as the project progresses.
• Risk register: Be sure to include this line-item list of risks and counter efforts.
Conclusion
In this section you should try to tie up all the above information in a short summary that
explains the potential value of the project and emphasises its feasibility.
Appendix
This is where you should put additional charts, graphs, reports, etc. that were cited in the
proposal, but were not appropriate to place in the main body of the document.
Did you complete all the relevant revision exercises and check your answers
against the answers provided?
2. Describe how a business selects which projects to work on when there are numerous
projects that could be performed.
A four-step process is recommended:
• Develop a set of criteria against which the opportunity will be evaluated.
• List assumptions that will be used as the basis for each project.
• Gather data and information for each project
• Evaluate each opportunity against the criteria.
4. Explain why building relationships with customers and partners is important. How can
this be achieved?
It is important to build relationships with customers and partners since they prefer to
work with people they know and can trust. Relationships establish the foundation for
It is important that the people who will be involved in performing the work are also involved
in planning the work. They have the most knowledge about the activities required to perform
and the duration of those activities. By being part of the planning of the work, commitment
towards achieving it according to the plan and within the constraints are achieved. While the
work on the project is being performed, it is necessary to monitor and control the progress to
ensure that everything is going according to the plan.
Section 1: Defining Scope, Quality, Responsibility, Activity Sequence and Developing the
Schedule.
• Establish a clear project objective and prepare a project scope document
• Discuss the importance and elements of a project quality plan
• Develop a work breakdown structure, a responsibility assignment matrix, define the
specific project activities and create a network diagram
• Estimate the resources required for activities and their durations
Section 1: Defining Scope, Quality, Responsibility and Activity Sequence and Developing the
Schedule.
• Clear project objectives are identified.
• A project scope document is correctly developed
• The importance of a project towards achieving organisational goals is discussed.
• Elements of a project quality plan are fully explained.
• A WBS and a RAM are developed from a scenario
• Project activities are correctly defined and used in developing the relative network
diagram
This section covers Chapter 4 and 5 of Gido, Clements & Harinarain (2018).
The project objective describes the project’s outcomes: intended and direct, short- and
medium-term effects on the target group. The project objective must lie within the scope of
the project, and one must be able to attribute the effects to the project directly. The project
objective is often formulated in terms of the project’s utility for the target group: “Better…
higher…” It also makes sense to formulate the project objective as a situation to be achieved
in the future.
The project objective ought also to describe an outcome, meaning the effect or change that
the project is supposed to cause for the target group. In practice it is often not quite so simple
to distinguish outcomes from outputs, i.e. the project’s products and deliverables. Well-
formulated, genuine outcome (and impact) objectives are therefore of great importance if
the outcome and impact assessment is to have any significance.
N.B. Do not simply summarise the outputs, but describe the effects that should be triggered
at a higher level.
Improvements are made in the health of children in the poorest parts of the country.
• Health course project
Young mothers in regions x, y and z should use clean drinking water more often or boil
dirty water.
• Well-building project
The population of regions x, y and z should have better access to clean drinking water.
• Medical care project
An easy way to ensure that you include enough detail in your objective is to follow the
mnemonic S.M.A.R.T.:
• Specific: Define your objectives clearly, in detail, leaving no room for
misinterpretation. Think of the 5Ws (who, what, when, where, and why).
• Measurable: State the measures and performance specifications you’ll use to
determine whether you’ve met your objectives.
• Achievable or Attainable: Choose objectives that the team has a reasonable
expectation of successfully completing.
• Realistic: Set objectives the project team believes it can achieve. Relevant
objectives align with group or company goals.
• Time-bound: Include the date or specific period by which you’ll achieve the
objectives.
Project scope is the part of project planning that involves determining and documenting a list
of specific project goals, deliverables, tasks, costs and deadlines. The documentation of a
project's scope, which is called a scope statement, terms of reference or statement of work,
explains the boundaries of the project, establishes responsibilities for each team member and
sets up procedures for how completed work will be verified and approved. During the project,
this documentation helps the project team remain focused and on task. The scope statement
also provides the project team with guidelines for making decisions about change requests
during the project. Please note, a project's scope statement should not be confused with its
charter; a project's charter simply documents that the project exists.
It is natural for parts of a large project to change along the way, so the better the project has
been ‘scoped’ at the beginning, the better the project team will be able to manage change.
Project managers generally find that establishing project scope ensures projects are
focused and executed to expectations. The scope provides a strong foundation for
managing a project as it moves forward and helps ensure that resources aren't diverted
or wasted on out-of-scope elements.
The project scope statement also establishes what is not included in initiatives, either
implicitly or explicitly. Objectives and tasks not listed in the project scope statement
should be considered out of scope. Project managers can also list specific work that will
not be part of the project. As such, this statement establishes the boundaries of each
specific project. Project leaders need to take those requirements and map out what
should happen and in what order those items need to occur. This generally leads to the
creation of a work breakdown structure (WBS). As the name states, the work
breakdown structure breaks down the totality of planned work into smaller portions
and required tasks.
Project managers should rely on change management processes that determine how
such requests should be evaluated while considering updates and alterations to the
project. The ability to distinguish between which requests are truly needed and which
are out of scope allows organisations to avoid scope creep. Scope creep happens when
more and more work is tacked onto projects as they're underway. Scope creep
frequently adds extra costs and unnecessary work while muddling objectives and
threatening the quality of the intended deliverables.
Project quality management is all of the processes and activities needed to determine and
achieve project quality.
At its most basic level, quality means meeting the needs of customers. This is also known as
‘fit for use’.
This simple definition of quality places the focus where it should be, on the customer. This
basic definition also implies that the requirements of the project have been met since the
requirements should reflect the customer's needs if collected properly.
As the project manager, there are three key quality management concepts that will help you
deliver a high-quality project
• Customer satisfaction
• Prevention over inspection
• Continuous improvement.
Customer satisfaction
Customer satisfaction is a key measure of a project's quality. It's important to keep in mind
that project quality management is concerned with both the product of the project and the
management of the project.
If the customer doesn't feel the product produced by the project meets their needs or if the
way the project was run didn't meet their expectations, then the customer is very likely to
consider the project quality as poor, regardless of what the project manager or team thinks.
The cost of preventing mistakes is usually much less than the cost of correcting them.
Continuous improvement
Continuous improvement is a concept that exists in all of the major quality management
approaches such as Six Sigma and total quality management (TQM). In fact, it is a key aspect
of the last concept, prevention over inspection.
From a project perspective, this concept can be applied by analysing the issues that were
encountered during the project for any lessons learned that you can apply to future projects.
The goal is to avoid repeating the same issues in other projects.
Plan quality involves identifying the quality requirements for both the project and
the product and documenting how the project can show it is meeting the quality
requirements. The outputs of this process include a Quality Management Plan,
quality metrics, quality checklists and a Process Improvement Plan.
• Perform quality assurance
Quality assurance is used to verify that the project processes are sufficient so that
if they are being adhered to the project deliverables will be of good quality.
Process checklists and project audits are two methods used for project quality
assurance.
• Perform quality control
Quality control verifies that the product meets the quality requirements. Peer
reviews and testing are two methods used to perform quality control. The results
will determine if corrective action is needed.
A work breakdown structure (WBS) is a key project deliverable that organises the team's work
into manageable sections. The Project Management Body of Knowledge (PMBOK) defines the
work breakdown structure as a "deliverable oriented hierarchical decomposition of the work
to be executed by the project team." The work breakdown structure visually defines the scope
into manageable chunks that a project team can understand, as each level of the work
breakdown structure provides further definition and detail.
An easy way to think about a work breakdown structure is as an outline or map of the specific
project. A work breakdown structure starts with the project as the top-level deliverable and
is further decomposed into sub-deliverables using the outline hierarchy.
The project team creates the project work breakdown structure by identifying the major
functional deliverables and subdividing those deliverables into smaller systems and sub-
deliverables. These sub-deliverables are further decomposed until a single person can be
assigned. At this level, the specific work packages required to produce the sub-deliverable are
identified and grouped together. The work package represents the list of tasks or ‘to-dos’ to
produce the specific unit of work. If you've seen detailed project schedules, then you'll
recognise the tasks under the work package as the ‘stuff’ people need to complete by a
specific time and within a specific level of effort.
From a cost perspective, these work packages are usually grouped and assigned to a specific
department to produce the work. These departments, or cost accounts, are defined in an
organisational breakdown structure and are allocated a budget to produce the specific
deliverables. By integrating the cost accounts from the organisational breakdown structure
and the project's work breakdown structure, the entire organisation can track financial
progress in addition to project performance.
Project work breakdown structures can also be used to identify potential risks in a given
project. If a work breakdown structure has a branch that is not well defined, then it
represents a scope definition risk. These risks should be tracked in a project log and
reviewed as the project executes. By integrating the work breakdown structure with an
organisational breakdown structure, the project manager can also identify
communication points and formulate a communication plan across the project
organisation.
When a project is falling behind, referring to the work breakdown structure will quickly
identify the major deliverables impacted by a failing work package or late sub-
deliverable. The work breakdown structure can also be colour coded to represent sub-
deliverable status. Assigning colours of red for late, yellow for at risk, green for on-
target, and blue for completed deliverables is an effective way to produce a heat-map
of project progress and draw management's attention to key areas of the work
breakdown structure.
The low-technology approach is easy to do; however, it does not work well with
distributed teams or translate easily into an electronic format. There are several tools
available that support mind mapping, brainstorming, and work breakdown structures,
for example Microsoft Project.
The responsibility assignment matrix (RAM) or RACI matrix is a useful project planning tool.
Yet we often see it used incorrectly. Let’s keep things simple and offer a concise RACI matrix
definition that makes it clear who does what.
This is really straightforward and people will be certain what role they fulfil in the project or
business change endeavour.
The responsibility assignment matrix or RACI matrix is used to clarify the roles in
projects or processes. There are four key roles that are included in the RACI matrix
definition. These are:
o Responsible – the person who does something as part of his/her job or role to do
a specific task or activity.
o Accountable – the person who is expected to justify actions taken or decisions
made to deliver the completed task or activity.
o Consulted – groups or people whose opinions are sought by the person
responsible for the task or activity.
o Informed – those groups or people who should be kept up-to-date on progress
with the task or activity.
o Correct use of the RACI matrix
If you break these simple rules, you create uncertainty and confusion. And, when someone is
made responsible for something, be sure he/she has the necessary authority to make it
happen.
Once the activities have been identified, the next stage is to sequence them according to their
dependencies. In other words, any relationships between activities need to be identified so
that dependent activities can be scheduled to follow those that they are dependent upon.
It is important to classify any dependencies properly because they indicate the sequence in
which activities must occur. There are four types of dependency relationships.
Dependencies may be external or internal. For example, an organisation may subcontract the
production of some deliverable from a supplier organisation and the delivery of this would
represent an external dependency, one that involves some relationship outside of the project
and its control.
Some dependencies may exist within the project. For example, an engineer may only be able
to contribute half of his time to a project, although his skills could potentially be used full
time.
The principal output from this process is a network diagram showing the sequence of
activities and their relationships. Always bear in mind that the purpose of this process is
simply to find and illustrate dependencies, there are assumed to be no resource constraints.
There are three interrelated techniques that can be used to sequence activities.
A precedence diagram is a graphical tool for scheduling activities in a project plan. It uses
boxes or rectangles, referred to as nodes to represent activities and connect them with
arrows to show the logical relationships that exist between them. This technique is also called
Activity On Node (AON) and is the method used by most software project management
packages.
In this example:
• 'Begin' and 'End' are both milestones.
• Activities A and B are not dependent on each other.
• Activity C is dependent on both A and B (shown as a circle).
Many of the project planning software packages available use this method, which simply plots
the tasks to be completed and connects them with arrows that show the dependencies. Note
that each activity has an input arrow and an output arrow.
Three types of dependencies are used to define the sequence among the activities:
• Mandatory
• Discretionary
• External.
The table below shows the dependency and gives an explanation for this.
Mandatory dependencies are inherent in the work or process, e.g. when constructing a new
building, building the walls is dependent on laying the foundations. The project team
determines which dependencies are mandatory to reach during the process of sequencing
the activities. They are also sometimes referred to as hard logic.
Discretionary dependencies are those defined by the project manager and his/her team.
They should be defined based on best practices or previous experience within a particular
Discretionary dependencies should be fully documented since they can create arbitrary total
float values and can limit later share dealing options.
Once the dependencies are agreed they can be mapped into a precedence diagram (on a PC,
on paper, or using post-it notes). When drawing the precedence diagram the project team
needs to decide:
• Which tasks can only be completed after another task
• Which tasks can be done at the same time
• Which tasks don't depend on other tasks at all (e.g. project review meetings).
It can be useful to work backwards when compiling the precedence diagram and ask yourself
what do we need to have done immediately before this task?
You will then need to apply leads and lags. A lag directs a delay in the successor activity. For
example, an IT project requires two different but similar user interfaces to be designed,
interfaces A and B. Each task is scheduled to take 5 days. There is no reason why these tasks
cannot be started at the same time, but it makes sense to design A first and obtain user
agreement before starting work on interface B which can then be largely based on A.
Therefore, the time between the start dates of the two tasks can be defined as a lag (The
project manager has specified two days in this case). It is important to note that task B does
not need to be completed before task A can begin but because some of the lessons learned
in the design stage of task A can be directly applied to task B it will reduce the overall amount
of work required if this lag is specified.
Lead refers to a relationship whereby the successor activity begins before the predecessor
activity has completed. Lead is only found activities with finish-to-start relationships: A must
finish before B can start. In order to leverage a lead, which will compress the total combined
duration of both activities, the dependency must be discretionary, meaning that there is no
physical limitation on completing A before B begins.
Standardised schedule network diagram templates can be used to expedite the preparation
of networks of project activities. They can include an entire project or only a portion of it.
Portions of a project schedule network diagram are often referred to as a sub-network or a
fragmented network.
Sub-network templates are especially useful when a project includes several identical or
nearly identical deliverables, such as floors on a high-rise office building, clinical trials on a
pharmaceutical research project, coding program modules on a software project, or the start-
up phase of a development project.
Essentially, driving without any idea of how you're going to get there is the same as
working on a project without a schedule. No matter the size or scope of your project,
the schedule is a key part of project management. The schedule tells you when each
activity should be done, what has already been completed, and the sequence in which
things need to be finished.
Luckily, drivers have fairly accurate tools they can use such as GPS. Scheduling, on the
other hand, is not an exact process. It's part estimation, part prediction, and part
‘educated guessing’.
Because of the uncertainty involved, the schedule is reviewed regularly, and it is often
revised while the project is in progress. It continues to develop as the project moves
forward, changes arise, risks come and go, and new risks are identified. The schedule
essentially transforms the project from a vision to a time-based plan.
With that in mind, what's the best way of building an accurate and effective schedule
for your project?
A project manager should be aware of deadlines and resource availability issues that
may make the schedule less flexible.
Scheduling tools
Here are some tools and techniques for combining these inputs to develop the
schedule:
• Schedule network analysis – this is a graphic representation of the project's
activities, the time it takes to complete them, and the sequence in which they
must be done. Project management software is typically used to create these
analyses – Gantt charts and PERT charts are common formats.
• Critical path analysis – this is the process of looking at all of the activities that
must be completed, and calculating the ‘best line’ – or critical path – to take so
that you'll complete the project in the minimum amount of time. The method
calculates the earliest and latest possible start and finish times for project
A good way of avoiding this is to schedule projects in distinct stages, where final quality,
finished components are delivered at the end of each stage. This way, quality problems
can be identified early on and rectified before they seriously threaten the project
schedule.
Project review
Once you have outlined the basic schedule, you need to review it to make sure that the
timing for each activity is aligned with the necessary resources. Here are tools
commonly used to do this:
• ‘What if’ scenario analysis – this method compares and measures the effects of
After the initial schedule has been reviewed, and adjustments made, it's a good idea to
have other members of the team review it as well. Include people who will be doing the
work – their insights and assumptions are likely to be particularly accurate and relevant.
This section covers Chapter 6 and 7 of Gido, Clements & Harinarain (2018).
While there are several important metrics and key performance indicators (KPI) in the project
management world, few are as important to the success of projects and the health of
portfolios as resource utilisation.
The key is to shift the emphasis away from frenetically correcting resource imbalances during
a project — which is like trying to keep a bunch of spinning plates in the air from slowing down
and crashing! — and instead taking a more strategic approach that minimises the frequency
and severity of resource imbalances when (not if) they occur.
To that end, here are five best practices for resource utilisation that will help all project
leaders, regardless of whether they’re at the helm of their 1st project or their 300th:
Before allocating individual resources to specific projects, it’s wise to take a step back
and create a global inventory pool that is comprised of resources that are currently
needed, and of the anticipated resources that will be required for projects coming down
the pipeline. This inventory helps project leaders know whether it is necessary to dial-
up recruitment efforts, as well as determine resource constraints that could (and
probably will) impact project deadlines and delivery dates.
Once a global inventory pool has been created, project leaders should leverage visibility
to allocate resources based on availability and need. This visibility is driven by project
management software (read: keep spreadsheets out of this!), and is characterised by
the ability to look across the entire project pool, quickly determine overall capacity, and
compare current load with future demand.
The simplest, smartest, and most successful approach is (as described above) to create
an inventory of resources, and then assign individual resources to specific projects as
required. From there, the project manager (sometimes with support from the resource
manager) has the inputs required — i.e. people — to build a detailed and above-all-else
realistic project plan. Indeed, it frankly doesn’t matter how intricate a project plan is,
and whether the work breakdown structure is beautiful to behold. If the plan isn’t
realistic because it’s not aligned with available resources, then it is doomed to fail
before it starts.
All project leaders know that they need to tell resources that their services are required
and schedule them accordingly for tasks. However, what makes this process time
consuming and error-riddled is when it must be done manually through emails, sending
spreadsheets back-and-forth, and so on. Granted, on very small and simple projects this
isn’t too much of a burden. But on larger and more complex projects — which is the
norm in enterprise environments — trying to get on-site and remote resources in the
loop can be an exercise in frustration and often futility as well.
Using powerful (but easy to use) project management software to assign individual
resources to specific work items is essential here, as it turns an uphill and unwelcome
challenge into a smooth, streamlined and largely automated process.
As noted above, resource imbalances in either direction are a major — and in some
cases, catastrophic — project threat. To mitigate this risk, project leaders need to
Resource utilisation can be a difficult objective, but it shouldn’t give project leaders
nightmares as they watch in horror as their projects veer off-track, and their portfolios
fail to generate ROI. It is possible to turn resource utilisation from a risky challenge into
a competitive advantage.
There are two processes within the cost knowledge area: Estimate Costs and Determine
Budget. Both are required in order to develop the project cost performance baseline.
Cost estimate
The cost estimates are simply the costs associated with the work packages or activities within
the project schedule. Depending on the work package or activity, the cost estimate may be
determined using parametric, three-point, or analogous estimating techniques.
It is important for all cost estimates to include any assumptions that were made, where did
the estimate originate, who provided the information, level of confidence, etc?
Budget
The budget is built using the cost estimates and the project schedule. The budget provides a
view of how much the project is estimated to cost both from a total and a periodic
perspective. This budget feeds the cost performance baseline which is then used as a critical
ingredient in performing earned value analysis and other cost management variance analysis
techniques.
Example:
A bathroom remodeling project will include the following cost estimates:
Both cost estimates and budgets are needed in order to determine the cost performance
baseline and the project funding requirements.
Cost estimates are the estimated costs for each work package or activity, whereas the budget
allocates the costs over the life of the project to determine the periodic and total funding
requirements.
Most organisations prepare a budget for every activity they engage in, as well as their normal
operations. At the end of the time period or project, the budget is compared with the actual
Current performance is the best indicator of future performance, and, therefore, using trend
data, it is possible to forecast cost or schedule overruns at an early stage in a project. The
most comprehensive trend analysis technique is the earned value method.
In a nutshell, earned value is an approach where you monitor the project plan, actual work,
and work completed value to see if a project is on track. Earned value shows how much of the
budget and time should have been spent, considering the amount of work done so far.
Earned value differs from the general budget versus actual costs incurred model, in that it
requires the cost of work in progress to be quantified. Earned value allows the project
manager to compare how much work has been completed, against how much he expected to
be finished at a given point in time.
The project manager needs to agree on the project scope, create a work breakdown structure
and assign a budget to each work package, the lowest level of the WBS. Next, he or she will
create a schedule showing the calendar time it will take to complete the work. This overall
plan is baselined (this is the planned value) and used to measure performance throughout the
project. As each work package is completed (earned) it is compared with planned value,
showing the work achieved against the plan. A variance to the plan is recorded as a time or
schedule deviation.
Earned value provides the project manager with an objective way of measuring performance
and predicting future outcomes. Earned value can enable him or her to report progress with
greater confidence and highlight any overrun earlier. This, in turn, allows the management
team to make cost and time allocation decisions sooner than would otherwise be the case.
It is true that past performance is a good indicator of future performance. Earned value is a
useful tool for predicting the outcome of projects in terms of time to completion, the cost to
completion and expected final costs.
Just as project managers must secure the availability of the project team members and the
materials or equipment required for the tasks, they must also secure the project cash
flow availability. While some contractors will wait until the completion of the project to
receive payment, others must be paid when they have finished their assignment. Still, other
contractors may require periodic payments during the course of the work. Some materials
and equipment may be available within the performing organisation but other equipment
must be leased or rented. And materials must be ordered from suppliers who have their own
payment terms.
The project manager should also create an actual cash flow document and compare it
with the planned cash flow each month. The cash flow project plan should be secured
and if either the project manager or finance manager wants to modify it, they should
ask for a change request. That is because the change will affect the project dimensions,
Time to do a progress check to determine whether you have gone through all the required
content and completed all the exercises.
Did you complete all the relevant revision exercises and check your answers
against the answers provided?
1. Explain how you would go about writing a project scope document. Why is it
important to clearly define the project scope?
Laddering should be used when a project has a set of activities that are repeated several
times and appropriate resources are available to handle tasks concurrently. Specific
examples will vary. Responses should contain a set of activities that are repeated and
that have adequate resources to do the tasks concurrently.
3. Work through the appendix on p.139 of Gido, Clements & Harinarain (2018) and begin
building the Consumer Market Study Project in Microsoft Project.
The Gantt Chart View and the Task ribbon are the default view when Microsoft Project
is first opened. Other views are chosen by clicking on the arrow in the View group on
the Task ribbon and selecting the name from the drop-down list.
Figure 4A.4, Work Package, and Activity Entry depicts the entry
of the work breakdown structure work items and work
packages. The work packages are the activities that start with
a verb. The summary tasks all start with a verb. The project
title is entered on the first task line to help students see the summary information.
Project 2013 has the capability to hide and view the summary tasks and the project title.
The team should establish a regular reporting period so team members can compare
actual progress to planned progress and deal with any discrepancies as early as possible.
5. The Microsoft project you started in Question 3.3 will now be completed further.
Work through appendix 2 on p.205 of Gido, Clements & Harinarain (2018) and work
further on the Consumer Market Study example.
Figure 5A.1 depicts the duration data for the project. The time can
be entered in as m for minutes, h for hours, d for days, w for weeks,
or mon for months. The duration time needs to be to the level that
the project task can be monitored and controlled. The default time duration is days. The
Figure 5A.2 depicts the schedule table for the project. Microsoft
Project automatically calculates the ES, EF, LS, and LF for the
project. Other tables are available on the Tables menu. Students
must explore the different types of tables. The information presented in the tables and
the choices of table types are dependent upon the view prior to choosing the table.
Figure 5A.3 depicts the Gantt chart with the highlighted critical
path in red. The highlighting of the critical path is important to help
show the tasks that, if delayed, would delay the completion of the
project.
Figure 5A.4 depicts the critical task report that shows information
about each of the tasks on the critical path. This is a valuable report
for communication with the project team about the tasks on the
critical path. Reports are now accessed on the Reports ribbon. Use the menu on the
Report ribbon to select the type of report necessary to display the summary information
about the project. Students must examine the different reports that can be generated.
Figure 5A.8 depicts the updated predecessors on the task list after
adding a new task. Note that Microsoft Project has automatically
adjusted the task numbers and the predecessor numbers.
Figure 5A.9 depicts the tracking table. The tracking table shows
how the project is progressing relative to the baseline that was set.
If the baseline was not set, then Microsoft Project will not have
anything to compare for the tracking table calculations. The percentages display the
amount of completion for the tasks and the summary tasks.
Figure 5A.10 depicts the tracking Gantt. Each of the bars has two
bars. One is for the baseline plan. The other is for the actual
progress of the project. This report shows the effects of changes to
the project for tasks that are completed early, late or on time.
Figure 5A.11 depicts the variance table. The variance table shows
the start and finish of each activity and summary task, the baseline
Resource levelling keeps the project on schedule because activities are delayed only to
the point where all their positive slack is used up, since any further delays would cause
the project to extend beyond the project due date.
8. The Microsoft project you started in Question 3.3 will now be completed further.
Work through the appendix on p.234 of Gido, Clements & Harinarain (2018) and work
further on the Consumer Market Study example.
Add material and cost resources by entering the name in the Resource name column.
Select the type as material or cost in the Type column by clicking on the down arrow in
the Type column for the entry. The ‘Consumer market study’ requires two material
resources and one cost resource, in addition to the four work resources.
Changing a task from Effort driven to not effort driven allows for the entry of work time
that does not equal the duration of the task. Making the change on the Task usage sheet
lets the system make the change for the specific resource within the task. This is a finer
detail than if the work time is changed on the Gantt chart entry view.
Figure 6A.10 depicts the Resource usage report. This report summarises
the work done by each resource for each task by week. The total working
time for each resource is shown at the top of each week's cell for each
resource. This report is helpful for communicating with other project managers who
may be using these same resources; it can help reduce conflicts from over-allocating
shared resources.
10. Define the following: TBC, CBC, CAC, CEV, CPI, CV, FCAC, and TCPI. How is each
calculated?
a) top-down = a portion of the total project cost is allocated to each work package.
b) bottom-up = the sum of the costs of all the activities that make up that work
package.
• CBC: cumulative budgeted cost = the amount budgeted to achieve the work
scheduled to be performed up to that point in time.
• CAC: cumulative actual cost = the amount actually spent to achieve the work
scheduled to be performed up to that point in time.
• CEV: cumulative earned value = % complete X TBC (for the work package)
• CPI: cost performance index = CEV/CAC
• CV: cost variance = CEV – CAC
• FCAC: forecasted cost at completion
a) FCAC = TBC/CPI
b) FCAC = CAC + (TBC – CEV)
c) FCAC = CAC + Re-estimate of remaining work to do
• TCPI: to-complete performance index = (TBC – CEV)/(TBC – CAC)
11. Continue with the Microsoft project you started in Question 3.3. Work through
appendix 2 on p.276 of Gido, Clements & Harinarain (2018) and complete the work on
the Consumer Market Study example.
Figure 7A.2 depicts the Cost resource entry for the task.
The cost of a cost resource is entered as a cost on the
Resource tab in the Task information window. To open
the Task information window, double-click on the task's name in the Task name column
and click on the Resource tab. Choose the name of the cost resource using the drop-
down arrow in the Resource name column for the next open row of Resources. There is
no entry for a cost resource in the Unit column. Only the amount of the cost is entered
in the Cost column.
Figure 7A.3 depicts the Work overview report. The reports in Microsoft
Project 2013 are in the Reports ribbon. If the task resource information is
updated, then this report will show the actual versus baseline for work
resources. The Work overview report provides a quick report for stakeholders about the
key performance information for the project.
Figure 7A.4 depicts the Cash flow report. During the planning phase,
the cash flow report communicates the amount expected to be
expended during each week of the project. The cash flow report
Figure 7A.7 depicts the Task cost overview report. The budget report
displays the total cost, baseline cost, and variance for each activity. Be
sure to save the project baseline when planning is complete in order to
populate a report like the budget report and track the actual costs versus the planned
costs. As with other reports, you can select the number of pages and the dates for the
report on the print menu for the budget report.
Figure 7A.8 depicts the Cost variance table for tasks. This cost
table is one of the table views available in Microsoft Project.
Entry, Schedule, and cost are table types. If you view the Resource sheet and choose the
cost table view, you can see the costs for the resources by resource. To make sure that
you view the costs for the tasks, be sure to have the Gantt chart entry table visible
Managing risk
One attribute of a project is that it involves a degree of uncertainty. Such uncertainty can
impact the outcome of a project. Risk is an uncertain event that, if it occurs, can jeopardise
achieving the project objective. Risk management involves identifying, assessing, and
responding to project risks in order to minimise the likelihood of occurrence and/or potential
impact of adverse events on the achievement of the project objective. Addressing risks
proactively will increase the chances of achieving the project objective. Waiting for
unfavourable events to occur and then reacting to them can result in panic and costly
responses. Managing risk includes taking action to prevent or minimise the likelihood of
occurrence or the impact of such unfavourable events.
Some level of risk planning should be done during the initiating phase of the project life cycle
to make sure, for example, that a contractor understands the risks involved with bidding on
a proposed project. With knowledge of potential risks, the contractor can include contingency
or management reserve amounts in the bid price. On the other hand, if the risks seem too
great, the contractor may decide not to bid on a proposed project. Subsequently, more
detailed risk planning should be done during the planning phase of a project.
A project manager cannot be risk-averse. A project manager must accept that risk is a part of
project management and has to address it head-on. Furthermore, the project manager needs
to set the tone for encouraging open and timely discussion of risks among the project team.
Managing risk:
Would you buy a T-shirt that said, ‘Risk Happens’?
If you answered yes, then you’re thinking like a project manager. Risk is part of your planning
make-up. When you start the planning process for a project, one of the first things you think
about is: what can go wrong?
It sounds negative, but it’s not. It’s preventative. Because issues will inevitably come up, and
you need a mitigation strategy in place to know how to manage risks on your project.
But how do you work towards resolving the unknown? It sounds like a philosophical paradox,
but it’s not. It’s very practical. There are many ways you can get a glimpse at potential risks,
so you can identify and track risks on your project.
o Technical
o Schedule
o Cost
o Human resources
o External and
o Sponsor/ customer
• The likelihood and impact of risk are accurately determined using a risk assessment
matrix.
• Appropriately prioritise risk on a scale from most likely to less likely
• Evaluate and identify the correct risk response with valid reasons from the following
options:
• Correctly detail the procedure for conducting the post-project evaluation meeting.
• Accurately select the criteria for the evaluation
• The value of the lessons learnt exercise is discussed using practical project examples
• The importance of organising and archiving project documents is correctly explained.
• Design a filing system
• The provision of project benefits to the customer is objectively assessed
• The level of customer satisfaction is correctly assessed.
• The feedback that will be helpful for future business relationships is exhaustively
identified.
• The various circumstances that could lead to early project termination are described
fully and applied to a practical scenario.
A risk is anything that could potentially impact your project’s timeline, performance or
budget. Risks are potentialities, and in a project management context, if they become
Risk management can mean different things on different types of projects. On large-scale
projects, risk management strategies might include extensive detailed planning for each risk
to ensure mitigation strategies are in place if issues arise. For smaller projects, risk
management might mean a simple, prioritised list of high, medium and low priority risks.
To manage risks effectively, it is crucial to start with a clear and precise definition of what
your project has been tasked to deliver. In other words, write a very detailed project charter,
with your project vision, objectives, scope and deliverables. This way risks can be identified
at every stage of the project. Then you’ll want to engage your team early in identifying any
and all risks.
And if you are not working in an organisation with a clear risk management strategy in place?
Then you have to talk openly to your boss or project sponsor about risk. You, as the project
manager want them to be aware of what risks are lurking in the shadows of the project. Never
keep this information to yourself, you’ll just be avoiding a problem that is sure to come up
later.
And with every risk you define, you’ll want to put that in your risk tracking template and begin
to prioritise the level of risk. Then create a risk management plan to capture the negative and
positive impact on the project and what actions you will use to deal with them. You’ll want to
set up regular meetings to monitor risk while your project is ongoing. It’s also good to keep
communication with your team ongoing throughout the project. Transparency is critical so
everyone knows what to be on the lookout for during the project itself.
Not all risk is created equally. As mentioned, risk can be either positive or negative, though
most people assume risks are inherently the latter. Where negative risk implies something
unwanted that has the potential to irreparably damage a project, positive risks are
opportunities that can affect the project in beneficial ways.
Negative risks are part of your risk management plan, just as the positive risk should be, but
the difference is in approach. You manage and account for known negative risks to neuter
their impact, but positive risks can also be managed to take full advantage of them.
There are many examples of positive risks in projects: you could complete the project early;
you could acquire more customers than you accounted for; you could imagine how a delay in
shipping might open up a potential window for better marketing opportunities, etc. It is
important to note, though, that these definitions are not etched in stone. Positive risk can
quickly turn to the negative risk and vice versa, so you must be sure to plan for all eventualities
with your team.
Like everything else on a project, you are going to want to strategise and have the
mechanisms in place to reap the rewards that may be seeded in positive risk.
• The first thing you’ll want to know is if the risk is something you can exploit. That means
figuring out ways to increase the likelihood of that risk occurring.
• Next, you may want to share the risk. Sometimes you alone are not equipped to take
full advantage of the risk, and by involving others you increase the opportunity of
yielding the most positive outcome from the risk.
We have all been conditioned to think of risks as negative, but the risk is a way to safeguard
yourself by preparing for the possibility of failure or danger. If you have prepared for risk,
understand its potential to both serve and derail your project, then risk can help you widen
the aperture and see things that may have beforehand been invisible.
So, how do you handle something as seemingly elusive as project risk management? The same
way you do anything when managing a project. You make a risk management plan. It’s all
about the process.
The process can make the unmanageable manageable. You can take what looks like a
disadvantage and turn it into an advantage if you follow these steps.
One way is brainstorming or even brainwriting, which is a more structured way to get a
group to look at a problem.
As mentioned earlier, you can tap your resources. That can be your team, colleagues or
stakeholders. Find those individuals with relevant experience and set up interviews so
you can gather the information you’ll need to both identify and resolve.
As you’re identifying risk, you’ll want to make sure you that your risk register isn’t filling
up with risks that are really outliers and not risks at all. Make sure the risks are rooted
in the cause of a problem. Basically, drill down to the root cause to see if the risk is one
that will have the kind of impact on your project that needs identifying.
When trying to minimise risk, it’s good to trust your intuition. This can point you to
unlikely scenarios that you just assume couldn’t happen. Remember, don’t be
overconfident. Use the process to weed out risks from non-risks.
When you assess project risk you can ultimately and proactively address many impacts,
such as avoiding potential litigation, addressing regulatory issues, complying with new
legislation, reducing your exposure and minimising impact.
So, how do you analyse risk in your project? Through qualitative and quantitative risk
analysis, of course. What does that mean? It means you determine the risk factor by
how it impacts your project across a variety of metrics.
Those rules you apply are how the risk influences your activity resources, duration and
cost estimates. Another aspect of your project to think about is how the risk is going to
impact your schedule and budget. Then there are the project quality and procurements.
These points must be considered to understand the full effect of risk on your project.
Having a large list of risks can be daunting. But you can manage this by simply
categorising risks as high, medium or low. Now there’s a horizon line and you can see
the risk in context. With this perspective, you can begin to plan for how and when you’ll
address these risks.
Some risks are going to require immediate attention. These are the risks that can derail
your project. Failure isn’t an option. Other risks are important, but perhaps not
threatening the success of your project. You can act accordingly.
Then there are those risks that have little to no impact on the overall project’s schedule
and budget. Some of these low-priority risks might be important, but not enough to
waste time on. They can be somewhat ignored because sometimes you just should let
stuff go.
That determination is up to you. There might be a team member who is more skilled or
experienced in the risk. Then that person should lead the charge to resolve it. Or it might
Think about it. If you don’t give each risk a person tasked with watching out for it and
then dealing with resolving it when and if it should arise, you’re opening yourself up to
more risk. It’s one thing to identify risk, but if you don’t manage it then you’re not
protecting the project.
You’ll want to set up a series of meetings to manage the risks. Make sure you’ve already
decided on the means of communication to do this. It’s best to have various channels
dedicated to communication.
You can have face-to-face meetings, but some updates might be best delivered by email
or text or through a project management software tool. They might even be able to
automate some, keeping the focus on the work.
So much time and effort are put into the planning of a project, it is often forgotten that the
end of a project is equally important. There’s a lot of work involved even once a project is
technically complete.
For example, there are many tasks that you still must complete. They might be procedural,
but that doesn’t make them any less important. There are approvals, signatures, payments,
all of which might seem like pushing paperwork to you, but tell that to the team member
waiting to get paid.
Not to mention, when you are ending one project, you’re likely beginning another. Therefore,
you want to get transition support for this changeover. You’ll have to release resources,
archive documents and don’t forget to acknowledge the project's success with a party or
some type of celebration. That’s important, too.
The close of the project is the final phase of your job, it’s the last turn of the project life cycle,
and like any other aspect of a project, it requires a process. The following are five steps you
should take to make sure you’ve dotted all the I’s and crossed all the T’s, as well as taken full
advantage of the experience.
Gather the core team to invite feedback about what worked and what didn’t. Encourage
honesty. By documenting the mistakes and the successes of the project, you’re building
a catalogue that offers historic data. You can go back and look over the information for
precedents when planning for new projects. Projects are never standalone things, but
part of a continuum, where the specifics might vary, but the general methods usually
remain the same. There’s a wealth of knowledge produced after any project closes.
This includes addressing all outstanding payments. You want to make sure that all
invoices, commissions, fees, bonuses, etc., are paid. Complete all the costs involved
with the project. It’s not done if it’s not paid for.
Before you close a project, archive all the documents and any notes and data that could
prove useful. Even if you never access it, there’s a need to keep a paper trail of the work
done on any project for other people in the organisation. This might include legal teams,
or HR teams, or even your successor. You never know when someone might have to go
back and respond to a question or want to learn how an old issue was resolved. Consider
it like putting away provisions for the winter.
That’s because when you note a job well done, you’re building morale. It makes team
members feel better. You might have been a hard taskmaster in the project, but you
To make sure that every i is dotted and t crossed, follow this step-by-step project closure
checklist.
• Start at the beginning with the project scope document you created and make sure that
you’ve met all the requirements listed there.
• Make sure that all deliverables have been handed off and signed by stakeholders,
getting their approval and satisfaction.
• Other project documents must also be signed by the appropriate person, this includes
any outstanding contracts and agreements with vendors and other contractors.
• Once documents are signed off on, then process them and pay off all invoices and close
out any project-related contracts.
• Add all documents together, including finalising all project reports, then organise and
archive them as historical data to be used for future reference.
• Use collected paperwork to identify and document the lessons learned over the course
of the project, including any feedback from stakeholders, so you don’t make the same
mistakes in future projects.
• Assign a transition support person to shepherd the project after completion so that the
project closure is thorough.
• Release or reassign the project resources, which includes your team and other project
personnel and any equipment or site rentals used for the project.
• If you’ve not used project management software program, get one, as it helps control
not only the life cycle of the project but also the process of closing the project
thoroughly.
3.7. Why Ending A Project Properly Makes Your Next Project Better?
Once you’ve closed out the project, you now have the documentation to share and talk about
with your team. You also get an opportunity to hear from the team in a more intimate and
casual way that allows them to express their opinions on the management of the project.
All this information might not be used later, but it’s all useful in that it provides perspective
and gives everyone involved a more rounded view of the project mechanics. Taking the time
to have a post-mortem after the project closure is complete, puts you and your team in a
position to start the next project from a more informed place.
Time to do a progress check to determine whether you have gone through all the required
content and completed all the exercises.
Did you complete all the relevant revision exercises and check your answers
against the answers provided?
2. Do you believe a risk assessment matrix can assist in managing risk? If so, how?
The risk assessment matrix helps the process by organising the identified risks and
assessing the risks' impact, likelihood, degree of impact, the action trigger for the risk,
who is responsible, and the response plan.
3. What types of risk for a project should be given the highest priority? Does the priority
for a risk change as the project progresses?
Risks that have the highest priority are those on the critical path and those that have a
high degree of impact and a high likelihood of occurrence. Yes, the priority of risk can
4. As the project progresses, how does the project risk change? Would you make any
changes to the risk assessment matrix? If so, what changes would you make?
As the project progresses, some initial risks may no longer be a factor and other risks
may be identified that need to be addressed. The risk assessment matrix is adjusted to
update the likelihood of occurrence, the degree of impact, the action trigger, the
responsibility, and the response plan.
5. As part of closing a project, which activities would you perform and why?
The process of closing the project includes collecting and making final payments,
recognising and evaluating staff, conducting a post-project evaluation, documenting
lessons learnt, and organising and archiving project documents. These activities are
important to make sure that the customer is satisfied, to gather information about how
to improve for future projects, to determine whether additional opportunities are
available with the customer, and to obtain permission to use the customer as a
reference.
6. How would you obtain feedback from a customer after a project has been completed?
How would you use this information?
The post-project evaluation can be conducted as a meeting with open-ended questions
or through a customer evaluation survey. The information is used to assess the level of
satisfaction of the customer, opportunities for future work, and permission to use the
customer as a reference.
7. Explain the reasons as to why some projects are terminated before they are
completed. When do you think it would be wise to do so?
The sponsor or customer can terminate a project for a variety of reasons including
changes in financial situation or project return on investment, dissatisfaction with
This study unit focus on the importance of the people involved in a project. It is the people,
not the procedures and techniques, who are critical to achieving the project objective.
Procedures and techniques are merely tools that help people do their jobs.
A project manager is a person who has the overall responsibility for the successful initiation,
planning, design, execution, monitoring, controlling and closure of a project. The project
manager must have a combination of skills including an ability to ask penetrating questions,
detect unstated assumptions and resolve conflicts, as well as more general management
skills.
Key among a project manager's duties is the recognition that risk directly impacts the
likelihood of success and that this risk must be both formally and informally measured
throughout the lifetime of a project. Risks arise from uncertainty, and the successful project
manager is the one who focuses on this as his/her primary concern. Most of the issues that
impact a project result in one way or another from risk. A good project manager can lessen
risk significantly, often by adhering to a policy of open communication, ensuring every
significant participant has an opportunity to express opinions and concerns.
A project manager is also responsible for making decisions, both large and small. The project
manager should make sure he/she controls risk and minimises uncertainty. Every decision the
project manager makes must directly benefit the project.
But the project manager cannot do it alone. An effective project team is needed. The project
team comprises those people who have a role in the same project. Team members can be
grouped but each individual has a certain role and function and thus can be assigned certain
tasks. The project team fulfils these roles and functions within the time frame of the project
Good cooperation among the project team is vital for project success. Especially
communicating efficiently and effectively is important to ensure that everyone has the
necessary information to complete his/her tasks and fulfil his/her role properly. Ideally,
opinions, solutions and also conflicts are considered, debated and resolved within the project
team.
Leading a project towards success requires the manager to get the work done by the team
members efficiently and effectively. It requires the person to have a clear vision, clarity in
reason, be practical in scheduling and have the ability to attract a talented and efficient team.
The stress in project management is about ensuring that things get done while motivating the
project team towards delivering project success. Good leadership can be cultivated and
modified as per the organisational culture so as to gain results.
The basic distinction between the manager focus and the leadership focus can be captured
as given below:
The application of leadership and management in the project execution is usually dependent
on the type of project and the life cycle stage that the project is in. For projects which are
huge impact, large scale, complex and global in nature the standards to be achieved, the goals
and the deliverables are constrained by the time frame, budgets and market dynamics. These
types of projects involve large and distributed project teams, comprising members from
diverse disciplines. Also, the implementation is going to be multi-phased. In such a situation
the project success and business sustenance can be achieved only through effective and smart
leadership.
The leadership style should be flexible, sharing, and innovative so as to bring about the
project's success. At the same time, the leader should emphasise team building and
motivation so that the divergent members can work together as a team.
During the planning phase of the project, the leader should lead the team and the
stakeholders through a fine-tuned project study so as to understand the project needs. This
phase needs to be stressed so as to gain complete awareness of the requirements. Similarly,
the project leader has a pivotal role to play in change management. A good leader should be
able to anticipate the change and address it effectively. The leader should be able to steer
and direct the team members on the methods to cope with change and utilise change to one’s
advantage.
Most importantly the leader should be able to give credit, nurture creativity and support team
members in taking calculative risks so as to deliver project success.
Researchers concur that team selection should consider two critical questions:
• Are the skills required for the team’s task represented in the selected members?
• Do the selected team members possess the skills necessary for effective collaboration
and interaction among them?
Therefore, project parameters that are likely to influence team selection and composition
must be identified before choosing individual members of the team. Team member selection
should focus initially on selecting a potential membership pool based first on task skills and
then on teamwork skills and not the other way around. Knowing one another and familiarity
is no good if the task cannot be completed as per specification.
When choosing individuals to staff a team, the goal is to simulate high output by the team.
Task parameters associated with the emerging projects are likely to influence the need for
various personnel capabilities in teams, for example, change management projects may
require a greater emphasis on certain communication skills or an assignment that has a very
tight deadline for completion may require greater familiarity among team members. Thus,
The goal of this step is to identify a possible pool of team members based on the task skills
needed for team effectiveness. Task skills refer to the individual capabilities that enhance
one’s ability to act effectively in broadly defined performance task domains. Accordingly, such
skills are transportable across teams and performance domains. Different team members
have different levels of different skills, but the team, as a whole would possess all required
task skills.
In addition to this, one needs to look at teamwork skills. Teamwork skills refer to the
capabilities to work effectively in any generic team environment, regardless of the task. The
possession of these skills should be a second factor to weigh when considering individuals for
team membership. Teamwork skills reflect fundamental requirements for collaboration and
integrated action on team tasks.
Building stronger teams by facing your differences. Extinguish any ‘fireworks’ in your team by
resolving conflict quickly. Conflict is pretty much inevitable when you work with others.
Conflict isn't necessarily a bad thing, though. Healthy and constructive conflict is a component
of high-functioning teams. Conflict arises from differences between people, the same
differences that often make diverse teams more effective than those made up of people with
similar experiences. When people with varying viewpoints, experiences, skills and opinions
are tasked with a project or challenge, the combined effort can far surpass what any group of
similar individuals could achieve. Team members must be open to these differences and not
let them rise into full-blown disputes.
Understanding and appreciating the various viewpoints involved in the conflict are key factors
in its resolution. These are key skills for all team members to develop. The important thing is
to maintain a healthy balance of constructive differences of opinion and avoid negative
conflict that's destructive and disruptive.
Getting to, and maintaining, that balance requires well-developed team skills, particularly the
ability to resolve conflict when it does happen, and the ability to keep it healthy and avoid
conflict in the day-to-day course of the team working.
When a team oversteps the mark of a healthy difference of opinion, resolving conflict requires
respect and patience. The human experience of conflict involves our emotions, perceptions,
The three-stage process below is a form of the mediation process, which helps team members
to do this:
Discuss the impact – as a team, discuss the impact the conflict is having on team
dynamics and performance.
Agree to communicate – the most important thing throughout the resolution process is
for everyone to keep communications open. The people involved need to talk about the
issue and discuss their strong feelings. Active listening is essential here because to move
on you need to really understand where the other person is coming from.
Once the team is ready to resolve the conflict, the next stage is to understand the
situation and each team member's point of view. Take time to make sure that each
Sally and Tom believe the best way to market the new product is through a TV
campaign. Mary and Beth are adamant that Internet advertising is the way to go, whilst
Josh supports a store-led campaign.
List facts, assumptions, and beliefs underlying each position – what does each group or
person believe? What do they value? What information are they using as a basis for
these beliefs? What decision-making criteria and processes have they employed?
Sally and Tom believe that TV advertising is best because it has worked very well in the
past. They are motivated by the saying, "If it ain't broke, don't fix it."
Mary and Beth are very tuned-in to the latest in technology and believe that to stay
ahead in the market, the company has to continue to try new things. They seek
challenges and find change exhilarating and motivating. Josh believes a store-lead
campaign is the most cost-effective. He is cautious and feels this is the best way to test
the market at launch, before committing the marketing spend.
Analyse in smaller groups – break the team into smaller groups, separating people who
are in alliance. In these smaller groups, analyse and dissect each position, and the
associated facts, assumptions and beliefs.
By considering the facts, assumptions, beliefs and decision making that lead to other
people's positions, the group will gain a better understanding of those positions. Not
only can this reveal new areas of agreement, but it can also reveal new ideas and
solutions that make the best of each position and perspective.
Take care to remain open, rather than criticise or judge the perceptions and
assumptions of other people. Listen to all solutions and ideas presented by the various
sides of the conflict. Everyone needs to feel heard and acknowledged if a workable
solution is to be reached.
Convene back as a team – after the group dialogue, each side is likely to be much closer
to reaching an agreement. The process of uncovering facts and assumptions allows
people to step away from their emotional attachments and see the issue more
objectively. When you separate alliances, the fire of conflict can burn out quickly, and
it is much easier to see the issue and facts laid bare.
Now that all parties understand the others' positions, the team must decide what
decision or course of action to take. With the facts and assumptions considered, it's
easier to see the best of action and reach an agreement.
In our example, the team agrees that TV advertising is the best approach. It has had
undeniably great results in the past and there is no data to show that will change. The
message of the advertising will promote the website and direct consumers there. This
If further analysis and evaluation are required, agree what needs to be done, by when
and by whom, and so plan to reach agreement within a particular timescale. If
appropriate, define which decision making and evaluation tools are to be employed.
If such additional work is required, the agreement at this stage is to the approach itself:
Make sure the team is committed to working with the outcome of the proposed analysis
and evaluation.
When conflict is resolved take time to celebrate and acknowledge the contributions
everyone made toward reaching a solution. This can build team cohesion and
confidence in their problem-solving skills and can help avert further conflict.
As well as being able to handle conflict when it arises, teams need to develop ways of
preventing conflict from becoming damaging. Team members can learn skills and behaviour
to help this. Here are some of the key ones to work on:
• Dealing with conflict immediately – avoid the temptation to ignore it.
• Being open – if people have issues, they need to be expressed immediately and not
allowed to fester.
• Practicing clear communication – articulate thoughts and ideas clearly.
• Practicing active listening – paraphrasing, clarifying, questioning.
• Practicing identifying assumptions – asking yourself ‘why’ on a regular basis.
• Not letting conflict get personal – stick to facts and issues, not personalities.
• Focusing on actionable solutions – don't belabour what can't be changed.
1. Using examples, explain how a project manager performs the planning, organising and
controlling functions for a project.
2. Explain why good verbal and written communication skills are important to project
managers.
3. How can a project manager help create an environment in which a project team feels
motivated?
4. Explain each of the stages of team development by addressing the process, problems,
and level of productivity of each stage.
5. Do you agree or disagree with the statement that there is ‘no I in TEAM’? What steps
can you take to be an effective team member?
6. Describe the project manager’s role in relation to ethical behaviour of the team. How
can one encourage a high level of ethical behaviour?
Time to do a progress check to determine whether you have gone through all the required
content and completed all the exercises.
Did you complete all the relevant revision exercises and check your answers
against the answers provided?
1. Using examples, explain how a project manager performs the planning, organising
and controlling functions for a project.
The project manager must clearly define the project objective, reach an agreement with
the customer on this objective and communicate this objective to the project team. The
project manager involves the project team in developing the plan and setting up a
system for comparing actual to planned progress. Specific examples will vary. Answers
should include the activities of a project manager performing project planning.
Organising includes securing the appropriate resources to perform the work. The
project manager must decide which tasks should be done in-house and which by
subcontractors or consultants. The project manager gains commitment from the
specific people who will work on the project and assigns responsibility and delegates
authority, thus creating an environment in which the individuals are highly motivated
to work together as a project team. Specific examples will vary. Answers should include
the activities of a project manager organising the project's tasks and resources.
2. Explain why good verbal and written communication skills are important to project
managers.
Communication is the key to success. Project managers need to communicate regularly
with the project team, as well as with the customer, any subcontractors, and their own
company’s upper management. Effective and frequent communication is crucial for
keeping the project moving, identifying potential problems, soliciting suggestions to
improve project performance, keeping abreast of customer satisfaction, and avoiding
surprises.
3. How can a project manager help create an environment in which a project team feels
motivated?
The capable project manager understands what motivates team members and creates
a supportive environment in which individuals work as part of a high-performing team
and are energised to excel. A project manager can create such an environment by
encouraging participation and involvement by all members of the project team.
Techniques include facilitating project meetings so as to draw all individuals into the
discussions, soliciting an individual’s ideas when meeting separately with that person,
and having various team members participate in presentations to the customer or the
company’s upper management. The project manager shows that he or she values the
contributions of each team member and also fosters motivation through recognition of
the project team as a whole and of individual members.
4. Explain each of the stages of team development by addressing the process, problems,
and level of productivity of each stage.
• Forming is the initial stage of the team development process. It describes the
transition from an individual to a team member. Team members generally have
5. Do you agree or disagree with the statement that there is ‘no I in TEAM’? What steps
can you take to be an effective team member?
It is said that ‘there is no ‘I’ in TEAM’, because effective team members put the success
of the project above personal gain.
6. Describe the project manager’s role in relation to the ethical behaviour of the team.
How can one encourage a high level of ethical behaviour?
The project manager must set the tone and expectations and must exemplify ethical
behaviour. If the project team sees the project manager taking actions or making
decisions that are ethically questionable, they will think it is acceptable for them to do
the same thing. The project manager must be committed to always doing what is right
and fair and communicate the same expectations to the project team.
The project manager should discuss the importance of ethical behaviour at a project
team meeting at the beginning of the project and mention it regularly at meetings
throughout the project. Ethical actions, such as a project team member’s raising an
issue about an unsafe design, should be encouraged, acknowledged and appreciated.
Misconduct and conflicts of interest must be addressed and appropriate disciplinary
action is taken to show that such behaviour is unacceptable and will not be tolerated.
Two actions a project organisation can take to help prevent any wrongdoing are to have
a written policy on ethical behaviour and to provide training about ethics in the
workplace.
In order to have effective communication, the project manager must also understand the
project organisation structure wherein the project must be completed. A project organisation
is a structure that facilitates the coordination and implementation of project activities. Its
main reason is to create an environment that fosters interactions among the team members
with a minimum amount of disruptions, overlaps and conflict. One of the important decisions
of project management is the form of organisational structure that will be used for the
project.
Each project has its unique characteristics and the design of an organisational structure
should consider the organisational environment, the project characteristics in which it will
operate, and the level of authority the project manager is given. A project structure can take
on various forms with each form having its own advantages and disadvantages.
One of the main objectives of the structure is to reduce uncertainty and confusion that
typically occurs at the project initiation phase. The structure defines the relationships among
members of the project management and the relationships with the external environment.
The structure defines the authority by means of a graphical illustration called an organisation
chart.
Communication is an essential process in our day-to-day life, and the entire world revolves
around it. Communication is “who says what to whom in what channel with what effect”.
Communication is exchanging of information from one point of the project to the other point
in an efficient manner. Communication is an essential tool in the field of project management.
The success of a project largely depends on the efficiency of its communication network. It
starts working from day one of the ventures and continues for the entire life span of the
project. It provides regular updates to notify the status of the project as well as its
performance capacity. But surprisingly, it has been found that most projects experience a
breakdown in communications. It has been said that 90% of a project manager's time is spent
communicating what is going to be done.
• The techniques to enhance personal verbal and written communication are fully
discussed and correctly applied to a project scenario.
• Accurately describe four barriers to effective listening
• The techniques to improve listening and understanding are correctly applied to a
project scenario.
• The preparation and facilitation of an effective project meeting are correctly explained
within the context of a project task.
• An agenda for a given scenario is correctly designed.
• The preparation and making of informative and interesting presentations are accurately
explained and demonstrated using a case study.
• A useful, readable, and understandable project report is drafted from a project
scenario.
• The controlling of changes to project documents is correctly explained.
• A project communication plan is correctly designed from given information
• The tools for collaboration and enhancement of communication are identified and
correctly applied to appropriate scenarios.
4.
This section covers Chapter 12 of Gido, Clements & Harinarain (2018).
Communication is an essential process in our day-to-day life, and the entire world revolves
around it. Communication is exchanging of information from one point of the project to the
other point in an efficient manner. Communication is an essential tool in the field of project
management. The success of a project largely depends on the efficiency of its communication
network. It starts working from day one of the venture and continues for the entire life span
of the project. It provides regular updates to notify the status of the project as well as its
performance capacity. But surprisingly, it has been found that most projects experience a
breakdown in communications. It has been said that 90% of a project manager's time is spent
communicating what is going to be done.
The word communication comes from the Latin word communis, which means common.
When we communicate, we are trying to establish ‘commonness’ with someone. That is, we
are trying to share information, an idea, or an attitude among the team involved in that
particular project.
One can never take for granted that the receiver will interpret the message the same way as
the sender intended it. Communication is not an absolute, finite thing. To do this effectively,
the project manager needs to consider all the factors like the different realities, the space the
communication takes place in, verbal as well as non-verbal messages, and the intended
meaning versus the perceived meaning, etc. Figure 1 depicts the cost of bad communication.
To understand the communications process, project managers must understand all the
relevant factors.
• The communications process requires a sender and receiver. The sender formulates the
message to communicate, which is meant for a receiver. The sender creates the content
with some intent in mind. The receiver, of course, receives the message and then deals
with it according to personal reactions. He or she may accept, revise, or reject the
message. For example, a project manager informs the customer that a slide on a major
milestone will occur and provides reasons. The customer, in turn, may make a decision
based upon that information.
• The communications process requires a medium to communicate the content of a
message. The medium may take just about any form, each unique in its ability to
influence the receptivity of the receiver. As with the message itself, the receiver may
elect to accept or reject the medium employed. The receiver may even elect to alter the
medium so that he or she can receive and interpret the message according to his or her
preferences. In the earlier example with the schedule slide, a project manager may send
the message as email rather than have a face-to-face meeting with the customer.
• The communications process requires a message. The message can take many different
forms, usually in hard or soft format. The hard format is usually written on paper
whereas soft format is electronic. Regardless of the format, a message is necessary to
initiate communication and stimulate a relationship between two or more people. In
the previously mentioned example, the message is that the project will slide a major
milestone and it is sent in a soft (e.g., electronic) format.
• The communications process requires feedback between the sender and the receiver.
Feedback may be positive, negative, or neutral, indicating the receptivity of the sender
or receiver. Feedback can also be simple or complex. Simple feedback occurs when it
involves just two people; complex feedback is when the process involves three or more
people. The movement from simple to complex is because the number of channels and
opportunities for misinterpretation increases geometrically as each one codes their
message and the other decodes the same. In the last example, the customer gives
The basic communication model is explained here using a facsimile (fax) machine as an
example:
Figure 2 explains how communication moves from one person to another. If we imagine each
portion of the model as a fax machine, it would be easier to visualise the components.
• Sender: This refers to the person who first initiates communication. Let's say a
document related to the project is being faxed by the project manager.
• Encoder: This device encodes the message to be sent. In this case, it is the fax machine.
• Medium: This is the device or technology to transport the message between the
encoder and the decoder. Here it is the telephone line.
• Decoder: This device decodes the message to be received. Here it is the fax machine
itself.
• Receiver: This refers to the person who receives the communication finally. The
receiver may interpret the information, make a comment, and send it back to the
sender.
• Feedback: The communication may be disrupted by noise and misinterpret the
message. A part of the message may be faded out or discolored, etc. This would have
been caused by the distortion of the telephone line.
Communication is a vital element of a well-managed project. There are two main groups of
people with whom the project manager needs to ensure clear and effective communication,
the stakeholders and the project team. Every project will be sponsored by a part of the
business with a stake in the outcome. They will likely be represented on the project board,
which sets the objectives for the project and monitors progress over time. The project board
will include others with a stake in the outcome, for example, those who will need to
implement the project outcomes and those who will need to supply resources once the
project outcomes have been met. All of these stakeholders will need regular updates, and it
is imperative that communication with them is regular, clear and complete.
In addition, projects often involve the need for the project manager to coordinate the work
of a large group of people working on different aspects of the project (often referred to as
workstreams). The project manager is required to ensure that everyone is clear about what
he or she must achieve and he or she also needs to clearly report on progress to the project
board and/or project sponsors. There are many opportunities for things to go badly wrong if
effective communication is not established and maintained.
The following steps will help the project manager to communicate effectively:
Based on stakeholder analysis, the project manager and the project team can determine
the communications that are needed. There is no advantage of supplying stakeholders
with information that isn't needed or desired, and the time spent creating and
delivering such information is a waste of resources.
The communications plan may also include information and guidelines for project status
meetings, team meetings, e-meetings (electronic meetings) and even email. Setting
expectations for communications and meetings early in the project establishes
guidelines for the project team and stakeholders.
First, the team to whom communication is essential needs to determine the number of
channels of communication possible using the communication formula as illustrated in
Project Management Institute (2008). This is a very simple equation that any good
program and project manager should know which is: N(N-1)/2.
Using the formula, let us take an example with a small project team of five people where
the formula calculates that there are 10 possible channels of communication as:
5(5-1)/2 = 5(4)/2 = 20/2 = 10. So, the project manager must ensure that five people on
the team are communicating in real-time and that there are no gaps in everyone's'
understanding that they need to manage only 10 communication channels among the
team.
Stakeholders will need different types of information, depending on their interest in the
project and the priority of the project. The project manager will need to complete the
analysis of the identified stakeholders to determine what information they actually
need as well as how often the information is needed. The project manager and the
project team can identify the demand for communications using the following:
• Organisation charts
• The project structure within the performing organisation
• Stakeholder responsibility relationships
• Departments and disciplines involved within the project work
• The number of individuals involved in the project and their locales
• Internal and external information needs
• Stakeholder information.
These enterprise factors should be identified and reviewed and the project manager
should align his or her project initiative considering all of these factors.
These process assets may be unique for each organisation, but if this is reviewed before
the initiation of the project and reflected in the communication to the team, then there
will never be a problem throughout the project.
The main communication obstacles (across interfaces listed earlier) can be drilled down to
the following three broad areas:
• Political: Whenever there are many groups involved, there is the possibility of vested
interests and power games getting in the way of dialogue. Such political obstacles
usually originate in the upper ranks of an organisational hierarchy, a step or two above
levels at which projects are planned and executed. Project managers need to be aware
of the key political players in the organisation. In traditional corporate environments,
these might be functional or senior-level managers who are not always obvious project
stakeholders. Once the political players have been identified, the project manager
should take steps to gain their confidence and buy-in on project goals. This should help
There are many different avenues a project manager and a project team can take to
communicate. Project teams can effectively communicate through hallway meetings or
formal project status meetings. Information can be transferred from stakeholder to
As part of the communications planning, the project manager should identify all of the
required and approved methods of communicating. Some projects may be highly sensitive
and contain classified information that not all stakeholders are privy to, while other projects
may contain information that is open for anyone to explore. Whatever the case, the project
manager should identify what requirements exist, if any, for the communication modalities.
Communication modalities can also include meetings, reports, memos, emails, etc. The
project manager should identify the preferred methods of communicating based on the
conditions of the message to be communicated. Consider the following, which may have an
effect on the communication plan:
• Urgency of the information: When the information is communicated can often be as
important as what is being communicated. For some projects, the information should
be readily available, while other projects are less demanding.
• Technology: Because of the demands of the project, technology changes may be
needed to fulfill the project request. For example, the project may require an internal
website that details project progress. If such a website does not exist, time and money
will need to be invested in this communication requirement.
• Project staffing: The project manager should evaluate the abilities of the project team
to determine if appropriate levels of competency exist to fulfill the communication
requirements or if training will be required for the project team.
• Project length: The length of the project can have an influence on project technology.
Advances in technology may replace a long-term project's communication model. A
short-term project may not have the same technical requirements as a long-term
project but could benefit from the successful model a larger project uses.
• Project environment: How a team communicates often depends on its structure.
Consider a collocated team versus a virtual team. Each type can be effective, but there
will be differing communication demands for each type of team.
• Fax: This is not recommended, as it is not possible to confirm if the sent fax was received
until the receiver confirms.
The most common type of communication between a sender and a receiver is verbal
communication. When verbal communication is involved, the project manager should
Today in this globalised world, communication between diverse groups is a major challenge.
However, communication within a diverse workgroup can create complex and challenging
situations. People with varying perspectives and experiences have different meanings and
contexts for words and phrases. They also use nonverbal expressions differently. What is
appropriate to one person may be offensive to another.
Know who you are communicating with. What is the background of each team member?
What are their experiences and how do they shape the team members' views, opinions,
perspectives and biases? It is imperative to keep an open and flexible mind.
Recognising differences means acknowledging and respecting individuals for who they
are, but it does not necessarily imply agreement with their perspectives, nor is it a
like/dislike dimension.
You (the sender) need to consider how you are different from the intended audience.
What is your background and experience, and how does the past shape your views?
What are your opinions and biases? Communication is a two-way process, and you, as
the sender, play an important role.
Your message can be delivered in many different ways such as written documents, a
team meeting, voice mail, email, or face-to-face communication. Each communication
mode has its own advantages and disadvantages. Select the type that will maximise the
successful delivery of your message given the diversity issues involved. Knowing your
audience can greatly help determine when and how to deliver the message.
You will want to check for understanding and ensure that your message was accurately
received. The important point is to ensure accurate comprehension, not necessarily
agreement.
The overall content of this study guide is based on the prescribed textbook of this module:
Gido, J., Clements, J.P. & Harinarain, N. (2018) Successful Project Management. CENGAGE.
Alphabetical list
Anstey, M. (1991) Negotiating Conflict. Kenwyn: Juta.
Armstrong, M. (1994) Performance Management. London: Kogan Page.
Belout, A. (1998) “Effects of human resource management on project effectiveness and
success: toward a new conceptual framework”, International Journal of Project Management,
16(1), pp. 21-26.
Boddy, D. & Buchanan, D. (1992) Take the Lead: Interpersonal Skills for Project Managers.
New York: Prentice-Hall.
Caroll, A.B. & Buchholtz, A.K. (2012) Business and Society: Ethics and Stakeholder
Management. 8th ed. Mason, OH: South-Western College.
Farrow, E. (2013) “Ethical practice in project management”. Available from:
<http://projectmanager.com.au/ethical-practice-in-project-management>. [Accessed on 9
October 2019]
Lewis, J.P. (1998) Team-based Project Management. New York: Amacom.
Martin, P.K. & Tate, K. (n.d.) “The high-performing team”, PM Network, 13(8), pp. 22-38.
Maylor, H. (1996) The Project Manager’s Desk Reference. New York: McGraw-Hill.
Meredith, J.R. & Mantel, S.J. (2000) Project Management: A Managerial Approach. New York:
John Wiley & Sons.
Pinto, J.K, Thoms, P., Trailer, J., Palmer, T. & Govekar, M. (1998) Project Leadership from
Theory to Practice. Pennsylvania: Project Management Institute.
Project Management Institute. (2019) A Guide to the Project Management Body of
Knowledge, PMBOK® Guide. 6th ed. Project Management Institute.