This is “Nurturing a Feeling of Satisfaction”, section 4.4 from the book Beginning Project Management (v. 1.1).
This book is licensed under a Creative Commons by-nc-sa 3.0 license. See the license for more details, but that basically means you can share this book as long as you credit the author (but see below), don't make money from it, and do make it available to everyone else under the same terms.
This content was accessible as of December 29, 2012, and it was downloaded then by Andy Schmitz in an effort to preserve the availability of this book.
Normally, the author and publisher would be credited here. However, the publisher has asked for the customary Creative Commons attribution to the original publisher, authors, title, and book URI to be removed. Additionally, per the publisher's request, their name has been removed in some passages. More information is available on this project's attribution page.
For more information on the source of this book, or why it is available for free, please see the project's home page. You can browse or download additional books there. You may also download a PDF copy of this book (55 MB) or just this chapter (3 MB), suitable for printing or most e-readers, or a .zip file containing this book's HTML files (for use in a web browser offline).
Project milestones represent significant events on the project. Some project milestones signify external events that provide critical information or resources to the project or an external event that requires information or deliverables from the project.
The client’s board of directors meets on March 15, and the client must report the project progress and submit the project final budget for approval. The project team develops the information needed for the project progress report and finalizes the project estimate by March 10 to provide the client with five days to review the information and make any changes.
Recall that a milestone is an event that consumes no time or resources. In this example, the Provide Client with Report is the milestone event. All the activity to develop and deliver the report takes place before the milestone event.
On March 8, the project team determines that the progress report and estimate cannot be completed by March 10. The team will need one more day to complete the report and estimate. Should the project manager ask the client for a one-day extension? The client may be able to review and revise the information before it goes to the board in four days, but the message to the client has a bigger impact on the project. By missing the deadline, the client can develop the perception that client deadlines are less important, that the project team is unable to complete critical tasks on time, or that the project team is not dedicated.
Instead of asking the client for one more day, the project manager pulls together the project team and asks what it will take to make the milestone date. If the estimator works overtime tonight and the project controls team starts a few hour early on March 9, then the project controls team can work late on March 9 to finish the report. The project administrative staff can come in early on March 10 to do the revisions and make copies, and the reports can be ready by noon. Other activities will have to be delayed and critical staff will work overtime, but the client will get the needed information by the promised date.
Making the extra effort to deliver by the milestone date communicates to the client and the project team the importance of meeting milestones. The client develops confidence that the project team is dedicated to meeting client expectations and that deadlines are important. The extra efforts by the team to meet the client’s critical dates will often result in the client making an extra effort to help the project team meet critical dates.
During the life of a project, the project team encounters a large number of small problems that can cause small delays. A thunderstorm caused the loss of electricity in the office building, and the bidders’ conference had to be delayed one day; a computer virus shut down the use of computers, causing the loss of another day; and the airplane flights were late, so the project reviews were one day late. None of these events caused significant problems for the project, but together they add up to delays that could affect the end date of the project.
Meeting milestones creates better project atmosphere.
© 2010 Jupiterimages Corporation
If these delays continue to add up, then the project end date will begin to slip. As the project nears the completion date, the team will work overtime, decisions will be rushed, and resources will be added to the project to avoid missing the project end date. This type of end-of-project atmosphere will leave a strong lasting impression with the client and usually does not produce a satisfied client.
Project milestones provide the opportunity for the project manager to spread the end-of-project pressure over the life of the project. Project managers add resources, authorize overtime, and expedite work to accomplish what is required to meet the milestone. The project work increases in intensity, motivating project team members to accomplish the work on time until the milestone is achieved. After the milestone is achieved, the project celebrates and acknowledges the success of the team and then begins working toward the next milestone. Project managers use milestones to increase this intensity and focus to keep the project on schedule and prevent the delays of hard decisions to the end of the project.
Meeting milestone objectives reduces stress.
© 2010 Jupiterimages Corporation
This approach allows the project manager to lower the intensity of the project after a milestone is accomplished. After celebrating the successful completion of the milestone, a project manager will often review the future plans and allow the team to reflect on finding new ways of approaching the project work. Adjustments are made to the project work plan and the milestone cycle begins again.
Milestones are rarely evenly distributed over the length of the project. Project managers often select key events and make them milestone events to create roughly equal spacing between milestone dates. On large, multiyear projects, managing to a milestone each quarter provides good timing for the project. On shorter projects, monthly milestones can provide the right timing. On larger, more complex projects, typically a large number of activities can be designated as milestones for the project. On smaller projects, the project manger may need to artificially create milestones.
Project celebrations are a time when the project manager and the management team can thank the project team members for their contribution to the project’s success at various stages of the project. Celebrations for successfully accomplishing project milestones are good examples of creating the opportunity to honestly celebrate. Some projects have birthday celebrations for the team or holiday celebrations, and although these events can be a positive contribution to the project morale, they are not connected to the success of the team in accomplishing project objectives.
Include the client in milestone celebrations.
© 2010 Jupiterimages Corporation
Successful celebrations reinforce the effort and activities that created the success. Successful celebrations communicate appreciation for the energy and commitment of the team, focused on team goals. Successful celebrations communicate progress and confidence to project stakeholders, and successful celebrations share the success of the project with the client and reinforce the meeting of client expectations.
Successful celebrations result from good planning and the application of some basic principles for celebrations. The following are some of the basic principles for developing a successful celebration:
When clients speak at a celebration, their remarks usually provide high praise for the work of the project team. This event provides an opportunity for the client to reflect and appraise the progress of the project team. Often the client concludes that the team is meeting or exceeding expectations. The celebration reinforces that conclusion.
If the client has doubts about some of the project performance but still speaks at the celebration and praises the team, the client may experience cognitive dissonance. The client will typically reevaluate the perception of the project team’s performance and conclude the team really has done a good job. The perception is now consistent with the client’s remarks and the end result is a client perception of a project as meeting expectations.
Understanding and meeting client expectations is a proactive process. The project manager and the project team develop plans and processes that focus on defining both specifications and expectations that are often difficult to quantify. The team executes the project in a way that meets both the specifications of the client and also the more subtle expectations not reflected in the measured data.
Consider a workplace with which you are familiar. If it utilizes milestone celebrations to mark completion of special tasks or phases of work, compare the components of the celebration with those recommended in the text. If it does not, describe how you would use milestone celebrations in this workplace.