DVU The Work Breakdown Structure and Software Purchasing Discussion
Description
Review the Work Breakdown Structure (WBS) presented in Week 4: Introduction and Lesson, or the Project Schedule Section E of your Course Project. Select one of the project tasks (i.e., task name) and identify the risk you might encounter in the execution of the task. Next, describe the root cause of the risk and the risk impact on the project objectives (i.e., cost, schedule, quality.).
For example:
- Task WBS index: 1.4.3
- Task name: Transfer data
- Risk identified: Network capacity
- Risk root cause description: Failure during uploads due to low bandwidth
- Risk impact: Project delays and budget overrun
- Risk owner: Network services
*Work Breakdown Structure (WBS): A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables
The creation of the WBS is a process that divides the project work into smaller and manageable pieces of work.
The WBS hierarchical chart of the Getta Byte – Billing System project is presented below.
(Links to an external site.)“>Image Description (Links to an external site.)
To create a WBS, start at the top of what will eventually be the pyramid of deliverables and then break down each level of work into a lower level of more detailed work packages. As this process is repeated, a pyramid of work description evolves and the work of completing the project is broken down. The work packages can be assigned to project team members for completion, their costs estimated, and the activities scheduled.
The WBS also contains index numbers (i.e., WBS index number) to represent each component in the chart. The top-level has a single number and is reserved for the project title. The second level has two numbers and represents the number of milestones, phases, or major deliverables in the project. The third level has three numbers and represents the number of work packages under a milestone.
Finally, It is important to remember that when creating the project schedule, the work packages represent the project tasks. Project task names should start with an action verb. For example, the work package 1.2.1 above should read “Select vendor” when entered into the project schedule.
