Pom 1 1
Pom 1 1
Project
A project is defined as a sequence of tasks that must be completed to attain a certain outcome. According
to the Project Management Institute (PMI), the term Project refers to ” to any temporary endeavor with a
definite beginning and end”. Depending on its complexity, it can be managed by a single person or
hundreds.
Characteristics of a project
A project is a set of interdependent tasks that have a common goal. Projects have the following
characteristics:
1. A clear start and end date – There are projects that last several years but a project cannot go on
forever. It needs to have a clear beginning, a definite end, and an overview of what happens in
between.
2. A project creates something new – Every project is unique, producing something that did not
previously exist. A project is a one-time, once-off activity, never to be repeated exactly the same
way again.
3. A project has boundaries – A project operates within certain constraints of time, money, quality,
and functionality. We’ll see more about this in later sections.
4. A project is not business as usual – Projects are often confused with processes. A Process is a
series of routine, predefined steps to perform a particular function, say, expense reimbursement
approvals. It’s not a one-off activity. It determines how a specific function is performed every single
time.
The diverse nature of projects
Projects come in a wide range of shapes and sizes. A project can:
• Be big: Like the construction of the Hoover Dam, take years to complete, and have a humongous
budget.
• Be small: Like your weekend project of installing a pathway in your lawn
• Involve many people: Like planning a wedding
• Just yourself: rearranging the photos in your wedding album
Types of projects
Projects can be diverse in the ways in which they are implemented. Here are some examples of projects:
1. Traditional projects: These are run sequentially in phases. These phases are typically initiation,
planning, execution, monitoring, and closure. Most high-cost infrastructure projects make use of
traditional project management.
2. Agile projects: These are used mainly in software development. They are people-focused and
adaptive. They also typically have short turnaround times.
3. Remote projects: Remote project management is usually used by distributed teams that seldom
meet in person. Handling freelance contributors is an example of a remote project.
4. Agency projects: Agency projects are outsourced to an agency that is likely to have projects with
multiple clients. Marketing and design projects are commonly outsourced to agencies.
The boundaries of a project
Every project operates within certain boundaries called constraints:
• Project scope • People
• Project schedule • Resources.
All of these project constraints depend on what the project aims to achieve and when. The outcome of a
project results in deliverables. Anything that’s produced during the project’s development such as
documents, plans, and project reports is considered a deliverable. A deliverable may also be the result of
the project itself.
Having a final deliverable, as well as a finite timespan, distinguishes project management from business-
as-usual operations. Since projects are unlike routine operations, most people involved are those who
usually don’t work together. Sometimes, the professionals involved will come from different organizations
and geographies. If the desired outcome is achieved on time and within budget, a project is considered to
be a success.
Project life cycle – 5 Phases
Often, projects are divided into five project phases each of which comes with a distinct set of tasks,
objectives, and a particular deadline. Dividing a project into different phases enables teams to stay on track
throughout their entire life cycle.
1. Initiation
The first phase in a project’s life cycle is called project initiation. Here, a project officially launches. It is
named, and a broad plan is defined. Goals are identified, along with the project’s constraints, risks, and
shareholders. At this point, shareholders decide if they want to commit to the project.
Depending on the project, studies may be conducted to identify its feasibility. For IT projects, requirements
are usually gathered and analyzed during the initiation phase.
This phase involves making the case for the project to convince the project stakeholders. A Project
Initiation Document (PID) is created with basic information about the project including probable resource
use and feasibility.
The project initiation phase marks the onset of projects. Typically, a project will be initiated in response to
an opportunity that needs to be explored or a problem to be solved. By then, a cost-benefit analysis should
have been conducted.
Part of the cost-benefit analysis includes conducting a feasibility study, defining the project scope,
establishing the project deliverables, and the stakeholders involved to build a business case.
In this phase, the project charter becomes the most critical document as it outlines:
• The vision and mission of the business
• Goals of the project and the value it will deliver to the business
• A list of all the stakeholders involved in the project
• Project deliverables
• Project scope and budget
• Anticipated risks
Once all these details have been verified and the project approved, the project officially kicks off, project
teams assemble, and planning begins.
2. Planning
A roadmap that will guide teams from creating a project plan throughout the project’s execution and closure
phases is developed comprehensively during the planning stage. Deadlines must be set, and resources must
be allotted. Breaking down tasks into smaller, manageable activities makes it easier to manage project
risks, costs, quality, time, and so on.
This phase occurs once a project has received approval from stakeholders. This is a critical phase that
involves a myriad of tasks including contingency planning, allocating tasks, and planning resource sharing.
At the same time, breaking down tasks into digestible pieces will empower everyone involved to
accomplish the project on time and stay within budget.
During project planning, it is essential for the project manager to understand the project requirements and
objectives. The planning phase is the most critical stage for any project as planning impacts the project’s
risk and outcomes.
During the planning phase, a project plan is developed to provide all stakeholders with the roadmap for the
project. It outlines all the activities, tasks, timelines, roles, costs, milestones, deliverables, and other
dependencies required to execute the project successfully.
The project plan is crucial during the execution, monitoring, and closing phases of the project as it details
not only the project goals and objectives but also the ‘how to’ and the ‘who does what’ during
implementation.
The following documents are prepared during the planning phase:
• Scope statement
• Work breakdown structure (WBS)
• Project plan
• Project schedule
• Change request management
• Communication plan
• Project quality plan
• Acceptance plan
3. Execution
The project plan is implemented during the project execution phase. At this point, teams will work on the
deliverables to ensure that the project meets the necessary requirements.
Everyone usually gathers for a meeting to mark the official start of the project, where teams can get
acquainted with each other and discuss their roles in the success of the project. Modes of communication
and project management tools are identified before the project plan is executed.
This is the phase when the actual work happens. Periodical reviews are conducted to ensure that execution
happens within schedule. In addition, team members familiarize themselves with the necessary status
meetings and reports that will be conducted throughout this phase to collect project metrics. The project
execution phase is a critical point in a project’s life cycle as it will help everyone determine if their efforts
will ultimately be fruitful or not.
Project planning and execution are two of the essential phases in achieving the goals of a project. The
execution phase is typically the longest and takes up the biggest allocation of resources as the actual
implementation of the project is done. At this point, controlling the project’s resources, monitoring the
project’s progress, and maintaining clear communication among all the stakeholders becomes crucial.
The project team uses the WBS and the project schedule to execute the tasks outlined in the project plan.
Also, frequent team meetings are held to report the project progress, evaluate variances in the project, as
well as address change requests, and update the project plan in case of any. The project manager ensures
that he keeps all stakeholders up to date on the project’s progress through status reports. Communication
should be appropriate as indicated in the communication plan. Once the deliverables have been produced,
the final product delivered and accepted by the customer following the acceptance criteria, the project is
ready for closure
4. Monitoring and Controlling
The project monitoring and controlling phase happen at the same time as the execution phase. It’s the job
of the project manager to oversee operations and make sure that everything is headed in the right direction,
according to plan.
Monitoring happens in tandem with execution. Constant monitoring by the project manager is required to
ensure that work goes on minus hiccups. Aside from overseeing the project’s performance, project
managers have to monitor resources, manage risks, head status meetings, and reports, etc. If unforeseen
issues arise, the project manager may have to make adjustments to the plans, as well as the project schedule.
Even though monitoring and control are intended to check the entire project management process, it is
handier during the execution phase. Monitoring and controlling are done to ensure that the project moves
in the right direction and within the defined scope. When the project progresses as planned, the risk is
minimized. Ideally, monitoring the project’s actual performance is compared against the planned
performance and the appropriate course of action taken in the event that there is a variance.
5. Closing
The final phase of the project management life cycle known as the project closure phase isn’t as simple as
delivering the output itself. Project managers have to record all deliverables, organize documents in a
centralized location, and hand over the project to the client or the team responsible for overseeing its
operations during the project closure phase.
This phase involves the important final tasks in the project including project delivery to the client and
documenting the learnings from the project. Not only that, but teams come together for a final meeting to
discuss the insights they’ve learned and to reward the hard work of each member.
The project is closed after it has achieved its goals and the product is ready for release and delivery to the
client. This last phase is also known as the follow-up phase, where the project manager and the teams come
together to discuss the project events and insights in a closing meeting. They will recap the entire life cycle
to draw lessons and takeaways from it, identify strengths and opportunities for improvement, and document
them alongside other project data for future reference.
Sometimes, the project is closed before completion, mainly due to failure.
A Project is Considered Successful When
Simply put, a successful project is one that is completed on time, within the budget, and having achieved
its objective(s).
Here are seven pointers of a successful project.
1. Completed on time or before time
2. Executed within the budget
3. Objectives are met
4. Meets or exceeds the expectations of the stakeholders
5. Arising issues were addressed proactively
6. Output is beneficial to the user
7. Positive feedback from the project execution team about how the project was run
Module 2
Project management knowledge areas
Project Management Institute (PMI) has divided the large field of project management into 10 more
digestible parts, which it calls the 10 project management knowledge areas in its A Guide to the Project
Management Body of Knowledge (PMBOK).
Project management knowledge areas coincide with the process groups, which are project initiation, project
planning, project execution, monitoring and controlling, and project closing. These are the chronological
phases that every project goes through.
The knowledge areas take place during anyone of these process groups. You can think of the process groups
as horizontal, while the knowledge areas are vertical. The knowledge areas are the core technical subject
matter, which are necessary for effective project management.
Effective project management requires planning, communication, and task management. But do you know
all the main project management knowledge areas and how they work together?
These 10 project management knowledge areas will provide you with the essential information and skillsets
you need to run smoother projects, delight your stakeholders, and fight fewer fires.
The ten knowledge areas, each of which contains some or all of the project management processes, are:
1. Project Integration Management: the processes and activities needed to identify, define,
combine, unify, and coordinate the various processes and project management activities within the
project management process groups.
2. Project Scope management: the processes required to ensure that the project includes all the work
required, and only the work required, to complete the project successfully.
3. Project Schedule Management: the processes required to manage the timely completion of the
project. Until the 6th edition of the PMBOK Guide this was called "Project Time Management"
4. Project Cost Management: the processes involved in planning, estimating, budgeting, financing,
funding, managing, and controlling costs so that the project can be completed within the approved
budget.
5. Project Quality Management: the processes and activities of the performing organization that
determine quality policies, objectives, and responsibilities so that the project will satisfy the needs
for which it was undertaken.
6. Project Resource Management: the processes that organize, manage, and lead the project team.
Until the 6th edition of the PMBOK Guide this was called "Project Human Resource Management"
7. Project Communications Management: the processes that are required to ensure timely and
appropriate planning, collection, creation, distribution, storage, retrieval, management, control,
monitoring, and the ultimate disposition of project information.
8. Project Risk Management: the processes of conducting risk management planning, identification,
analysis, response planning, and controlling risk on a project.
9. Project Procurement Management: the processes necessary to purchase or acquire products,
services, or results needed from outside the project team. Processes in this area include Procurement
Planning, Solicitation Planning, Solicitation, Source Selection, Contract Administration, and
Contract Closeout.
10. Project Stakeholder Management: the processes required to identify all people or organizations
impacted by the project, analyzing stakeholder expectations and impact on the project, and
developing appropriate management strategies for effectively engaging stakeholders in project
decisions and execution.
Each of the ten knowledge areas contains the processes that need to be accomplished within its discipline
in order to achieve effective project management. Each of these processes also falls into one of the five
process groups, creating a matrix structure such that every process can be related to one knowledge area
and one process group.
Project Integration Management
Project integration management is a project management knowledge area that helps teams work together
more seamlessly. Integration management brings together various processes, systems, and methodologies
to form a cohesive strategy.
To accomplish this, trade-offs must be made. Project goals need to be the guiding star when determining
when and where these trade-offs will take place. They also require buy-in from the full project team and
all stakeholders. Everyone won’t get what they want, but the result will be a project completed on time and
within budget.
Benefits of project integration management.
Achieving project integration of teams and processes can be challenging. However, there are several key
benefits for the progression of your projects.
• Increased accountability from team members.
Aligning project goals means team members should be 100% sure of their responsibilities, and aware of
the importance in managing each one. As team members take on more responsibility, communication loses
clutter and becomes more focused.
• Increasing efficiency.
Integration management means taking an overview across all project teams and analyzing where you can
make efficiencies. Making the most of the resources at your disposal could help save time on tasks and
improve productivity, ensuring team members always have something to do.
• Clearly defined roles with no surprises.
Once a project manager has fully fleshed out the strategy, there should be no (initial) margin for error. Each
team will be aware of its main aims and objectives, and therefore which is responsible for delivering its
part.
Project integration management steps.
Before implementing project integration management processes, you must first gain a clear understanding
of current systems, processes, and methodologies utilized by every team in the project. As a project moves
forward, there are eight primary integration management steps and milestones with corresponding
deliverables:
1. Project charter 5. Manage project knowledge
2. Scope statement 6. Monitor and control project work
3. Project management plan 7. Perform integrated change control
4. Direct and manage project work 8. Close project or phase
• Developing a project charter.
Traditionally, the project sponsor or project manager writes the project charter. It serves multiple purposes
throughout the project life cycle.
This high-level document provides the project manager with the authority to execute the project and likely
won’t require adjustment as work proceeds. It also outlines the initial roles and responsibilities of all team
members and establishes goals and project deliverables.
• Write the scope statement.
Scope statements fulfill one of the most important project aspects — outlining everything included in the
project. It provides a framework for all tasks, which teams execute those tasks, and what deliverables are
needed. While these scope statements occasionally shift throughout the life of a project, it’s vital to keep
them as accurate as possible from the beginning to avoid scope creep.
• Develop a project management plan.
The project management plan brings all aspects of the planning phase together into a single document. It
includes elements such as:
• Project goals • Work breakdown structure
• Budget • Stakeholder management plan
• Risks • Change management plan
• Scope
This fixed plan should not change without a formal change request.
• Direct and manage project work.
Teams complete most of the work associated with a given project in this step of integration management.
This involves:
• Managing resources
• Executing on the work
• Creating changes where necessary
Review performance against project goals throughout the project’s life to make necessary changes and
keep things on track. To avoid scope creep, communicate and stay transparent with every team and
department involved. Use the scope statement as a guidepost to achieve the original intent of the project.
• Manage project knowledge.
What your teams learn as they work on projects can be an invaluable tool for the future. Capturing this
information is an important part of the project integration process. Make the most of the information
available to smooth out the execution. Record anything new you’ve learned in a ‘Lessons Learned
Register’, so the organization can benefit from learnings to make efficiencies on future projects.
Discern the differences between tacit and explicit knowledge and record as much of both as you can. This
way workers don’t need the benefit of psychic powers to grab it from a colleague if they have any questions.
a. Tacit knowledge – The knowledge workers retain without context. That is, without knowing how
they know.
b. Explicit knowledge – The knowledge workers have that can be asked for and formally recorded.
• Monitor and control project work.
This entails the consistent tracking and reporting on progress of the work to stakeholders. It ensures they
have a clear ongoing idea of:
▪ Where the project is heading
▪ Whether it’s on schedule
▪ And on (or preferably under) budget
This aspect of the process is unique, in that it doesn’t really follow during the order we’ve specified.
Instead, it’s something that can be performed throughout the process, to ensure each stage is on track.
Measure performance against the project management plan as a whole, so you get the best overview of
where work may stray off-scope or off schedule.
• Perform integrated change control.
Change control spans the life of a project. The project plan, goals, and scope statement are integral assets
in this iterative process. Never jeopardize the primary project goals with revisions made during this process
and take corrective action when any change strays too far from the plan. Request and document any changes
through an official process and avoid ad-hoc changes to minimize scope creep. The project manager
appoints members of a control board who help evaluate change requests and outline next steps.
• Close project or phase.
This is where successful projects wrap up. This step involves reviewing various aspects of the project and
documenting findings to a reference archive. Some project teams find it useful for each member to rate the
project execution and management in an official post-mortem review meeting.
Project Scope Management
In today’s fast-paced, modern workplace, work is increasingly completed and managed digitally and
remotely, with communication spread across multiple mediums. In the midst of all this chaos, it is
imperative to have an effective project scope management plan in place.
Project scope management is the process that defines and outlines all of the work that is included within a
project, including its:
• Objectives • Deadlines
• Tasks • Budgets
• Outputs
It’s an essential part of the project planning process and clearly determines what you and your team will
need to do in order to deliver a product, service, or result with specified functions and features. It includes
everything that must go into a project, as well as what defines its success. Without a comprehensive scope
management plan, there’s a good chance your team is doing work that’s unnecessary to complete the project
at hand or even wasting time thinking about what they should be doing next.
The importance of project scope management.
The project scoping process is essential to keeping your work on track, regardless of setbacks, variables
and ad hoc requests that may impact the process.
For example, many of us may start a project with a clear plan, but influential stakeholders, clients and
colleagues may have a different idea of what success looks like. What’s more, business priorities can shift
throughout the course of a project and throw it off course.
A solid scope management process can help you strike the right balance between outcomes, expectations
and business priorities. It helps you keep discipline in your project and ensure it stays true to its initial
concept.
By learning how to manage project scope effectively, you can:
a. Ensure your project sticks to deadline, budget and specification.
b. Avoid scope creep, when your project swerves outside of its agreed parameters.
c. Decide on what is and isn’t needed for your project in advance.
d. Identify elements of your project that may be subject to change.
Steps of project scope management.
To help you get your team working on more of the right work, here’s a step-by-step guide to some key
project scope management processes.
1. Plan Your Scope.
When you start project planning, you want to gather input from all of the project stakeholders. This
stakeholder management stage is essential, as together you will decide and document how you want to
define, manage, validate, and control your project scope.
The scope management plan also includes information on how you will:
•Handle unforeseen circumstances – You can outline how you will deal with ad-hoc projects
throughout, including how resource will be allocated and timelines amended.
• Accept project deliverables – How agreed deliverables will be accepted and processed by your
team – outlining roles and responsibilities for who is handling this.
• Come up with other key elements – How you will come up with some of the other key
elements, including a work breakdown structure (WBS) and a scope statement.
2. Get a handle on your requirements management.
This process will give you a clear idea of what your stakeholders want and how you’re going to manage
their expectations. You will need to document exactly what is required in terms of status updates.
Think about how often:
• Check-ins are needed with the client
• The client wants to be informed of deliverable status
• Communications need to be sent and in what format
This information can be gathered through focus groups, interviews, or surveys, and by creating prototypes.
Use our requirements management process to help you avoid frustrating hurdles throughout the project and
understand the differences between scope, requirements and expectations.
3. Define Your Scope.
With your project scope in place, you’re ready to define exactly what is in and out of scope for your project
with a project scope statement. This serves as a guide throughout the project and forms the backbone of
your project scoping process.
Team members should be able to refer to it, and easily be reminded of what is and is not involved in that
specific job. This is also helpful when someone is asked to work on an area that is outside of a project’s
scope.
Scope statements often include:
• Justification. Why is the project happening in the first place?
• Goals. What are you seeking to achieve?
• Deliverables. A breakdown of deliverables and who will be responsible for them.
• Expected results. When the project is complete, what will change? Think about your original
justification here and back it up with projections and data.
• Assumptions. What are you relying on to make your project happen? Consider availability of
teams, budgets, materials, training etc.
• Inclusions and exclusions. Finally, what is in and out of the scope of your project? It’s good
to drill down into specifics here.
4. Create a Work Breakdown Structure (WBS).
Based on your project scope statement and the documents created during requirements collection, you’ll
want to build a Work Breakdown Structure, which is essentially the entire project broken down into smaller
individual tasks. Deliverables are clearly defined, providing the project manager and the team with several
more manageable units of work. A streamlined operational system of record makes creating a WBS simple.
In Workfront’s enterprise work management platform, for instance, it’s easy to standardize and automate
forms, tasks, and workflows. Your team can work faster and more efficiently, knowing they are working
on the correct tasks, in order to complete a project.
5. Validate Your Scope.
This is where your deliverables are reviewed by whoever needs to approve them, whether it be:
• Customers • Managers
• Stakeholders • All three
It’s important to have a plan in place for exactly how project deliverables will be accepted as complete. At
the end of this process, you’ll accept deliverables, change requests, or project document updates.
With an operational system of record, you’re able to set up the scope validation process ahead of time so
that each deliverable is automatically submitted for approval by whoever needs to see it.
You can skip the long, confusing email chains and avoid unnecessary meetings. While stakeholders can
see completed tasks for a project all in one place and be immediately notified when a task is awaiting
approval.
6. Control Your Scope.
Monitoring and controlling is essential throughout the project. A project’s status should be monitored from
start to finish to ensure that it is being executed according to your project scope management plan.
You never know when the scope may need to change, or a customer may add new requirements. In order
to prevent scope creep, project managers should compare performance reports with the project
requirements. Using Workfront, any gaps will be easy to spot and change, quickly getting the project back
on track.
Tips for project scope management.
• Be as clear as possible when wording your scope. Once it has been drafted, re-read it to ensure there
is no ambiguity anywhere. This can help avoid misinterpretations by stakeholders and reduce
follow-up questions.
• Invite as many team members as possible to collaborate during the drafting stage. If more people
are contributing, a greater number of team members will know exactly what is required from the
project.
• Ensure there are zero alterations to the scope once the project has begun. Making amends can
muddy the waters a little and potentially lead to things like increased scope and confusion among
those working on the project.
Implementing project scope management processes.
Implementing these project scope management processes takes a fair amount of time and effort. But in the
long run, they will save you time, money, and headaches.
A good scope management plan involves open communication between all the stakeholders and team
members involved in a project. This results in fewer unwelcome surprises and miscommunications
throughout. Everyone knows and understands exactly what work is involved and can easily stay focused
on the right deliverables.
❖ Project Time Management
Project time management involves analyzing and developing a schedule and timeline for project
completion. Formalized time management processes provide a buffer for things like unexpected roadblocks
and under or over-estimated project timelines.
Time management plans determine what tasks to adjust, and how to allocate and manage resources
throughout the project.
How project managers define project time management varies, and techniques differ between project
management methodologies. For instance, an agile marketing method might need tasks that can fit into
short sprints as requirements change. Managers using Kanban methodologies, on the other hand, might
plan time in more generous segments — allowing for smoother flow. Regardless of project type, the
definition of project time management involves setting time markers against your project and its tasks. It
means defining the time value of each task and allocating resource to each step.
The importance of project time management.
Project time management directly impacts the quality, scope, and cost of a project, making it one of the
most important project management knowledge areas. Managing time helps to secure project completion
on time and on budget. It also clarifies:
• How much time a project requires
• What stakeholders (internal and external) to involve
• And at what point to include their expertise
This process provides a framework for developing a sequence of activities, activity durations, resource
estimations and how these fit into the overall project management plan.
In project management, the time management phase is an important step — when you know what you
intend to deliver and why, time planning helps you get there smoothly. It gives each formerly abstract
subtask a value.
Correct timings are essential.
• Time planning allows you to set realistic deadlines
• Time is money, so managing it well helps boost your bottom line
• Time management can empower your teams to deliver projects on time
Benefits of project time management.
One of the primary benefits of project time management is it creates more time for teams and other
stakeholders to deliver on projects. Effective time management positively impacts the careers and personal
lives of everyone involved.
Additional benefits of time management in project management include:
1. Reduce stress with project time management.
Project completion plans reduce stress levels associated with meeting deadlines. When your teams know
timelines have been mapped out effectively, they can visualize the path to completion with confidence.
Accurate time estimates also reduce unnecessary pressure on an individual level and across your teams.
With good time management, you may find it easier to keep project scope in check, keeping your talent
focused on what’s important. When there’s also a change management plan in place, your people feel
empowered to dedicate the right time to the right tasks, even as processes shift.
2. Increase productivity with project time management.
Knowing what to prioritize increases productivity and allows you to focus on the most beneficial and
strategic needs. This works by giving your teams a sense of urgency, control and direction.
Each of your deliverables should align with a time investment estimate to serve as a guide. This should
prevent aspects of the work taking more time than they’re worth, keeping the knots of productivity tied
tight.
3. Make fewer project mistakes with time planning.
Focusing on only one aspect of a project helps get the right work done and prevents mistakes overall.
Incorporating time values into your project plan helps staff to understand the required investment for each
task. When there’s time planned for checks, this effect is heightened further still.
Great project time management helps you avoid last-minute rushes and meet lead time goals without
sacrificing quality.
4. Increase proficiency with better time management.
Having a timeline in place for projects provides a view into what teams need to work on and when. This
makes them and their organization more proficient across many areas. Effective time management in
project management allows managers to pull together the best talent for the required work. In turn, this
allows for specialization — delivery teams will soon know project details inside and out, reducing pressure
on you.
5. Create more opportunities with better time planning.
With the right approach, teams or departments can become more efficient at managing projects and
completing them on time and on budget. This may even generate further opportunities to manage additional
projects in the future.
What’s more, great project time planning techniques let you showcase your ability to manage ad-hoc
projects effectively on the side. Time management doesn’t mean tunnel vision — rather, it’s about making
accurate projections. This allows you to be flexible in positive ways.
6. Stay on budget with strong time management.
Everyone knows the phrase ‘time is money.’ Keeping a project on target not only ensures things stay on
budget, but keeps stakeholders happy that their investments are working in the most efficient, valuable
way.
For this to work best, consider implementing project monitoring and controlling processes. The sooner you
have accurate data on delivery, the sooner you can recalibrate if aspects of the work start to look
unprofitable.
7. Project time management helps you meet goals.
Time management plans help to achieve project goals as well as impact other personal and professional
goals. All of these benefits lead to increased efficacy and satisfaction across the board.
The main task for any project manager is to get professional projects done. Great time management makes
successful delivery more likely by reducing the risk of project overrun.
Project time management best practices.
• The Pareto Principle.
The Pareto Principle is also known as the 80/20 rule. This means 20% of your time should produce 80%
of your results. From the beginning, identify and highlight the tasks that provide the most value. If, at any
time, value and time fall out of balance, review the task priority and, if necessary, submit a formal change
request.
• Keep it simple.
It’s easy to overcomplicate tasks. Take a step back, evaluate the real ‘why’, and think of more focused
ways to accomplish a task. Concentrate efforts on the most effective methods for completing each given
task, while always keeping the end project goals in mind.
Ask:
o What’s involved?
o What resources do you need to get the job done?
And lean on internal teams to estimate timings. After all, they’re the experts in their fields.
• Observe and analyze time expenditure.
Regularly review time allocation across the board. Efficient use of all resources, especially human capital,
maintains project timelines and budgets. Great data insights help you review this more efficiently,
identifying patterns while there’s still time to claw back resources. For example, if the data shows that it
looks like you underestimated IT resource needs, recalculate and communicate.
• Act rather than worry.
It’s easy to spend time worrying if something is ‘good enough’ or if the team will really hit that deadline.
Drop the worry and take action. Do more research. Ask for an extension if needed and make the necessary
adjustments to get something done right.
• Break larger goals into subtasks.
At first, any large project seems daunting and difficult to figure out where to start. Take larger projects and
break them into smaller pieces and smaller tasks, providing a simpler way to start and prioritize a project.
When each of these has its own deadline and time allocation, it’s easier for everyone to stay within the
lines, reducing the risk of backlogs. Consider working in sprints.
Set daily, weekly, and monthly goals.
Setting goals helps to instil a sense of urgency. Set a monthly goal and work backward. Weekly and daily
goals should roll into each other. When teams and departments hit their daily and weekly goals, they meet
the entire month’s targets by extension.
• Plan for short breaks.
When breaking large tasks down into manageable pieces, make sure to plan time for breaks. Providing
much-needed, scheduled breaks keeps the mind fresh and the body energized. Your people are better placed
to stay on track when there’s breathing space built into the plan.
• Think strategically about team energy.
We should all work on the most important tasks during the most productive, energetic hours of the day,
and save other tasks for less-motivated portions of the day. A project manager’s job is to get the best work
from your people, so broaden your thinking beyond overambitious deadlines. Is it wise to plan so much
specialist software development work in a single week, and do those deadlines really need to be so close?
Asking questions like these helps you to keep things running smoothly.
Creating effective project timelines is an art and a science. Learn how to create a project timeline with our
step-by-step guide.
Five Time Management Strategies
There are many strategies to improve time management in project management. These five provide a good
starting point:
1. Set clear priorities – Rank your tasks in order of importance to ensure you follow an appropriate
activity sequence.
2. Introduce shorter deadlines – Bring forward deadlines so there’s leeway in case of any delays or
interruptions to tasks.
3. Delegate tasks effectively – Ensure relevant personnel are responsible for tasks within their area
of expertise.
4. Reduce interruptions – Improve focus by managing external, environmental and other
distractions.
5. Plan with intention – Create to-do lists for each day of tasks intended to be complete, as a powerful
way to increase productivity.
Project Cost Management
Cost management in project management involves the planning, estimating and overall control of budget.
Cost management processes are in place to help project teams plan and control budgets during the project
life cycle.
While cost management overall is a complicated process and a critical project management knowledge
area, we can break it down into four processes:
1. Resource planning.
While resource management is in place to plan, allocate, and schedule the resources needed for each stage
of a project, resource planning looks specifically at the costs associated with each of these resources.
Because of the complexity of this process, a work breakdown structure (WBS) can help to simplify and
provide clarity.
Using your resource management software, identify what resources will be used to complete each item in
the WBS, determine the associated costs, and perform a cost-benefit analysis.
2. Cost estimation.
Cost estimation is the process of approximating the costs associated with each of the resources required for
all scheduled activities. It’s an important part of the cost management process.
Cost estimating forecasts the cost of completing a project within a defined scope. Given that scope tends
to shift throughout the life of a project, cost estimation is not a one-time process.
Effective cost management requires project managers to keep abreast of budgetary changes during a
project’s lifespan. These estimations sum up all the costs involved in successfully completing a project.
To get a good estimate at the costs, you can use one of the following techniques:
• Analogous estimating – Past projects should inform the cost estimate, here. Analogous estimations
use previous, similar projects as a reference point for costing up the new one.
• Parametric modeling – Mathematical formulas, based on Regression Analysis or Learning Curve
models, inform potential project cost estimations.
• Bottom-up estimating – Costs are based on known quantities, such as individual work or item cost
and duration or time spent on individual tasks.
3. Cost budget.
Cost estimations lead directly into cost budgets. Here, you’ll work out the base costs and any
additional requirements for the project.
A good project budget will help you make key decisions with respect to the project schedule and resource
allocation constraints.
These budgets should account for everything from direct labor costs, to material costs, factory costs,
equipment costs, administrative costs, and software costs.
To set the cost budget, consider the following techniques:
• Cost aggregation – This requires you to aggregate or combine costs from an activity level to a
work package level. The final sum of the cost estimates is applied to the cost baseline.
• Reserve analysis – With this cost management method, you create a buffer or reserve to protect
against cost overruns. The degree of protection should be equivalent to the risk foreseen in the
project. The buffer is part of the project budget, but not included in the project baseline.
• Historical data – Under this technique, you use estimates from closed projects to determine the
budget of the new project. This is very similar to analogous estimation.
• Funding limit reconciliation – Here, you adhere to the constraints of a funding limit. This is based
on the limited amount of cash dedicated to your project. To avoid large variations in the expenditure
of project funds, you may need to revise the project schedule or the use of project resources.
4. Cost control.
Good project managers should have a constant eye on cost and potential scope creep. This includes being
vigilant for times when costs vary from estimations. Cost control also involves informing the stakeholders
of cost discrepancies that vary too much from the budgeted cost.
Controlling the budget means being aware of the:
• Original budget • Actual costs
• Approved costs • Committed costs
• Forecasted costs
Budget control involves being aware of and acting on changes and issues as and when they occur.
To effectively control project costs, consider these tools and techniques:
• Earned value management – This uses a set of formulas to help measure the progress of a project
against the plan. It integrates schedule, scope and costs to measure project success against planned
and actual values. Benefits include measuring cost alongside other factors.
• Forecasting – This uses a project’s current financial situation to project future costs. The forecast
is based on budgeted cost, total estimated cost, cost commitments, cost to date, and any over or
under budgeted costs. It can be useful as part of the controlling and monitoring phase.
• To-Complete Performance index (TCPI) – A cost management tool that represents the level of
project performance needed for future work to meet the budget. Useful to make decisions about
efficiency when a project is under way. A TCPI figure above 1.0 indicates your project is running
above budget.
• Variance analysis – A technique that involves analyzing the differences between the budget and
final cost projections.
• Performance reviews – These are used to check the health of a project. A performance review
includes an analysis of project costs, schedule, scope, quality and team morale. This may help to
gain a broader view — for instance, if you suspect an unprofitable project will cause talent drain in
the long term.
By learning how to estimate expenses, determine budgets, and control costs, you can be a better project
manager and leader. Effective cost management will help you get projects done on time and under budget,
the golden ticket for any successful project manager.
Why is cost management important?
In project management, the cost management process is an important tool to keep profits healthy, reducing
the risk your project could become unviable. When you define what healthy finances look like, it’s easy to
make decisions in real time when work is underway.
Ask yourself:
• Does an aspect of the work need scaling back?
• Do you need to cut investment in a low-priority area?
The earlier these questions are answered, the more opportunity there is for a project manager to recalibrate
and preserve return on investment (ROI).
The importance of cost management comes into play from the very beginning of the project lifecycle,
however. This is because costs and budgets affect key project decisions — from the people you hire to the
materials you use.
When a project doesn’t stay within budget, it can remain incomplete, harming a project manager’s
reputation. In a worst-case scenario, mismanaged costs can make an organization unviable.
Great project cost management lets you generate data to share with stakeholders. When you view this using
intuitive software, it’s easy to lift insights for future project plans.
The benefits of implementing project cost management.
The project cost management process empowers you to plan a project well, make informed decisions once
activities are underway, and measure success.
Keep track of multiple types of project cost, including:
• Direct costs – These include money earmarked for software fees and other mission-critical
overheads.
• Indirect costs – In business, indirect costs are a fact of life. Each individual project contributes to
your organization’s electricity bill, for instance.
• Fixed costs – One-off fees may be considered fixed, since they aren’t linked to time management.
• Variable costs – This type of cost rises if a project is extended or delayed. Staffing costs are a
common example.
• Sunk costs – These are purchases that have already been made, effectively the cost is deemed to
be sunk.
Understanding each can help you to differentiate and find ways to make savings.
The challenges of project cost management.
When elements of your project plan change, the corresponding cost figures will alter too. Losing grip of
your project’s scope is a fast way to also lose track of costs, putting your entire project at risk.
Accurate cost management also requires schedule and cost integration. Communication can be key for this.
Ask your finance analysts to provide direction to managers responsible for aspects of project delivery, and
for teams to report back on issues in turn. If tasks are stretching beyond timelines in the original plan, this
should be reflected in a project manager’s calculations right away.
Finally, when reporting is slow or inaccurate, it makes the above aims harder to achieve. Check figures for
accuracy regularly to avoid surprises.
Methods of Cost Estimation
The three main methods of estimating cost are the:
• Expert judgement – The quickest and involves asking expert people or groups to provide insight.
They may use data on past projects also.
• Parametric estimating – Uses statistical information about the relationship between variables and
may use an algorithm to map past project data onto current plans.
• Analogous estimating – something of a half-way house between the above two methods. Uses
values such as scope, duration and project-specific measures from past activities. The actual costs
in previous projects help to shape estimates.
Project Quality Management
Project quality management is the process of continually measuring the quality of all activities and taking
corrective action until the team achieves the desired quality. Quality management processes help to:
• Control the cost of a project
• Establish standards to aim for
• Determine steps to achieve standards
Effective quality management of a project also lowers the risk of product failure or unsatisfied clients.
Project quality management plan.
Most project managers intend to create the best possible product or service. But even the most skilled,
educated teams, with the most modern tools, may fail without the right project quality management plan in
place.
Measuring quality may seem like something you can’t do until after the project is complete. However,
project quality management should be planned from the beginning and monitored throughout with these
three quality management processes:
• Quality planning • Quality control
• Quality assurance
Quality planning.
A good quality management plan starts with a clear definition of the goal of the project. First, be clear on
what the product or deliverable is supposed to accomplish. Then, ask yourself:
• What does it look like?
• What is it supposed to do?
• How do you measure customer satisfaction?
• How do you determine whether the project was successful?
Answering these questions and others will help you identify and define quality requirements, allowing you
to discuss the approach and plans needed to achieve those goals.
This includes:
• Assessing the risks to success
• Setting high standards
• Documenting everything
Also key is defining the methods and tests to achieve, control, predict, and verify success. Be sure to include
quality management tasks in the project plan and delegate these tasks to workgroups and/or individuals to
report and track quality metrics.
Quality assurance.
Quality assurance provides evidence to stakeholders that all quality-related activities are being done as
defined and promised. It ensures safeguards are in place to guarantee all expectations regarding quality
outputs will be met.
Quality assurance is done to the products and services delivered by a project, as well as the processes and
procedures used to manage the project. The team can do this through systems such as a process checklist
or a project audit.
Quality assurance tests use a system of metrics to determine whether the quality management plan is
proceeding acceptably. By using both qualitative and quantitative metrics, you can effectively measure
project quality with customer satisfaction.
These tests or quality audits will help you predict and verify the achievement of goals and identify the need
for corrective actions. Quality assurance tests will help you map quality metrics to quality goals, allowing
you to report on the status of quality at periodic project review meetings.
Quality control in project management.
Quality control involves operational techniques meant to ensure quality standards. This includes
identifying, analyzing, and correcting problems. While quality assurance occurs before a problem is
identified, quality control is reactionary. It occurs after a problem has been identified and suggests methods
of improvement.
It measures specific project outputs and determines compliance with applicable standards. It also identifies
project risk factors, their mitigation, and ways to prevent and eliminate unsatisfactory performance.
Quality control can also ensure the project is on budget and on schedule. You can monitor project outputs
through peer reviews and testing. By catching any deliverables failing to meet the agreed standards
throughout, you can simply adjust direction rather than having to entirely redo certain aspects.
Benefits of project quality management:
• Quality products. Ensuring you and the project team check the quality of the project means the
product will go through multiple development processes. This will help to deliver a final product
that meets customer expectations.
• Customer satisfaction. Tackling problems in real-time and communicating with the customer will
ensure they’re up to date and aware of any issues. Incremental customer feedback can also help you
to deliver a better final product.
• Increased productivity. With a project quality management system everyone knows deadlines and
what is needed in advance. Having set deadlines, meetings, and reports can influence the project
team to hit targets early to keep the project on track.
• Financial gains. Projects can run over budget if good quality management is absent. By having the
three processes in place — planning, assurance, and control — you can tackle problems before they
cut into your budget.
• Removes silos. Boost collaboration between teams with project quality management tools. Being
able to easily see where each team is up to and using meetings to discuss feedback between
departments can remove departmental silos.
Quality management tools.
Affinity diagrams.
Affinity diagrams generate, organize, and consolidate information concerning a product, process, complex
issue, or problem. It expresses ideas without quantifying them (brainstorming sessions).
Process decision program charts.
Process decision program charts see the steps required for completing a process and analyzing the impact.
These charts help to identify what could go wrong and help plan for these scenarios.
Interrelationship diagrams.
SixSigmaDaily defines interrelationship diagrams as diagrams that show cause-and-effect relationships.
These diagrams identify variables that occur while working on a project and what parts of the project those
variables might affect.
Prioritization matrices.
Use these during brainstorming sessions to evaluate issues based on set criteria to create a prioritized list
of items. It helps to identify what issues may arise and determines the problems to prioritize to meet
objectives.
Network diagrams.
A visual representation of a project’s schedule. This helps plan the project from start to finish. It illustrates
the scope and the critical path of the project. The two types of network diagrams are:
• Arrow diagram
• Precedence diagram
Matrix diagrams.
A matrix diagram is used to analyze data within an organization’s structure. It shows the relationships
between objectives, factors, and causes that exist between rows and columns that make up the entire
matrix. There are multiple types of matrices to use, depending on the number of items and groups of items
to analyze.
The different matrix diagrams and their use cases:
• L-shaped matrix. Creates a relationship between two items.
• T-shaped matrix. Creates a relationship between three groups of items.
• Y-shaped matrix. Creates a relationship between three groups of items, but it is displayed in a
circular diagram.
• C-shaped matrix. Creates a relationship within three groups of items, and it is displayed in 3D.
• X-shaped matrix. Creates a relationship between four groups of items.
Quality management software.
Project quality management is multifaceted. Your team must:
• Clearly understand the quality expectations
• Determine how you will measure whether you’re meeting those expectations
• Implement any necessary changes along the way
The ideal work management platform allows you to track these aspects in one easy-to-use place.
Project Resource Management
Resource management in project management involves managing and assigning your organization’s
resources like budgets, capacity, and team members. To be successful at resource management, you must
provide the following:
Insights: Resource management relies on granular insights into what your team is working on and how
long it takes them to complete each task.
Priorities: Priorities management for the project and expectations must be articulated clearly and shared
to the relevant stakeholders and team members.
Tracking: Status updates need to be tracked throughout the project life cycle.
Resource management gives your team the ability to work on the right work at the right time. In project
management, the resource management process happens in two stages: resource planning and resource
scheduling.
Resource planning
The resource planning phase of resource management is where you identify the necessary resources for the
project. You won’t be assigning tasks to any team members at this stage of the process, or allocating
budget—just laying the foundation.
Forecasting your resources includes considering “what if” scenarios. This will ensure you know how other
priorities and project timelines will be affected. When you utilize resource planning as a part of
your resource management plan, you avoid blown budgets, miscommunication, and a lot of frustration
across tasks and teams.
Resource scheduling
In the scheduling phase of your resource management’s management plan, you will check your needs
against availability. Using the forecasted resources like time, budget, and skills from the planning phase
you will now be able to determine where there is overlap with your team’s current projects and workload.
Using the resource forecasts and team availability in your resource management software, you can now
assign tasks based on the individual skills and abilities of your team. When your team is working on
something they are good at, they are happier and more engaged in their work, which improves project
turnaround.
Benefits of project resource management
The benefits of resource management can’t be overstated. Without a resource management plan, you may
be dealing with missed deadlines, overworked team members, and frustrated stakeholders. Resource
management ensures your team is efficient, your stakeholders have the proper visibility, and your costs are
managed. The benefits of project resource management include:
• Increased visibility into team member utilization
• Ability to make adjustments on the fly
• Increased project risk awareness
• Improved engagement morale
Tips to improve your resource management
1. Develop a strategic breakdown structure
No matter what stage your business is in, take the time to create a Strategic Breakdown Structure where
you align each of your goals with measurements. Following are a few questions you could ask yourself to
get started:
• What are you trying to accomplish?
• How will you measure success?
• Are you working on the right things?
• What’s not going to help you succeed?
Measure your results as you go and adjust your resource management plan along the way. You should keep
your company’s and team’s strategic initiatives as your North Star, guiding all of your efforts, because you
can’t manage what you don’t measure.
2. Take the time to gather project requirements
Getting the information about a project before it kicks off will enable you and your team to plan and manage
resources effectively for the full scope of any project. Depending on the type of work you’re doing, your
project input form will likely be different, but should focus on the end goal you’re working to accomplish,
including:
• Strategic alignment
• Relevant deadlines and milestones
• Project goals and success metrics
• Budget
• Actionable learnings from prior projects
• Key competitors and approach
• Approvers required throughout the project
Don’t be afraid to invest time upfront into your requirements gathering, because everything you document
before you launch into the project will be time (and sanity) saved along the way.
3. Plan for the unplanned
We all hate ad hoc requests, but in some industries and companies, they come with the territory. A last-
minute opportunity might arise that requires support, or a market shift may make your planned activities
obsolete (such as warm weather when you’re planning a marketing blitz advertising coats).
Whatever the reason, ad hoc requests happen. The typical response, though, is that they completely derail
your work—making you and your team miserable. Instead, plan for ad hoc work to come your way as a
part of your resource management plan. If you are tracking your team’s work, you can come up with a
good idea of how much time typically goes to last-minute requests. If that number is 20%, then account for
it in your resource plans. Yes, that means you’ll likely only be able to schedule team members at 60%
utilization (80% utilization is typically given to a full-time employee), but you’ll have a more realistic view
of what your team can actually accomplish.
4. Know how long things take
This one is really simple—track how long it takes you to complete repeatable work projects. Track time
over both hands-on time (hours worked) and duration (over what period of time). You’ll likely be surprised
at how you were under-allocating time for projects, assuming they have fewer steps and take less time than
they actually do. Once you know how long things take, it’s much easier to accurately forecast resources to
get them done.
5. Create your prioritization methodology
There are a lot of ways to prioritize—around departmental and company goals, against opportunities that
arise, or to the requests of the boss. At the end of the day, it’s best to take all of these into consideration.
Consider the following as you create your team’s prioritization methods:
Balance strategic alignment: how do the requests align to the strategic mission of your team or
department?
Urgent vs. important: there are those requests that are absolutely urgent; and those that are important—
how do you identify the fine line between both?
Relative effort: it’s common for people to bring requests that “will only take 5 minutes” in order to get
things slipped through the system (and they rarely really take 5 minutes). Have an idea of the relative effort
needed to accomplish your commonly requested tasks so that you can schedule the requests properly.
6. Change is hard
Any change you make to the way you manage a project’s resources requires a mind shift from your team.
And change is really hard. Don’t skimp on giving your team members leeway to process and react to the
change in their own way. Most should quickly embrace a system that will let them work fewer weekends,
but you could have push-back. Following are the tips that Erica shared to navigate the change process:
Communicate: Define what you want people to do differently. Visibly and transparently change your
intake, prioritization and resource management behaviors. Let everyone see how you’re doing things
differently.
Model: Live the change – leadership models the new behavior. Get executive/leadership buy-in for
more structured intake process, prioritization, and resource management
Reinforce: Rewards and consequences are the most powerful levers you have. Reward those who follow
suit (call-out in company meetings, spot awards, “good job”, etc.) and ensure there are consequences for
the “old behaviors” (chaotic/randomized work isn’t funded/supported, for example).