In a hectic business environment, project fundamentals such as scope definition and the Work Breakdown Structure often take a backseat to a “just get going” mentality. It might better be described as the “flail until you fail” approach. Here is the 101 on creating a plan that defines your project from the outset.
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."
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