Project Management

Project Management Central

Please login or join to subscribe to this thread

Topics: Agile, Work Breakdown Structures (WBS)
Agile WBS Planning
I have noticed that during Agile planning, project managers choose easy tasks initially to run with Agile and have quick wins, but sometimes ignore dependencies and major predecessors when carrying out these quick win tasks. This places huge pressure on time when large tasks are to be under taken.

Is there a step where, prior to commencing the first task, to verify that the planned tasks are in sync with project plan and the work planned is in sequence and acheivable in the Agile Runs planned?
Sort By:
Network:4634
Sergio is the best to answer on Agile. I will wait for his response :)
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.
...
1 reply by Chanu Rajagopala
Jan 16, 2017 7:48 AM
Chanu Rajagopala
...
Thanks for the insight and taking the time to provide a educational reply. I have a lot to learn and I am glad to be on a platform where experts share their views for benefit of the larger community.

Regards
Chanu
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/
...
1 reply by Chanu Rajagopala
Jan 16, 2017 7:48 AM
Chanu Rajagopala
...
Thank you for the knowledge share Saket.

Regards
Chanu
Jan 09, 2017 6:11 AM
Replying to Sergio Luis Conte
...
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.
Thanks for the insight and taking the time to provide a educational reply. I have a lot to learn and I am glad to be on a platform where experts share their views for benefit of the larger community.

Regards
Chanu
Jan 14, 2017 9:42 PM
Replying to Saket Bansal
...
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/
Thank you for the knowledge share Saket.

Regards
Chanu
While I understand why you would choose to start with quick and easy features, it's not your best approach. You should start with features that add the most value to your client. These are usually flagged as high priority.

The problem with quick and easy is that you tend to under-design the features which can lead to a lot of rework on the bigger, more important pieces.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Great souls have wills; feeble ones have only wishes."

- Chinese Proverb

ADVERTISEMENT

Sponsors