Milestones in Project Planning
| Line 53: | Line 53: | ||
When the results are good enough, the milestone is reached and the job is finished <ref name="PMI" />. | When the results are good enough, the milestone is reached and the job is finished <ref name="PMI" />. | ||
After the milestones are determined, they should be listed with the date when the milestone needs to be achieved. It is important to align within the project management team whether the milestones are mandatory, and in that case, which is not. | After the milestones are determined, they should be listed with the date when the milestone needs to be achieved. It is important to align within the project management team whether the milestones are mandatory, and in that case, which is not. | ||
| − | There are multiple ways of displaying a milestone list, it could be as a list or as a Gantt Chart, an example of this is displayed in figure .... <ref name= | + | There are multiple ways of displaying a milestone list, it could be as a list or as a Gantt Chart, an example of this is displayed in figure .... <ref name="PMBOK"> |
During the project, the milestone list should be kept updated and milestones which are achieved should be ticked off. | During the project, the milestone list should be kept updated and milestones which are achieved should be ticked off. | ||
Revision as of 21:11, 3 March 2019
Contents |
Abstract
A good and balanced project plan is a crucial success factor for a project, as insufficient resource planning and unrealistic schedules count for 30 % of the reason when looking at why projects fail [1]. There is a wide range of different approaches and tools used for project planning. This article clarifies milestone planning and how to use it in project management.
According to Managing Successful projects with PRINCE2 is a milestone defined as "an event on a schedule which marks the completion of key activities" [2]. Milestones are a tool used in project management to mark the completion of a major phase in a project. Milestone planning is results-oriented and a milestone should present what is supposed to be achieved at a given time in the project. Milestones may influence the way activities in a project are sequenced. Milestones are targets in the project phase, it does not have a duration, but they need to be completed at before a given date. A milestone list for a project is used to estimate activities duration as well as develop the project schedule [3].
This article will contain two main parts, one with a focus on how to set milestones and a second with a focus on how to implement milestones in the project schedule. The first part of this article will also contain an introduction to project planning and milestones in general. While the second part will contain an example of a milestone chart and how to incorporate it in the project schedule displayed in a Gantt chart.
Introduction
A project schedule is used to obtain a clear overview who and when the project will deliver the products, services or results. According to Project Management: A guide to the Project Management Body of Knowledge (PMBOK guide) Project schedule management consists of six processes [3]:
- Plan Schedule Management
- Define Activities
- Sequence Activities
- Estimate Activities Durations
- Develop Schedule
- Control Schedule
Depending on the size of the project will some of these processes be linked tightly.
There are different scheduling methods, it is the project management team job to determine which method to use, the two most common are critical path or an agile approach. When the project management team has conducted the project-specific data into the six processes, it is possible to create the project schedule by entering the data into a scheduling tool, this is illustrated in figure 1. When a project schedule has been created it should be presented graphically. Often this is done by an Activity list, a Bar/Gantt Chart or a Network Diagram.
Milestone planning
Milestone planning is a way of planning a project on a basis of milestones. A milestone is defined as "an event on a schedule which marks the completion of key activities."[2] Milestones are described as a desired condition or state in the project at a certain point in the timeline of the project. As milestones can be understood by non-experts, is it a good and easy way to keep stakeholders updated and satisfied. As stakeholders can see how the project is developing as more and more milestones are reached [4]. The milestone planning approach differs from traditional project planning, as the focus is on achieving the set goals, instead of executing activities and tasks. When a project is planned from milestones the road to the desired state is not planned. Therefore will it be possible to achieve the state for a milestone in a variety of ways.
When using milestone planning, the mentality of the project team needs to switch from activity-oriented thinking and planning to result-oriented thinking and planning. This is done by answering the question "what should be achieved?" before "how should it be achieved?". The desired results the project management team would like to achieve should be discussed and determined, from this, a milestone plan should be created. A milestone plan should consist of both the desired end result as well as interminate results and indicators.
Milestones in project stages
The milestones have to be decided early in the project stage. The following list contains the phases of project management were milestones figure in.
- Starting up a project - Prepare the outline business case.
- Project manager determines the key milestones.
- Directing a project
- Authorize initiation - The project definition is confirmed by the project board. This should include the confirmation of key milestones.
- Authorize the project - The project plan is validated and the achievability of the project plan and milestones should be approved.
- Initiating a project - Create the project plan
- The project is reviewed, the deliverables and predetermined milestones are checked, they should match the project brief.
- Controlling a stage - Authorize a work package
- The work there has to be done during the project is set into packages. For each package is the milestones, their tolerances, effort, cost, and end date defined.
Defining and setting milestones
The number of milestones and the duration between them is critical. As a general rule, there should be fewer milestones than deliverables but still enough to ensure eventual issues can be detected and solved, so the project plan can proceed as expected [2]. It is important that project managers attach the right importance or value to the milestones, so all the concerned are working hard to achieve the desired results for the milestones. If the milestones do not add value or importance to the project, they end up being trivial.
When conducting a milestone plan there should be a logical dependency between the milestone, see a simple milestone plan in figure ... The figure displays the logically flow milestone to milestone and shows that it is logically impossible to obtain the results form milestone 2 before the results from milestone 1 are finalized. A milestone diagram should not be connected to activities. Some activities start long before the milestone is within a target range, while others first start when the latest milestone has been reached.
A milestone can be many things within a project, there is no rule for what there can be called a milestone. The only important thing is that it should be possible to determine if the results behind a milestone are reached or not. Examples of milestones could be "description of a company current conditions", "delivery of a product", "completion of a room" etc. All depending on which type of project are being managedCite error: Closing </ref> missing for <ref> tag
Cite error:
<ref> tags exist, but no <references/> tag was found
