3.2 Work Breakdown Structures

This video is about work breakdown structures For project management simulations specifically aimed at students of project management, visit www.ablesim.com

[@camshaft78]

Thanks Andrew, explanations like this make the information easier to understand.

[@maxpj9389]

You provide such detailed clarity!!! Love It! This tutorial is a great road map for Project Work Breakdown

[@ablesim6609]

Many thanks for your comment!

[@maxpj9389]

With much gratitude to you!!

[@vision6D]

Hello, Watched your video with attention as I also do videos about project management. I must say that I appreciated your different way to breakdown and I share your point of view. Have a great day.

[@jjglj]

great tutorial video, thanks for uploading

[@andrewbell-projectmanageme1434]

For project management simulations specifically aimed at students of project management, visit www.ablesim.com

[@didier-dirksenbraeckman8629]

First, let's start with some basics; the PMBOK® describes the work breakdown structure as "a deliverable-oriented hierarchical decomposition of the work to be executed by the team". This is a way of describing the work so that the team knows exactly what work is needed in order to meet the goals of the project. In many cases, a work breakdown structure is the first transition of organizational goals into real work that people can actually perform. It helps to provide clarity of the scope for the project and "breaks down" the scope into whole work units. A work breakdown structure is deliverable-oriented. So what is a deliverable? In a word, it can best be described as a noun. What is the difference between "write xyz specifications" and "xyz specifications"? One describes the end product and the other describes a single step to produce it. The end product is described as a noun without a verb. When you start using verbs, then you are in another process of the PMBOK: Define Activities ! Please see WBS Standard of PMI - 4.2.1. bullet 9

[@ablesim6609]

Great, we are in violent agreement. The deliverable is the specification. To achieve that we have to break it into manageable tasks, in the correct order, and assignable to relevant staff. That may include "Define Specification", "Write Specification", "Approve Specification", "Circulate Specification". The product is the deliverable - the specification (noun). The tasks to create it require a verb, and a verb-noun for clarity.

[@gerrymccarey4754]

Thank you.

[@saviourndaba6269]

Thank you God bless you

[@gsiyoum]

thanks so much

[@hernanperez912]

The WBS is or should be Deliverable based, breaking it down by Department or Funcional Organization is not a good practice

[@andrewbell-projectmanageme1434]

I believe that most engineering companies now use a phased approach. Functional organisations are historical for large companies, who are now mainly matrix/project based. However I think smaller companies are very often departmentalised, and so may use a function based structure.

[@rerere1973]

This lecture is not compatible with PMI, for all the professional who is following PMI this lecture not for you, it's for the UK PM.

[@didier-dirksenbraeckman8629]

A WBS does NOT contain verbs !!! ONLY NOUNS !

[@ablesim6609]

A Product Breakdown Structure may just contain nouns. This is a project management Work Breakdown Structure, and the tasks in the WBS need a clear VERB "What is being done", and a noun "To what".

[@DodaGarcia]

In the UK they differentiate between Product and Work Breakdown Structures