This preview shows page 1. Sign up to view the full content.
Unformatted text preview: into the example database. You will begin learning how to do this shortly. If you do not have either Microsoft Access 97 or Microsoft Access 2000 installed on your computer, it should not interfere with your ability to understand the project management methods, philosophy, and tools discussed in this book. During the past three decades, many project managers have used these methods and policies manually, without the aid of a computer. On large projects this requires a considerable staff, but it has been done and continues to be done. Packaged within example.mde is the Modern Project toolset. When you open example.mde with Microsoft Access the Main Menu for the Modern Project toolset will be displayed as shown in Figure 2 -3. Assuming you have one of these ver - sions of Microsoft Access available on your computer, start it up and open the example database (example.mde). Your computer screen should now look like Figure 2-3. 2.3.1— Entering WBS Information Now select (click your left mouse button on) the WBS Entry/ Edit Tool button on the left side of the Main Menu. This will cause the WBS Entry/Edit tool to start and display a WBS Edit/ Entry form on your computer screen that looks like Figure 2 -4. The WBS information to be entered is shown in Figure 2-5. The far-left column of Figure 2- 5 is labeled Hierarchy Position. Each control package in the WBS hierarchy has a position within the hierarchy, as previously discussed. The control package's hierarchy position identifier tells what that position is. We have already discussed how these identifiers were chosen for the example project. We chose to label these control package Figure 2-3. Main menu for the Modern Project toolset. Page 29 Unless you have some compelling reason to adopt a numbering scheme other than the one described for the example project, it is recommended that you adopt the scheme in the book, since the tools in the toolset have been tested only using the numbering scheme of the example project. The reports may still work if one does not depart too far from the hierarchy labeling scheme presented in the book. But they have not been systematically tested on any other scheme. It is preferable to avoid having more than six or seven packages under a given summary level control package, but it is possible to have more. There have been studies that indicate our comprehension of hierarchies diminishes when more than six hierarchy elements exist under a single parent hierarchy element. The reporting tools provided with this book have not been tested with more than nine packages under a single parent package at the next level up in the hierarchy. TE hierarchy position indicators as 0, 1, 2, 3, 1.1, 2.1, 3.1, and so on. But we could have used a scheme like 0, 1, 2, 3, 1-1, 2-1, 3-1, and so on, employing dashes between the numbers instead of dots (periods). AM FL Y
Figure 2-4. The WBS Entry/Edit Tool. Team-Fly® Page 30 Figure 2-5. WBS data to be entered for the example project. We note that the hierarchy position field...
View Full Document
This note was uploaded on 01/11/2011 for the course ACC 9 taught by Professor Yeetan during the Spring '10 term at Sunway University College.
- Spring '10