Retired course

This course has been retired and is no longer supported.

About this lesson

Understand when and how to use a milestone schedule on a project.  Learn how to create a milestone schedule. 

Exercise files

Download this lesson’s related exercise files.

Milestone Schedule.docx
59.5 KB Milestone Schedule - Solution.docx
59.8 KB

Quick reference

Milestone Chart

The Milestone Chart is a project schedule tool that shows items of significant risk or importance to the project.

When to use

Milestone Charts are for communicating risk.  The Milestone Chart is the primary schedule chart used in Management Reviews.  If a project must integrate with other projects, the Milestone Chart of each project should be shared with the others, so that each project is aware of issues that could impact the integration points.  I don’t recommend using a Milestone Chart for small one-person projects that are not technically complex.  The Milestone Chart does not add any value to project management in those cases and just becomes a waste of time.

Instructions

If the project has many stakeholders or team members, a Milestone Chart helps everyone to understand the significant risk events on the project. 

  1. At the time of initial project planning, the milestones for project phases are identified and the phase timing is set.  Project phases represent a major set of project deliverables and the start and completion of those items is a significant event on the project.
  2. Within each phase, when the phase is being planned in detail, significant events and risk reduction points are treated as milestones and added to the Milestone Chart.
  • Project deliverable completions are milestones since they represent a significant event in the success of the project. Ex: completion of software development
  • Strategic project decisions are milestones since they represent a significant event in the success of the project. Ex: selection of building architect
  • Completion of major high risk activities are milestones since they represent a significant reduction in overall project risk. Ex: completion of qualification test
  • Major project Management Reviews are milestones since management makes a determination on project progress or redirection.  Ex: monthly project reviews

The Milestone Chart is maintained as an active project management tool and is used in Management Reviews and often included in stakeholder communications.

Hints & tips

  • Milestones should be meaningful events to stakeholders.  Include their strategic “wins.”  If they don’t care about an event but should, use the Milestone Chart to help them understand.
  • When creating a Milestone Chart with project management software, don’t assign any resource effort to the Milestone.  Instead, create a task(s) of Milestone preparation effort.  A Milestone is treated as a “zero-time” event in most software,  assigning effort to an event with no time often screws up the cost calculations.
  • Have at least one significant project milestone each month, not counting management reviews.  This helps the stakeholders understand whether or not the project is making progress.
  • Try to describe your milestones in a “pass/fail” manner so it is clear whether or not the milestone was successfully passed.
  • Milestone:  “A milestone is a significant point or event in a project, program or portfolio.”  PMBOK®Guide

This definition is taken from the Glossary of the Project Management Institute, A Guide to the Project Management Body of Knowledge, (PMBOK®Guide) – Sixth Edition, Project Management Institute, Inc., 2017.

Login to download
  • 00:01 Hi, I'm Ray Sheen.
  • 00:06 Let's talk about project schedule planning using the tool the Milestone Chart.
  • 00:10 The milestone chart is used to track and communicate project risk.
  • 00:15 It gives a risk based view of the project schedule.
  • 00:20 The project management body of knowledge, the PMBOK Guide, defines a milestone
  • 00:25 as a significant point or event in a project, program, or portfolio.
  • 00:30 A milestone is normally used to indicate risk decision points or
  • 00:33 events that will change the project risk profile.
  • 00:36 At the milestone, the project team and
  • 00:38 stakeholders need to focus on the risk event, and take action if required.
  • 00:43 The milestone chart shows then events on a timeline
  • 00:47 which I will illustrate on the next slide.
  • 00:49 I use the milestone chart to make certain that I don't overlook key
  • 00:52 events in a complex program.
  • 00:54 I also use it as my primary reporting tool with senior management.
  • 00:58 On the milestone days, we have something to talk about.
  • 01:01 And between those days the project team has no new news.
  • 01:06 Let's look at some examples.
  • 01:07 This is the pipeline view of a milestone chart.
  • 01:10 As you can see, we have all of the months going across the top line, a pipeline, and
  • 01:15 all the milestones shown when they are scheduled to occur in each month.
  • 01:19 The other view is a calendar view.
  • 01:21 The milestones are identified in both views, but
  • 01:23 in the calendar view, each milestone is listed down the side and
  • 01:27 then the date is shown on the adjoining calendar.
  • 01:30 There are several recommended steps to create a milestone chart.
  • 01:34 Step one, aggregate all your project deliverables into the appropriate phases.
  • 01:39 If you use the project management methodology,
  • 01:41 this is probably already been done for you.
  • 01:44 Once you have the deliverables in phases, set a duration on the calendar for
  • 01:48 each phase.
  • 01:49 Now, set your milestones.
  • 01:51 Each phase start in end point is probably a milestone since they represent important
  • 01:56 decision events with respect to the project deliverables.
  • 01:59 Missing these dates will likely result in missing the project end date.
  • 02:03 Some of the major deliverables may be scheduled to complete at the end of
  • 02:07 the phase but some might be scheduled for completion in the middle of a phase.
  • 02:11 Show those major deliverables as milestones
  • 02:14 since they are a good indication of project progress and
  • 02:17 since the stakeholders typically are concerned about them.
  • 02:20 There may be other key project decisions within each phase that should be milestones
  • 02:25 because of their impact on the project and the project results.
  • 02:28 But they are not deliverables, include these as milestones also.
  • 02:32 For example, you may need to make a decision to select a key supplier for
  • 02:36 the project.
  • 02:37 The supplier selection is not a deliverable.
  • 02:39 But picking the correct supplier in a timely fashion
  • 02:42 will impact many other deliverables.
  • 02:45 Supplier selection should be on your milestone chart.
  • 02:48 Some hints and tips when creating milestones.
  • 02:51 Make sure that the milestones are meaningful to the stakeholders.
  • 02:54 You'll be reporting on the status of these items to them.
  • 02:57 Make it relevant.
  • 02:59 Milestones should be events.
  • 03:00 The milestone is a point in time, not all the work that leads up to that point.
  • 03:05 Put the work in other tasks that are supporting the milestone using
  • 03:08 the deliverables deployment technique.
  • 03:10 The milestone should be a pass or fail condition, a yes or no answer.
  • 03:15 A selection of X over Y.
  • 03:18 Finally, if possible, put at least one milestone in each month.
  • 03:21 That way, you'll have something significant to report each month and
  • 03:24 can show you are making progress on the project.
  • 03:27 The milestone chart is the best schedule chart to keep both your team and
  • 03:32 stakeholders focused on risk reduction and project progress.

Lesson notes are only available for subscribers.

PMI, PMP, CAPM and PMBOK are registered marks of the Project Management Institute, Inc.

Gift this course