Ahh…the project. Who among us has never had to do one? No matter what line of work we’re in, we all have at one time and/or another engaged in projects. Anything from planning an event such as a small dinner gathering to building infrastructure like bridges and highways comes under the purview of a project. But did you know that the success of projects is determined in large part by the amount and quality of project planning?
The Project Management Body of Knowledge defines a project plan as “a formal, approved document used to guide both project execution and project control.” However, there are many occasions when a “formal, approved document” may seem over-the-top (e.g., dinner party planning). But no matter the size of the project, having some type of documentation to guide you through execution is recommended.
Consider this. Successful projects can typically be traced back to planning work that can take up to 80% of the project manager’s (and others’) time. What, you ask? When do they have time to actually execute the plan? You may be surprised to learn that the process of planning projects touches all nine areas of project knowledge control areas, whereas the execution process covers only five areas. In fact, of the five project processes (initiation, planning, execution, control, and closing), only initiation and closing have less steps than execution.
How do you make sure you have a fool-proof project plan? Here are five considerations:
Define the purpose. Why are you doing the project in the first place? If you don’t know why, then you won’t know how to plan for the project, either. Knowing the purpose will help you define what success looks and feels like for the project.
Allow freedom to happen, but don’t lose control. Identify what needs to be in place (e.g., policies, procedures, standards) to ensure project success. Then put this in place and trust your project team to move the project forward.
Engage your team. Use brainstorming to fill in the gaps in your plan. Mind mapping used during brainstorming allows everyone to “see” the gaps and makes them easier to fill. A picture is worth more than a thousand words.
Write the plan. Organize your plan in a logical sequence so that both left-brain and right-brain people will be able to glean understanding. Use a simple “at a glance” template and add detail in an appendix. Below is a template that I really like. It captures the “define-measure-analyze-improve-control” principles from Lean.
Make decisions. As you implement your project plan, regularly keep checking the plan. Modify the plan during implementation, as necessary. Remember, plans are just that – plans. They serve as a guide in the process. Adjustments can and should be made to fit the reality of implementation.
Your complete project plan will include assumptions and decisions about the project as well as the project’s estimated (and approved) scope, cost, and schedule. Another advantage to having a project plan is that it helps to facilitate communication among stakeholders – they don’t need to guess about the project, since all the details are written in the plan. And that in itself can be counted as a successful outcome of your project!