Professional Documents
Culture Documents
1. Project Attributes
• A project has distinctive attributes that distinguish it from ongoing work or business
operations.
• Projects are temporary in nature - have definitive start dates and end dates.
• A large part of the project effort is dedicated to ensuring that the project is completed
at the appointed time.
○ To do this schedules are created showing when tasks should begin and end.
○ Projects can last minutes, hours, days, weeks, months, or years.
○ Projects exist to bring about a product or service that hasn’t existed before.
○ In this sense, a project is unique, new, this has never been done before.
• 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 organization 20 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 the product or service of the project is no longer needed and the project is
cancelled.
2. Definition of a project
• Project: a temporary endeavor undertaken to create a unique product, service, or
result.
• The end is reached when the project’s objectives have been achieved or when the
project is terminated because its objectives will not or cannot be met, or when the
need for the project no longer exists.
3. Project Characteristics
• When considering whether or not you have a project on your hands, there are some
things to keep in mind.
○ First, is it a project or an ongoing operation?
○ Second, if it is a project, who are the stakeholders?
○ And third, what characteristics distinguish this endeavor as a project?
• Projects have several characteristics:
○ Projects are unique.
○ Projects are temporary in nature and have a definite beginning and ending date.
○ Projects are completed when the project goals are achieved or it’s determined
the project is no longer viable.
• A successful project is one that meets or exceeds the expectations of the stakeholders.
• To examine the assignment you can ask:
○ Is it unique?
○ Does the product have a limited timeframe?
○ Is there a way to determine when the project is completed?
○ Is there a way to determine stakeholder satisfaction?
Figure 2.2 A schematic of the triple constraint triangle. The triad constraints by John
M. Kennedy T.
6. Application Knowledge
• Standards: guidelines or preferred approaches that are not necessarily mandatory.
• Regulations: mandatory rules that must be followed, such as government-imposed
requirements through laws
• Every industry has standards and regulations. Knowing which ones affect your project before
you begin work will not only help the project to unfold smoothly, but will also allow for
effective risk analysis.
• Application areas are made up of categories of projects that have common elements.
○ They can be defined by industry group (pharmaceutical, financial, etc.),
department (accounting, marketing, legal, etc.), technology (software
development, engineering, etc), or management specialties (procurement,
research and development, etc.).
• These application areas are usually concerned with disciplines, regulations, and the
specific needs of the project, the customer, or the industry.
9. Interpersonal Skills
• Ability to manage personal relationships and deal with personnel issues as they arise.
• Required skills: communication, influence, leadership, motivation, negotiation and
problem solving.
Communication
• they must be good communicators, promoting clear, unambiguous exchange of
information.
• it is your job to keep a number of people well informed.
• It is essential that your project staff know what is expected of them: what they have to
do, when they have to do it, and what budget and time constraints and quality
specifications they are working toward.
• If project staff members do not know what their tasks are, or how to accomplish them,
then the entire project will grind to a halt.
• If you do not know what the project staff is (or often is not) doing, then you will be
unable to monitor project progress.
• Finally, if you are uncertain of what the customer expects of you, then the project will
not even get off the ground.
• Project communication can thus be summed up as knowing “who needs what
information and when” and making sure they have it.
• Not all projects will have the same types of communication or the same methods for
distributing the information.
○ For example, will information be distributed via mail or email, is there a shared
website, or are face-to-face meetings required?
○ The communication management plan documents how the communication
needs of the stakeholders will be met, including the types of information that will
be communicated, who will communicate them, and who will receive them;
○ the methods used to communicate; the timing and frequency of communication;
the method for updating the plan as the project progresses, including the
escalation process; and a glossary of common terms.
Influence
• Project management is about getting things done.
• Every organization is different in its policies, modes of operations, and underlying
culture.
• There are political alliances, differing motivations, conflicting interests, and power
struggles.
• A project manager must understand all of the unspoken influences at work within an
organization.
Leadership
• Leadership is the ability to motivate and inspire individuals to work toward expected
Negotiation
• Project managers must negotiate for the good of the project.
• In any project, the project manager, the project sponsor, and the project team will
have to negotiate with stakeholders, vendors, and customers to reach a level of
agreement acceptable to all parties involved in the negotiation process.
Problem Solving
• Problem solving is the ability to understand the heart of a problem, look for a viable
solution, and then make a decision to implement that solution.
• The starting point for problem solving is problem definition.
• Problem definition is the ability to understand the cause and effect of the problem;
this centers on root-cause analysis.
○ If a project manager treats only the symptoms of a problem rather than its cause,
the symptoms will perpetuate and continue through the project life. Even worse,
treating a symptom may result in a greater problem.
○ For example, increasing the ampere rating of a fuse in your car because the old
one keeps blowing does not solve the problem of an electrical short that could
result in a fire.
○
• Root-cause analysis looks beyond the immediate symptoms to the cause of the
symptoms, which then affords opportunities for solutions.
○ Once the root of a problem has been identified, a decision must be made to
effectively address the problem.
○ Solutions can be presented from vendors, the project team, the project manager,
or various stakeholders.
○ A viable solution focuses on more than just the problem; it looks at the cause
and effect of the solution itself.
In addition, a timely decision is needed or the window of opportunity may pass