Friday, February 19, 2010

Work Breakdown Structures (WBS)

 

While gathering and elicitation of the requirement form the clients, many clients asks me about what is WBS. So, for them, here i have outlined it as per my view in a very simple terms about it. After reading this i am sure even a novice person will understand the excerpts out of it.

WBS typically means “Mapping the project work” , “Break the deliverable down into manageable chunks”, “Schedule of Project”

What is WBS ?

  •  A Work Breakdown Structure is a elaborated/detailed list of all the features/things/tasks that are needed to be delivered and the activities that need to be carried out to successfully complete the any project.
  • Basically WBs is nothing but a common understanding of the project in terms of structures and points.
  • There can be multiple features/sub-tasks under one task. That means descending level of WBS which in turn elaborate the description of minute project elements which needs to be considered.
  • WBS is also used as Feature list/Risk Issues (FE/RI) which list down all the feature lists along with the risk issues and the men effort which needs to put in to develop the particular feature/task.

For whom this WBS is ? This technique is often used by Project Managers during the formal project planning methodologies.

What WBS contains ?Typically WBS contains Scope, Project Deliverables, Resources, Process, Milestones, Assumptions, Time line , Total Cost, Contingency hours, Risk Issues, Comments from PM Team & Client etc.

Why to create WBS ?

  • Carry transparency between Client & Project Management Team :
    • While creating WBS, Project Managers and other stakeholders will be very much clear about as to what they have to provide you to their potential client.
    • At the same time, client when receives it, becomes very clear as what he will receive from the PM Team.
    • So, in nutshell, to be on the same page, WBS plays a vital role.
  • WBS adds value while being with the Project Scope Document.
  • WBS can be one part of either Project Scope Document/Business Requirement Document or can be a standalone document.
  • Before the project will be started, if WBS is in place then client will feel very sure about the deliverables they will get after the completion of the project.
  • In case, if PM team has not developed and deliver the project as per communicated and agreed upon, they can raise the objection while showing the WBS to PM Team.
  • Even for the development team keeps WBS in front of them while developing it ensure that they will not forget any critical things.
  • PM Team will be very clear that they are not going to provide any thing which are not written in the WBS.

Thus, WBS really helps !

How to make WBS :

There are various tools available to create WBS. For example, Microsoft Visio, Microsoft Excel(P.S. – its very easy to use)

Some snaps of WBS to visualize:

tmp8B  
   
tmp80  

Hope, this much information will add on the value to understand WBS.

Stay tuned ! Wave