Amacom - Modern Project Management (Ocr) - 2001 ! - (By Laxxuss)

This top down approach reflects the way the overall

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: arriving at what the work packages should be. Rather than dividing the work into the individual tasks that will appear in the project schedule and later gathering the tasks together into packages as advocated by some, we prefer to proceed in a "top-down" fashion. This top-down approach reflects the way the overall work will proceed. Usually, there is a specific way the work is conducted on a project. For example, if the project consists of building a ten-story building, one would not expect to begin building the tenth story first, before the foundation was laid and the lower nine stories were constructed. Page 18 In order to facilitate our thinking about project management, we now introduce an example project that has been devised to be extremely simple. We will use this example project in what follows to explain project management concepts and how to use the project management tools furnished with this book. This example project is not intended to be entirely realistic; rather, it was designed to be simple, yet realistic enough to be useful. The example project is to build a small, 5,000-square-foot building. In order to build this building, it will be necessary first to construct a foundation, then to build the structure, and finally to install the plumbing system, the electrical system, and the heating and airconditioning system. Consequently, we first subdivide the project into three subcomponents that we will call the foundation component, the structure component, and the systems component. In fact, we introduce some new terminology here for distinguishing the components of our subdivision. We call these components control packages , as opposed to work packages. The reason for this is that they are too large to be work packages; yet they are meaningful components both conceptually and, later, for project control. So we will have control packages that we will refer to as "Foundation," "Structure," and "Systems." We can represent this hierarchically as shown in Figure 2 -1. Figure 2-1. Subdivision of example project into control packages. Page 19 Notice that the hierarchy positions of these control packages are labeled 1, 2, and 3. Notice also that we are treating the whole project as a control package, which is at hierarchy position " 0." We have given a name to the "top-level" or total project control package, namely "Example Project." It is customary to label control packages this way. Next we subdivide these control packages further. For example, we subdivide the Foundation control package into four new packages that we label 1.1, 1.2, 1.3, and 1.4. This is the same way that sections in a document are often labeled. These labels are called the package identifiers or package IDs . They are used to show how the work content unfolds in much the same way that sections in a book show how the content of the book unfolds. Continuing our subdivision of these control packages, we sub...
View Full Document

Ask a homework question - tutors are online