Question

At what level on the WBS should you map the risks?

Answer 1

A Work Breakdown Structure (WBS) is a way of organizing a project by functional areas to segment the work to be done so that it has a logical structure that maps to the overall solution functionality.A WBS might be used at a functional level to break down the overall functionality and/or at a task level to break down both the functionality and the tasks required to implement the functionality.

A WBS is useful to understand the structure of requirements and functionality to see how it all fits together and to make sure that everything is really congruent and consistent with the overall project goals.

It also may be a useful way of dividing the work to be done and/or planning the architecture to implement the solution.

A WBS is more commonly used in a traditional, plan-driven project rather than an Agile project because there may not be enough information upfront in an Agile project to create a detailed WBS. However, a high- level WBS (sometimes called a "Story Map" is still useful in an Agile environment.

Work Breakdown Structure is also helps identify the risks of projects, which are ill defined and where the stated objectives are ambiguous.

Tips to overcome scope Risk.:

The occurrence of scope risks can be minimized with using good planning techniques, clearly defining the project, managing the changes in scope throughout the duration of the project, managing the changes in scope throughout the duration of the project, using risk registers to better manage risks, identifying the causative factors, and the appropriate responses to risky situations and developing greater risk tolerance in collaboration with the customer.