Project Management - Free Course with Quizzes

Get more done with project management

Project management is useful in a wide range of activities where structured planning, coordination, and execution are needed to achieve specific goals. Starting activities without planning often means a suboptimal result or redoing work, meaning extra time and costs.

An analogy for this approach is packing your car when you go on vacation. When items are packed when they arrive at the car, it often happens that a last-minute item, like a football, does not fit anymore. Unpacking all items in front of the trunk and repacking often solves the problem.

A more coordinated approach where all travelers put their items in front of the car before the packing starts, gives the possibility to plan what items are to be taken and how to fit them more densely.

A lot needs to be managed in a project, basically everything to make it a succes. The way to achieve this has been empirically found and is based on best practices. Some well-known frameworks are PMBOK, PRINCE2 and Scrum. Areas to manage are:

  • Deliverables as part of the scope
  • Create and track project planning
  • Cost tracking
  • Quality assurance and control
  • Resource allocation
  • Clear communication and status reporting
  • Stakeholder expectations and concerns

Quiz

When could Project Management be MOST valuable?

Coordination and planning are required here.

Quiz

For what activity is Project Management LEAST beneficial?

This activity has a relative short time frame.

Examples for improvement

Without proper Project Management a lot can go wrong on different aspects. Some results may look familiar to you. Click to see examples.

Poor planning with lack of direction, scope, or measurable objectives.
A software team builds features without a roadmap, leading to wasted effort on low-priority tasks.
Tasks drag on indefinitely, without schedules or milestones.
A construction project runs months behind due to uncoordinated work, resulting in missed deadlines and delays.
Costs spiral out of control due to poor resource tracking.
A marketing campaign overspends on unapproved vendors, resulting in budget overruns.
Teams work in silos, leading to misalignment and conflicts.
Engineers and designers clash because requirements weren't documented, resulting in chaotic communication.
Deliverables fail to meet standards or stakeholder expectations.
A product launches with critical bugs because testing was unorganized, resulting in low quality and unmet requirements.
Problems escalate because no one anticipates or mitigates risks.
A supplier delay halts production because backups weren't arranged, as a result of unmanaged risks.
Time, money, and effort are wasted on redundant or inefficient work.
Two teams unknowingly develop the same feature, resulting in wasted resources.
A client rejects a project because deliverables didn't match expectations.
Clients, sponsors, or users lose trust due to unmet promises, resulting in stakeholder dissatisfaction.
Employees quit due to constant firefighting and unclear roles.
Confusion and rework frustrate team members, resulting in team burnout and low morale.
A startup folds after a poorly managed product launch flops.
The initiative collapses, wasting all invested resources, resulting in project failure.

Quiz

What happens when a project has poor resource tracking?

Resource costs spiral out of control.

Quiz

What is neglected when deliverables fail to meet standards?

A product does not meet requirements.

Quiz

What causes team burnout and low morale?

Clear responsibilities are needed to work effective and efficient.

Life cycle

A project's life starts with an idea and ends with a result. In order to progress from start to finish, a breakdown in manageable phases is recommended. Each phase has it own goal, meant to decrease uncertainty while work and costs increase.

A project life cycle typically consists of 5 phases, starting at Initiating and ending at Closing. Phases are not necessarily sequential in time. Executing and Monitoring & Controlling take place at the same time. For some projects also Planning can take place at the same time as Executing. In a cyclic type of project, phases are planned more agile, meaning that they can follow external demand; during phase 1 the next phase 2 is planned, etc.

Phases differ per industry, company or even project. Standardization per industry or company helps to compare projects.

Phases

Click the following phases for typical activities.

Initiating

Here goals, stakeholders and feasibility are defined.

  • The goals are specified in Requirements documentation.
  • Identify the Stakeholders, those who have an interest in the project, like the customer, end-users, developers, etc.
  • Conduct Feasibility Studies, being technical, financial, commercial or operational, depending on the expected risk.
  • Create the Project Charter, a high-level document that outlines the project on purpose, time and budget.
  • The purpose can be shown in a Business Case, where costs and benefits are compared.
