In today's fast-paced business world, proper project planning can often take a backseat to other objectives. Employees are asked to leap into the project before the scope or Work Breakdown Structure is even defined. Does this scenario sound familiar? Your frazzled boss comes running into the room with a hot new project that needs to be completed ASAP. He tells you that there is no time to waste on discussing the project and wants you to get to work on it pronto. Essentially he is asking you to skip the most critical phase of the project--planning.
I have worked with many different project teams in many different industries and have discovered that the majority of project teams make the same mistake when developing project plans: they typically begin with determining how the work will proceed prior to defining the project itself or the Work Breakdown Structure that will be required. In other words, most project teams "put the cart before the horse."
Steps to a Well-Defined Project Plan
Fortunately, the project management discipline has defined standard project planning processes that are intended to provide project teams with guidelines for developing a well-defined and realistic project plan. Though elementary in nature, the following steps are beneficial in formulating a comprehensive and workable plan.
- Define the scope
- Identify the steps, sequence the work, and determine the timeframe
- Allocate the resources
Once the organization's management has formally authorized a project to proceed, it is imperative that the scope is properly defined. The scope definition and decomposition processes are designed to help the project team establish the boundaries of the project. Essentially, this is the phase of project planning where the organization answers the "what" questions associated with the project.
The primary technique for defining and decomposing scope is the Work Breakdown Structure (WBS). The WBS is a deliverable-oriented grouping of the project components that illustrates and depicts the scope of the project. In essence, it serves as the organizational chart for a project by taking deliverables and breaking them down into smaller, more easily managed pieces. A Work Breakdown Structure working session not only allows the team to define the content of the project (general rule: if it is not in the WBS, it is not in scope), but it also encourages early buy-in from key stakeholders as they contribute to the project planning process.
Activity Definition, Activity Sequencing, and Schedule Development
Once we have approved the Work Breakdown Structure, the team can identify how the project deliverables will be produced. With activity identification and definition, the team is determining "how" the project's scope (i.e. Work Breakdown Structure elements) will be delivered. At this point in the project planning, the team should not be concerned with how long, who, or how much specific activities will take to complete. This process is more concerned with the activities and tasks (actions) required to deliver the committed project work. To accomplish this phase of project planning, use techniques such as brainstorming, seeking expert judgment and gathering historical and background information.
Teams can now decide the order of the activities and their associated durations. These steps will help teams determine the overall project schedule (when) and its associated critical path (how long). By definition, the Critical Path is the longest time path on the project's network diagram, thus representing the minimal amount of time required to complete the project. At the conclusion of these steps, a project team can understand when the project can be optimally completed based on relationship of activities, dependencies, sequence and duration.