Reprinted with Permission by Quest Software Nov. 2004


Project Management Tips and Techniques
It is Important to Understand Your Project Start Date

Tom Mochal

Each month, Tom Mochal, President of TenStep, Inc. presents project management tips and techniques for planning and managing a project. TenStep, Inc. has a comprehensive, scalable project management process called TenStep (www.TenStep.com), as well as a project lifecycle process called LifecycleStep (www.LifecycleStep.com). Pipeline readers receive 20% off any TenStep or LifecycleStep purchase by entering the coupon code of "Pipeline" in their purchase.

One of the characteristics of a project is that there is a definite start and end date. This seems simple enough until you start to try to define exactly what these dates mean. There are no universally recommended standards for either date. In many respects, it depends on each organization and whether there are any implications for choosing one alternative over another. Here are some of the options for identifying the project start date. 

  • The idea is generated. This takes the start date back a long way before the project is actually formalized and on the surface may not make sense. However, remember that the definition you choose can depend on what the implication is. You may choose this definition if your company is trying to focus on the time it takes between when an idea is generated until the idea is fulfilled though a project. The concern may be that there is too much time to implement good ideas. If your company wants to minimize this total time span between idea and fulfillment, you might go with an early project start date definition like this. 
     
  • A budget is approved. This definition is a little more concrete than the prior idea. In this definition, an idea has been generated and the idea has made it far enough that a cost/benefit statement has been prepared. The project has also made it through the prioritization process and an actual budget has been approved. Keep in mind that the budget may have been approved during the prior year business planning process. The actual work may not start until the following year. Therefore, this definition again starts the clock early.
     
  • A project manager is assigned. This one is more common. It may be hard to say that a project has started before a project manager is assigned. When the project manager is assigned, the project planning and definition begins and the meat of the project starts. 
     
  • The project definition is approved by the customer. In some organizations the project officially starts when the customer approves the Project Definition document. Some companies require an approved Project Definition and workplan before the project team can be allocated. They do this to ensure that the upfront agreement is in place before project work begins. 
     
  • The project kickoff meeting is held. Using this definition, the planning and definition work is considered to be “pre-project” work. All projects start with a formal kickoff meeting with the client and project team. When the kickoff meeting is held, the planning is completed, the client has approved starting the work and the project team has been allocated. The kickoff meeting is the time to tell everyone that the project is ready to begin.

Why the Start Date is Important

To a certain extent, you might think that it doesn’t really matter when the project starts. Having a somewhat undefined start date does not take away from the fact that the work is a project. It’s obvious that the project started at some point, since there was a point when the work was not in progress and a point where the work is in progress. So, at some point the project did in fact “start”. 

The reason it is important to know the start date is that there may be consequences and incentives based on how long it takes to complete a project. The following are examples of these consequences.

  • Project team accountability. It is hard to hold people accountable for things that are not within their control. For that reason, it makes sense that a project manager is held accountable for the project no earlier than when they are assigned. If the project clock starts before they are assigned it is possible that some decisions were made and some resources expended before they were assigned, and therefore they do not have total control. Likewise, if team members are held accountable for completing a project within budget and on schedule, it is hard to hold them accountable for work and decisions that take place before they are assigned. For that reason, perhaps the project should officially start when the Project Definition and workplan are approved, or after the project kickoff meeting is held. 
     
  • Process improvement. Many companies keep track of the total duration of projects and attempt to shorten the average project duration over time. It is important that everyone within the company use a common starting and ending point. Otherwise the project duration numbers will not be meaningful.
     
  • Financial / accounting. Many projects are considered capital expenditures. Precisely defining when a project starts has consequences in terms of the work that can be capitalized and the work that needs to be expensed.
     
  • Comparisons with other companies. If you compare how long it takes your organization to deliver projects, you want to make sure you have a common definition of start and end dates. If your company considers a project to start when a project manager is assigned and other companies start the clock at the kickoff meeting, it will appear that your company takes longer to deliver projects. 

Would you like to receive project management tips every week? Sign up for the weekly TenStep Project Management Tip of the Week at www.TenStep.com.