Which approach do you use for planning in your projects? Or, do you use a hybrid of both?
What do you think are the benfits of each approach too?
Product-based Planning Vs Work Breakdown Structure
-
Mohamed.Benmerikhi
- Expert Member
- Posts: 57
- Joined: Thu 20 Sep 2012 10:19 am
- Location: France
Hi there,
Generally speaking product-based planning precedes the work breakdown structure. However, there are cases where for instance, product development involves and R&D function, in which case it would be difficult to attribute whole sub-product systems to one team of researchers. If this is the case, then WBS would be more adequate. It allows you to distribute the actions or tasks to the relevant actor or teams in terms of their functional areas. So, appointing an action leader may be a requirement. Additionally, a work package leader is sometimes required as well.
If the product being developed has idenitfiable sub-systems and known processes for their implementation, in other words, it presents less technological complexity, then it would make sense to use product-based planning.
Cases where certain sub-systems or components (of the product being developed) are less complex, requiring known methods for their implementation, while others present novel processes with an innovative character, then a hybrid of both product-based planning and WBS can be used.
Best of luck
Mohamed Benmerikhi
Generally speaking product-based planning precedes the work breakdown structure. However, there are cases where for instance, product development involves and R&D function, in which case it would be difficult to attribute whole sub-product systems to one team of researchers. If this is the case, then WBS would be more adequate. It allows you to distribute the actions or tasks to the relevant actor or teams in terms of their functional areas. So, appointing an action leader may be a requirement. Additionally, a work package leader is sometimes required as well.
If the product being developed has idenitfiable sub-systems and known processes for their implementation, in other words, it presents less technological complexity, then it would make sense to use product-based planning.
Cases where certain sub-systems or components (of the product being developed) are less complex, requiring known methods for their implementation, while others present novel processes with an innovative character, then a hybrid of both product-based planning and WBS can be used.
Best of luck
Mohamed Benmerikhi
Gotcha!
Thanks.
If it is possible to assertain the sub-products of a product, then use Product-based planning and then WBS to delivder those products.
If the products are ambiguous, and you are unable to define them, then use the WBS method.
Thanks.
If it is possible to assertain the sub-products of a product, then use Product-based planning and then WBS to delivder those products.
If the products are ambiguous, and you are unable to define them, then use the WBS method.
-
Mohamed.Benmerikhi
- Expert Member
- Posts: 57
- Joined: Thu 20 Sep 2012 10:19 am
- Location: France
Hi,
If a project involves an innovative system consisting of various components, some of which require known processes and an established technology, with some others innovative, it is a rather complex situation. The reason being, depending ob the architecture of the system, you would need system integration (at some point) to test the viability of the prposed system, then a hybrid of both product-based planning and WBS would both be needed.
Remember that the R&D function blurds the picture. You do not necessarily habe a stable task structure. Unknown tasks cannot be defined upstream with relative precision.
Regards
Mohamed Benmerikhi
If a project involves an innovative system consisting of various components, some of which require known processes and an established technology, with some others innovative, it is a rather complex situation. The reason being, depending ob the architecture of the system, you would need system integration (at some point) to test the viability of the prposed system, then a hybrid of both product-based planning and WBS would both be needed.
Remember that the R&D function blurds the picture. You do not necessarily habe a stable task structure. Unknown tasks cannot be defined upstream with relative precision.
Regards
Mohamed Benmerikhi