Agile WBS Planning

Hehehehe. Thank you very much Anupam. First, there is not agile planning (sorry if I missunderstood the point because english is not my first language). There is planning that you perform inside an agile environment perhaps using an agile software development method (most of them like DSDM or SCRUM becomes to agile solution delivery method). The method is based on a project life cycle which is create based on a life cycle model (adaptative or predictive). You can apply agile with any type of life cycle model. Returning to the point, agile software development methods like DSDM have defined the WBS as a deliverable. Others do not. So, you have to find the use and control of the WBS inside the method.

The general approach we take for decomposition of requirement in agile is dis-aggregation. Where we do more feature breakdown rather than work breakdown. The idea is divide the work in small slice and each slice can be completed, and ensure minimum dependencies among these slices. We can not avoid dependencies we just try to reduce them.

When it comes to planning, we usually do two levels of planning in agile. one is long term (release level, generally for 3 to 6 months duration) and another is short term (2 to 4 weeks duration). The long term planning is more based on features breakdown , where as short term planning is done based on task breakdown.

You may like to explore our short and free program on agile to know more. http://www.izenbridge.com/pmi-acp/free-pmi-acp-introduction/