Planning

Here the project plan is developed.

  • Define project scope, objectives, and deliverables, to know why.
  • Create a Work Breakdown Structure (WBS), to know what.
  • Define the project organization and responsibilities, to know who.
  • Estimate time, cost, and resources (people, material, equipment, services, etc), to know how.
  • Develop schedules (e.g., Gantt charts, critical path, milestones), to know when.
  • Identify risks and mitigation strategies, to know what if.
Executing

Here the project work is carried out according to the planning and results are delivered.

  • Assign tasks to teams and manage resources.
  • Procure materials and services from vendors.
  • Implement Quality Assurance to work according to standards and processes.
  • Develop deliverables, like software code, construction work, etc.
  • Discuss and communicate progress and risks in meetings and reports.
Monitoring and Controlling

Here progress is tracked, risk is managed and plans are adjusted if needed.

  • Monitor schedule and budget for deviations between plan and actual results.
  • Perform Quality Control on the deliverables by inspections and testing.
  • Track risks in a register and implement fixes.
  • Report status to stakeholders with a dashboard or meetings.
  • Manage changes and risks and update project plans if needed.
Closing

Here deliverables and documentation are finalized and lessons are learned.

  • Deliver the final product to the client.
  • Obtain formal acceptance.
  • Archive project documents.
  • Review the project and retrieve lessons learned.
  • Celebrate success with the team!

Milestones

Phases are typically separated by milestones. Here a phase is closed by all stakeholders and the next phase is kicked-off in more detail than it was at the previous milestone.

Quiz

In what phase do you conduct a feasibility study?

Study risks before you start planning.

Quiz

In what phase do you conduct Quality Assurance?

Work according to standards and processes.

Quiz

In what phase do you report the status of the project?

This is Monitoring the Execution.

Work Breakdown Structure

In general a Work Breakdown Structure (WBS) forms the basis for planning. It is a hierarchical decomposition of the work that needs to be done. It has a so-called tree structure with a root node (project scope) and branches to nodes that break down the scope into further details. An end node has no more breakdown nodes and is called a leaf.

In order to understand a node, you need to follow the entire path from root to node. The number of nodes in the path is the level of the node. With a WBS you make a breakdown from a complex deliverable to well-defined tasks. This systematic approach reduces the chance of overlooking relevant work.

WBS example

An easy way to visualize the WBS tree is to indent text. The hierarchical WBS code also shows the breakdown and level of a node. Click on a node to see the entire path.

project

/

1software

/software

/1

1.1firmware

/software/firmware

/1
/1.1

1.1.1develop

/software/firmware/develop

/1
/1.1
/1.1.1

1.1.2test

/software/firmware/test

/1
/1.1
/1.1.2

1.2app

/software/app

/1
/1.2

1.2.1develop

/software/app/develop

/1
/1.2
/1.2.1

1.2.2test

/software/app/test

/1
/1.2
/1.2.2

2hardware

/hardware

/2

2.1printed circuit boards

/hardware/printed circuit boards

/2
/2.1

2.1.1main board

/hardware/printed circuit boards/main board

/2
/2.1
/2.1.1

2.1.2user interface board

/hardware/printed circuit boards/user interface board

/2
/2.1
/2.1.2

2.1.3connector board

/hardware/printed circuit boards/connector board

/2
/2.1
/2.1.3

2.2power supply

/hardware/printed circuit boards/power supply

/2
/2.2

3mechanics

/mechanics

/3

3.1case

/mechanics/case

/3
/3.1

3.2buttons

/mechanics/buttons

/3
/3.2

3.3connectors

/mechanics/connectors

/3
/3.3

The WBS codes form a tree:

Products and Activities

A project breakdown consists of products (nouns) and activities (verbs). The most strict division is using products for nodes and activities for end nodes. When you make a breakdown in tasks, you use nouns and verbs per node.

