Overview:
Before we get into the elements of the work breakdown structure we should invite the question, ‘Why do we requirement to breakdown the work structure in the first place?’ That is, we should be conscious of the benefits to a project.
Project control:
Supposing that we operated a project, from beginning to end, with no thought of what is going on in between, then control is surrendered. In this circumstance, a project will taste minimal success. That’s why, dissecting the project into small steps will help control. Precisely how you will break it down is a different issue.
Milestones:
Dissecting the project into smaller steps helps the generation of milestones. These are critical junctures in the project which allow a pause. The project team may then assess project deliverables at this point, assess any other concerns and take the required helpful actions. Ordinarily, project management is achieved by exception, so everything ought to be fine unless somebody says otherwise. The milestone allows a possibility to check progress.
Milestones allow recognition of effective progress among the project team members which serves to increase motivation.
Much easier for people to manage:
Smaller work packages make it much easier to manage, ordinarily, since the time period is a great deal briefer. Whenever this holds, review of resource needs, costs and risks is a lot more precise. Control of spending grows easier. Plans with respect to the subsequent stage could be taken into account much more precisely as well. This is since future decisions will be hinged on superior details from the prior step.
List of all elements:
The work breakdown structure is regularly just referred to as WBS. Essentially, it is simply a listing of all of the elements that need completing before the project is able to complete. That is all the WBS is. Lots of people will get this confused with the project schedule. Nonetheless, until these individual parts are linked to each other, by means of timelines and dependencies, you’ll simply have a listing and no schedule. The list begins by way of the overall project goal and is steadily divided into smaller and smaller components. Only at that point are task durations and dependencies thought about to produce the project schedule.
By department:
It is usually the position, that every department will generate their very own work breakdown structure and provide task timeframes together with dependencies. When it is in place, it is then appropriate to consider the effect on tasks present in different departments. After this is done an initital draft of the total schedule may be generated.
Work packages and PRINCE2:
PRINCE2 treats each individual activity a little bit differently. Each activity will be refered to as a work package and each one will provide an output with criteria for its own success. Until these are complied with the work package is not complete. This process offers Team Managers a series of tolerances to work by.
Work packages are included in the section ‘Controlling a Stage’ with respect to PRINCE2 2009 and in the component ‘Controlling a Stage (CS)’ and the sub-process ‘Authorising Work Package (CS1)’ for PRINCE2 2005.