March 18, 2013
Work Breakdown Structure
A work breakdown structure is a product-oriented family tree subdivision of the hardware, services, and the data required to produce the end product (Kerzner, 2009). The work breakdown structure is considered one of the most important documents of a project because it provides a framework from which many aspects of a project can be structured around e.g. scheduling and budget. The work breakdown structure also provides the opportunity to see which objectives are dependent upon the completion of other task within the project. Skipping the WBS could cause delays, confused tasking by team members, and project overruns.
The first step in the creation of a work breakdown structure is creating the project scope. Creating the project scope will set boundaries for the project, which will enable the project manager to rein in requirements that fall outside of the project boundaries. The next step prior to the creation of the work breakdown structure is requirements gathering. This is none other than the collection of information or data, which can be either technical or operational in nature, which identifies the project deliverables. By identifying the project deliverables project managers are able to create a work breakdown structure that divides each objective and sub-task down to the lowest level possible.
The RCT Lab Database is a project that is essential to the future success of River City Testing. The work breakdown structure for the RCT Lab Database Project has five essential objectives, each with varying number of sub-objectives. Each objective and sub-objective have been segmented according to area of work. The main reasoning behind choosing the objectives, was simply because each objective was identified as the milestones that would be easiest to measure for progress.
The first objective for the RCT Lab Database Project is Approval. The...