The contents of the breakdown can be collected from:

  • Requirements documentation for deliverables
  • Contracts with obligations
  • Previous projects for lessons learned or collected data
  • Company policies on projects
  • Legal policies that apply for the product or service
  • Brainstorm sessions with project team and experts using for instance a mindmap

Quiz

How many end nodes are in the WBS example?

End nodes do not have further breakdown nodes.

Quiz

What WBS level has path /software/firmware?

The level is the number of nodes in the path.

Quiz

How many end-nodes in the WBS example are activities?

Develop and Test are two verbs for two products.

Resources

In order to execute a project, resources are required. There are many types of resources, most common is personnel that does the work. Personnel may require other resources like equipment, material, products, external services, etc. Resources have in common that they cost money and determine the project costs.

Resource types

Click on the resource type to see the definition:

Personnel

Team members that execute activities and tasks.
A personnel resource can be a person or a skill group. Using a generic skill group, like "carpenter", has the advantage that this resource can be assigned more efficiently.

Equipment

Special equipment and machinery that is not part of standard personal equipment.

Material

Warehouse material or special products that are used or installed.

Service

This is a broad category like travel cost, consultancy, software tools, etc.


See more about resource types in the user guide of ProjectWork.

Assignments

The amount of work is estimated per WBS activity and can be divided across the team members. The duration of activity work depends on the number of assigned team members and their availability percentages.

Personnel and equipment are priced per unit of time and the costs depend on the duration of an activity. Material and service are priced per unit and can be assigned to both products and activities, regardless of the time.


See more about resource assignments in the user guide of ProjectWork.

Capacity

Resources have limited capacity, meaning that their quantity is limited per unit of time. This is most clear for a person resource, who cannot work more than 100%. If a person needs to execute several activities simultaneously, this exceeds his capacity. Also other resources have a maximum capacity, like a skill group of 3 carpenters.


See more about capacity in the user guide of ProjectWork.

Quiz

Which statement about resources is correct?

Material is assigned per unit and cannot be assigned again.

Quiz

What contains a skill group?

More people can have the same skill.

Planning

In a schedule the project nodes, like phases, milestones, locations, deliverables and activities are arranged in time. The optimal start and finish dates of activities can be calculated based on their constraints. The start and finish dates of the lower level nodes in a path follow the higher level nodes. This will be explained with a visualization.

Gantt chart

A schedule can be made visible in a so-called Gantt chart, named after Henry Laurence Gantt who developed the chart around 1910. The chart contains the execution duration of the WBS nodes along a horizontal timeline as a bar, and the Work Breakdown along the vertical axis. The dependencies are indicated with arrows between the bars.

Dependencies

Activities in a Work Breakdown Structure may depend on each other in time. As an example, it makes sense to first develop a new function and than test it, rather than the other way around.

Dependencies can be described more general as one or more activities depend on one or more other activities. These dependencies turn the activities into a workflow. With complex dependencies you need to prevent loops in the workflow. As an example, in a Gantt chart dependencies look like this:

Activities D and E can only start when A, B and C are ready. Whether an activity is ready is made visible with a line in the centre of the Gantt bar. When the line has the same length as the bar, it is ready.

Do not confuse the work breakdown with the workflow. Nodes are part of the work breakdown and the workflow, but the breakdown is not part of the flow, see example in Gantt chart:


See more about dependency types in the user guide of ProjectWork.

Template

You can start a planning by copying a template. The advantage is that you do not need to create the WBS entirely yourself. Comparing projects from the same template is also easier.

Using a template is a good idea when it is a template that you made yourself from an existing project. You can include improvements, found while executing a project, to the template for future similar projects.

Taking a template from a gallery as a quick start has disadvantages. It may not contain all you need and making changes can take a lot of time. Making a WBS is teamwork and a gallery template is likely to distract or mislead.

Quiz

What is NOT a direct advantage of a Gantt chart?

This depends on the chosen timescale.

Constraints

