How And Why Is The WBS Constructed And How Can It Be Used To Identify Risk.

The work breakdown structure is a hierarchical decomposition of the total scope of work to be carried out by the project team to achieve the project objectives and create the required deliverables. With a WBS, you begin with the desired outcome, then break it down into the smaller deliverables or tasks needed in order to create it.

Why is the WBS constructed:

• ·         Provides a visual representation of all parts of a project.
• ·         Offers an on-going view for management and team members into how the entire project is progressing. 
• ·         Defines specific and measurable outcomes.
• ·         Provides a foundation for estimating costs and allocating human and other resources.
• ·         Ensures no overlap and no gaps in responsibility or resources.
• ·         Minimizes the chance of adding something outside the scope of work or forgetting a critical deliverable.

How is the WBS created:

Here are several inputs you will need to get you off on the right foot:

• The Project Scope Statement
• The Project Scope Management Plan
• Organisational Process Assets

To begin creating a WBS, define level one, the main deliverable of the project. Then add detail to level two as much as possible before moving to smaller chunks of work in level three, and beyond. Divide the overarching project into smaller and smaller pieces, but stop before you get to the point of listing out every action that must be taken.  Always try to define what’s required in the previous level in as much detail as possible before moving to the next levels.  Electronic templates and tools make it easier to record the chart.

Used to identify risk:

Analysing the WBS is a good way to identify potential risks. Each activity and deliverable can be examined for potential risks. WBS forms the basis of a way to identify risks. For each activity at the lowest level of your, identify all of the risks in undertaking the activity.  Start with a set of risk categories, like schedule, scope, budget,  or quality. For each one, break it down to component risks, and continue until you have a full breakdown of all of your project risks. The WBS numbering system will give each risk a unique identifier for use in your risk register.