a. Typically NOT. That will be a part of the Schedule and not the WBS that you create upfront. b. UNLESS, meetings and hiring are a major defining part of the project. For example, consider - "A project to build a Technical Team" or HR team projects. In these situations, meetings are a major part of the project itself - and only in those situations, I would include it in a WBS. In normal cases, where a weekly team meeting would suffice or a 15 minute AGILE SCRUM meeting would suffice, I would not include them in a WBS. I hope that clarifies sufficiently.
heygreene basically if you are doing a major buildings complex.. if holding one house takes more than 80hrs then you should break it up more.. let's say to foundation, painting, install fixtures.. now all those will be the end of WBS as work packages. however if u want to break paint further , let's say per room.. and each room takes maybe 3hrs of work (less than 8).. then you are doing too detailed WBS which makes management less efficient. regards and good luck
8/80 rule - absolutely do not agree - it means. that if I will use it in my construction project I would have a document with 10 000 positions and nobody will work with such a document. Decomposition should be so detailed - that you could work with the document.
Consider this example. A wall may be laid in 8 hours. If you have 5000 workers doing this - it is perfectly fine. But if you create a task that says "Build an office in 40000 person-hours" - then you will have to rethink.
I am a student in a certification course and this was explained beautifully..thank you!
Thanks for the appreciation!
Very clear and clever. Very helpful. Thank you !
Thanks for the appreciation!
Sir please continue your videos.
This stuff helped me to clarify some queries, thanks.
Awesome video, man. Thanks
Thanks for the appreciation!
Likely the most important thing I’ve found to is to define, for each work package, “how will we know it’s finished”?
I like that. As long as it's detailed enough to be scheduled, budgeted, and handed off to the team leader!
i dont know more about WBS & confused about levels of wbs please tell me it with the example of establishing a new business
what is the difference between wbs and Gozinto?
Should meetings and hiring of staff or other project management team tasks along the cycle of the project be depicted in the wbs?
a. Typically NOT. That will be a part of the Schedule and not the WBS that you create upfront. b. UNLESS, meetings and hiring are a major defining part of the project. For example, consider - "A project to build a Technical Team" or HR team projects. In these situations, meetings are a major part of the project itself - and only in those situations, I would include it in a WBS. In normal cases, where a weekly team meeting would suffice or a 15 minute AGILE SCRUM meeting would suffice, I would not include them in a WBS. I hope that clarifies sufficiently.
great stuff. you could add more explanation slides next time
Thanks for the appreciation!
awsome
This is a very easy explanation of everything, but I'm not clear on the 8/80 component.
heygreene basically if you are doing a major buildings complex.. if holding one house takes more than 80hrs then you should break it up more.. let's say to foundation, painting, install fixtures..
now all those will be the end of WBS as work packages.
however if u want to break paint further , let's say per room.. and each room takes maybe 3hrs of work (less than 8)..
then you are doing too detailed WBS which makes management less efficient.
regards and good luck
Can it be used for if I am an Scrum master ?
raj rishi purohit you would rather refer to your backlogs. Exactly the same concept, work packages are Feature or User Stories
8/80 rule - absolutely do not agree - it means. that if I will use it in my construction project I would have a document with 10 000 positions and nobody will work with such a document. Decomposition should be so detailed - that you could work with the document.
Consider this example. A wall may be laid in 8 hours. If you have 5000 workers doing this - it is perfectly fine. But if you create a task that says "Build an office in 40000 person-hours" - then you will have to rethink.