Download Approaches to Creating a Work Breakdown Structure (WBS) in Project Management and more Slides Human Resource Management in PDF only on Docsity!
Approaches to Developing WBSs
Using guidelines: some organizations, like the DOD, provide guidelines for preparing WBSs The analogy approach : review WBSs of similar projects and tailor to your project The top-down approach : start with the largest items of the project and break them down The bottom-up approach : start with the specific tasks and roll them up Mind-mapping approach: mind mapping is a technique that uses branches radiating out from a core idea to structure thoughts and ideas
21
Figure 5-6: Sample Mind-Mapping
Approach for Creating a WBS
22
The WBS Dictionary and Scope
Baseline
Many WBS tasks are vague and must be explained more so people know what to do and can estimate how long it will take and what it will cost to do the work A WBS dictionary is a document that describes detailed information about each WBS item The approved project scope statement and its WBS and WBS dictionary form the scope baseline , which is used to measure performance in meeting project scope goals
24
Advice for Creating a WBS and WBS
Dictionary*
A unit of work should appear at only one place in the WBS The work content of a WBS item is the sum of the WBS items below it A WBS item is the responsibility of only one individual, even though many people may be working on it The WBS must be consistent with the way in which work is actually going to be performed; it should serve the project team first, and other purposes only if practical ***** Cleland, David I. Project Management: Strategic Design and Implementation , 1994 25
What Went Wrong?
A project scope that is too broad and grandiose can cause severe problems Scope creep and an overemphasis on technology for technology’s sake resulted in the bankruptcy of a large pharmaceutical firm, Texas-based FoxMeyer Drug In 2001, McDonald’s fast-food chain initiated a project to create an intranet that would connect its headquarters with all of its restaurants to provide detailed operational information in real time; after spending $170 million on consultants and initial implementation planning, McDonald’s realized that the project was too much to handle and terminated it
27
Scope Verification
It is very difficult to create a good scope statement and WBS for a project It is even more difficult to verify project scope and minimize scope changes Scope verification involves formal acceptance of the completed project scope by the stakeholders Acceptance is often achieved by a customer inspection and then sign-off on key deliverables
28
Best Practices for Avoiding Scope
Problems
- Keep the scope realistic: Don’t make projects so large that they can’t be completed; break large projects down into a series of smaller ones
- Involve users in project scope management: Assign key users to the project team and give them ownership of requirements definition and scope verification
- Use off-the-shelf hardware and software whenever possible: Many IT people enjoy using the latest and greatest technology, but business needs, not technology trends, must take priority
- Follow good project management processes: As described in this chapter and others, there are well-defined processes
30 for managing project scope and others aspects of projects
