Please provide general information about how to manage a project schedule from start to finish and develop a work breakdown structure in detail.
How would you start the process of constructing a WBS? Who should be a part of the process? How do we manage the process to get a good WBS?
Creating a logical WBS, though a menial task, requires a significant amount of skill. With each project, one must add just enough detail to give stakeholders insight into the inner workings of the project, and do it well enough without over doing it. A renowned project manager once said, "nobody wants to read a WBS with 200 items." But, if you're a person like me, who wants to know every detail about every little thing, a 200 item WBS might not exactly be seen as overkill. I must say that I have seen several decimaled work breakdown structures used by the government that contained more than 100 items, and all of the information provided was key to helping the project stay on task. Needless to say, although there was a lot of information ...
This excerpt provides detailed information about how to create a concise and effective project schedule that will help you stay on task and within the parameters of your budget.
Answers to the following questions are provided in this posting: How would you start the process of constructing a WBS? Who should be a part of the process? How do we manage the process to get a good WBS? We also have to develop costs and assumptions for our project. What assumptions do we need to make? What areas do we need to develop specific new information for, and what areas can use existing information? Where would you be likely to obtain this information? What modifications might be necessary to make the information fit a new project?