Quality Improvement Zone

A Gantt chart helps teams understand what needs to happen, when activities are planned and who is responsible for progressing them.

Activities are listed vertically, with time shown horizontally. Coloured bars indicate when each activity is expected to start, how long it may take and when it should be completed.

A Gantt chart can also show:

• key project milestones
• activities happening at the same time
• links or dependencies between activities
• progress against planned timescales
• named owners for different activities

A Gantt chart provides an overview of the project schedule, while an action plan usually contains more detail about the individual actions, owners, deadlines and progress updates. Gantt chart is a visual timeline of tasks that helps a team/individual identify what tasks should be done and by when.

Improvement projects often involve several activities happening across different timescales. A Gantt chart makes the overall project schedule visible, helping teams coordinate work and understand how different activities fit together.

A Gantt chart can help you:

• plan and schedule project activities
• show the expected duration of the project
• clarify when activities should start and finish
• identify who is responsible for each activity
• show the order in which activities need to happen
• identify dependencies between activities
• highlight activities that can happen at the same time
• identify potential delays or scheduling conflicts
• communicate the project timeline to stakeholders
• monitor progress against the original plan

The value of a Gantt chart comes from making the project timeline easier to understand, discuss and update. It should support planning and communication rather than become an administrative task.

1. Clarify the project aim and scope

Start by reviewing the project charter, improvement aim and agreed scope. This helps ensure that the activities included in the Gantt chart remain focused on what the project is trying to achieve.

2. Identify the main activities

Review the action plan and identify the activities needed to progress the project. These will vary depending on the project.

Start with the main areas of work rather than adding every small task. More detailed actions can remain within the action plan.

3. Identify milestones

Add important milestones that indicate progress or key decision points.

Milestones are usually shown as points in time rather than activities with a duration.

4. Agree the timeline

Decide which timescale is most useful for the project, such as:

• days
• weeks
• months
• quarters

Use a level of detail that is appropriate to the length and complexity of the work. A short project may need a weekly timeline, while a longer programme may be easier to manage using months or quarters.

5. Estimate activity duration

For each activity, estimate:

• the planned start date
• the expected duration
• the planned completion date

Use this information to add a bar across the relevant part of the timeline.

Timescales are estimates and may need to change as the team learns more about the system and tests different approaches.

6. Identify owners

Assign a named owner to each activity. The owner does not need to complete all the work alone but is responsible for ensuring that the activity progresses and is updated.

7. Identify dependencies

Consider whether any activities depend on others being completed first.

For example:

• measures may need to be agreed before baseline data is collected
• approval may be required before a test begins
• testing may need to demonstrate improvement before implementation starts

Showing dependencies helps teams understand how delays in one area could affect the wider project.

8. Agree how progress will be shown

Use clear and consistent status categories, such as:

• Not started
• In progress
• Complete
• Delayed or at risk
• No longer required

Colours can make the chart easier to interpret but include text labels or another indicator so that meaning does not depend on colour alone.

Agree on the definitions of each status so they are used consistently. The current page’s emphasis on agreeing operational definitions for status remains useful here.

9. Review and update the chart

Review the Gantt chart regularly during project meetings.

Use the review to:

• update progress
• identify delays or risks
• adjust dates where needed
• review dependencies
• add new activities
• remove activities that are no longer required
• communicate changes to stakeholders

Changes to the timeline do not necessarily mean the project has failed. Improvement work often requires teams to adapt their plans as learning emerges.