Constraints are the core of Project Management. The main constraints are scope, time and cost. The scope is what needs to be achieved within time and budget. List of constraints:

Scope

The work that needs to be accomplished (features, deliverables, tasks).

Time

The schedule and deadlines for completing the project.
Deadlines are fixed dates that cannot be shifted in time, like external events. Work needs to be done before or after a deadline.

Cost

The budget allocated for the project.

Quality

The legal, industry, or organizational standards and performance expectations of deliverables.

Dependencies

Work can only be executed when dependencies are fulfilled.

Resources

Work can only be executed when human resources are available.

Risk

Uncertain external factors that affect the project, like market conditions, weather, or geopolitical issues.

Solutions

Planning a project is in essence finding a schedule that fulfills all constraints. This complex calculation can be fulfilled with powerful Project Management software, like Microsoft Project and ProjectWork.

The Critical Path Method (CPM) solves the Dependencies and Deadlines constraints by first fulfilling the dependencies from project start to project finish and than backwards from finish to start. The nodes that have identical start and finish dates in both directions are on the so-called critical path, meaning that any delay for these nodes results in delay for the project.

Another method that includes the Resources constraint as well, is called Critical Chain Project Management (CCPM). It solves the human resource conflicts and makes explicit when human resources are available in buffers. If human resources are always available, then the Critical Chain is identical to the Critical Path.

In general, Resource Leveling solves the human resource constraints by shifting nodes. The result is that no human resource exceeds its capacity.

Uncertainty

A project is per definition a projection into the future, therefore the amount of work that is required to realize a Work Breakdown Structure is uncertain. The effect of this uncertainty on the project completion date is hard to analyse because of dependencies: nodes that follow each other will statistically counteract their variance, uncertainty in concurrent nodes can cancel out. In general the effect of uncertainty on the project completion date is overestimated because worst-case estimates are simply added.

Instead of analysis, a Monte-Carlo simulation can be used, named after the casino. In each calculation a random selection is taken from the uncertain work according to a probability distribution. Each calculation will result in a project completion date, which accumulate in a probability distribution. From this distribution, confidence levels on project completion dates can be derived. To avoid the time-consuming entry of a probability distribution and lengthy calculations, you can limit the entry to the most uncertain activities.


See more about uncertainty simulation in the user guide of ProjectWork.

Quiz

Under which constraint are legal standards listed?

A deliverable is expected to fulfill legal standards.

Quiz

What statement is correct?

A project is a complex accomplishment in the future.

Monitoring

When a project is executed, monitoring is required to see if everything is going according to plan. If differences are noticed, control is required to make adjustments.

Progress

A simple and effective way of monitoring, is tracking the progress of all activities. With a long and complex activity, estimating its progress is difficult and ticking off completion happens late. When you split a long activity into several, more concise activities, delays are noticed sooner.

The progress of a node follows the progress of its higher level nodes. Since end-nodes do not have higher level nodes, their progress can be entered.

Risk

Uncertain events can cause a planning to need revision. Therefore it is required to identify and register risks upfront. Risks which you identify are more likely to be avoided and when they occur the response is already known.

The impact of a risk can be quantified by giving it a probability of occurring and the extra cost in time or money. The multiplication of these numbers is the impact of the risk. All risks can be ranked in this way to find the most impactful once that need an alternate plan.

Baseline

When the project planning is adjusted, remembering where you come from is beneficial. This can be achieved by setting a baseline of the planning before you adjust it.

Having a baseline also helps to predict the delay in project completion, based on the Earned Value Method (EVM). This method creates a curve from project start to project finish on the horizontal axis and the accumulated amount of work vertically. Typically an S-shaped curve appears.


See more about baselines in the user guide of ProjectWork.

Quiz

Which statement is correct?

A WBS depicts the structural dependency of the nodes.

Quiz

What is NOT correct?

There is no distribution, only a chance of occurring.

Feedback

If you have any questions, comments or suggestions about this course, please let us know!

Please contact the helpdesk.