Now that you have all of that information in the requirements document, let’s start by using that to define the project phases and begin to define the WBS. The WBS shows the work needed to be done to accomplish the project in a logical format. Define your project into phases corresponding to the requirements document you have created, and then break each of those phases into smaller work packages that will end in a deliverable. We are still operating at a somewhat high level so keep your WBS to three or four levels of detail. Much of the requirements you defined will be used to break out the executing process. This is where you start to define what actually needs to be done to make this project successful. Don’t forget to include ‘supporting tasks’; tasks that need to be done in order to allow necessary work to progress. Choose only four of your requirements to further define in your WBS.
A work breakdown structure is a key project deliverable that organizes the team’s work into manageable sections. The Project Management Body of Knowledge (PMBOK) defines the work breakdown structure as a “deliverable oriented hierarchical decomposition of the work to be executed by the project team.” The work breakdown structure visually defines the scope into manageable chunks that a project team can understand, as each level of the work breakdown structure provides further definition and detail