Work Breakdown Structure (WBS) Template
This Project WBS Template is free for you to copy and use on your project and within your organization. We hope that you find this template useful and welcome your comments. Public distribution of this document is only permitted from the Project Management Docs official website at:
Work Breakdown Structure
City, State Zip Code
The WBS is a view into the project which shows what work the project encompasses. It is a tool which helps to easily communicate the work and processes involved to execute the project. The Project Manager and project team use the WBS to develop the project schedule, resource requirements and costs. There are many ways you can present the WBS for your project; this template provides many of the most popular layouts from which you can choose. Depending on where in the Project Plan you're putting the WBS a different layout may be more suitable for you. For instance many Project Managers include a high level WBS within the project plan, then a detailed version as an appendix to the plan. You may find that you prefer one layout for a high level WBS and a different one for a detailed WBS.
In order to save space in this template we only developed the WBS examples down to the third level. In your project you will want to develop them down to a much more detailed level using the 8 to 80 rule (where the WBS is broken down to where a work package contains between 8 and 80 hours of work to complete).
The Work Breakdown Structure presented here represents all the work required to complete this project.
The outline view presents an easy to view and understand layout for the WBS. It is also a good layout to use when developing the WBS because you can easily make changes, especially since the Microsoft Word auto numbering feature updates the WBS Code automatically.
1. Widget Management System
1. Evaluation & Recommendations
2. Develop Project Charter
3. Deliverable: Submit Project Charter
4. Project Sponsor Reviews Project Charter
5. Project Charter Signed/Approved
1. Create Preliminary Scope Statement
2. Determine Project Team
3. Project Team Kickoff Meeting
4. Develop Project Plan
5. Submit Project Plan
6. Milestone: Project Plan Approval
1. Project Kickoff Meeting
2. Verify & Validate User Requirements
3. Design System
4. Procure Hardware/Software
5. Install Development System
6. Testing Phase
7. Install Live System
8. User Training
9. Go Live
1. Project Management
2. Project Status Meetings
3. Risk Management
4. Update Project Management Plan
1. Audit Procurement
2. Document Lessons Learned
3. Update Files/Records
4. Gain Formal Acceptance
5. Archive Files/Documents
The hierarchal structure is similar to the outline view but without indentation. Although this format is more difficult to read, it may be useful where you have many levels and indenting each level would make the table to large to fit into a document. |Level |WBS Code |Element Name | |1 |1 |Widget Management System | |2 |1.1 |Initiation | |3 |1.1.1 |Evaluation & Recommendations | |3...
Please join StudyMode to read the full document