I have an assignment in my project management unit where I have to compile a WBS for a hypothetical project. Thank you so much for this, this has been more useful than the two and a half video lecture I sat through
Andy, this was very helpful. I love the post it notes method of creating a WBS and I can't wait to use it with my colleagues on our next project. Thank you!
Thanks for the feedback! Let me know how it goes! If you lead teams and projects, you may find our podcast helpful as well. See PeopleAndProjectsPodcast.com. I wish you much continued success!
Again, ,thank you for your videos on how to create and use a WBS! I agree, Post-its are great for brainstorming. They're so "low tech", they don't seem an intimidating tool, making it easier for folks to engage. Also, love the creativity on how to use the Delphi approach :)
Thanks for the kind feedback, Mohamed! I appreciate it! We have some additional videos on sequencing/network diagram (ua-cam.com/video/H-1Ab30_rrM/v-deo.html) and critical path (ua-cam.com/video/oP9RiG7vSrk/v-deo.html). Let me know if you find them helpful! Andy PeopleAndProjectsPodcast.com
Hey Andy Thank you for sharing this I particularly like the Before-During-After overall structure I'm curious: what steps would you recommend to enable one use the WBS to design an effective organization/team? Thanks again
Hi! Such an interesting question! Technically, a WBS is used to decompose the scope--to understand the work to be done for a project. But it's really just a way to do a top-down breakdown of anything. A typical organizational chart is rather similar so I suppose you could use some variation of it to design an organization. Before you do a WBS, you have a project charter and scope statement. The rough equivalent for an organization/team is to make sure, ahead of time, that you understand things like mission, strategy, etc. From there you could breakdown the organization in whatever manner that would best serve the mission and strategy. It's an intriguing idea! Thanks!
Thanks Patrick! One way virtual teams handle this is by using some cloud-based collaborative tools, such as Trello and Asana. You could also do a video conference where you share the desktop of someone that is using your in-house tool. Nothing beats face-to-face, but sometimes an organization will have technology that can be leveraged to help. Let me know what follow-up questions you have! PeopleAndProjectsPodcast.com
Nice presentation; however, I am still trying to figure out why would you place activities on a WBS when it really should be a list of Deliverables. Thanks.
That is a great observation, Taffy! Thank you for mentioning that! Technically, activities do not show up on a work breakdown structure. In practice, it happens all the time, especially for smaller projects. By design, the lowest level of a WBS is a work package. Some organizations only include deliverables, as you mention. But the big picture remains: use a WBS to decompose the project. Thanks again for adding your voice to the conversation, Taffy!
Thanks again for asking the question, Taffy! If you're studying for the exam, I wish you much success! Let me know if you have any follow-up questions!
Nice video. thanks! I like visual tools. what you construct by making things visible and discussing it with the group is a 'shared mental model'. You might take a look into this psychological concept.
Hi, Tavinee. Thanks for leaving feedback. Are you saying the video quality is murky? Or the explanation of the topic? I'd be glad to answer any questions you have if it's the latter. Thanks!
Delphi? Really? Delphi is an iterative process in which the participants do a second round to glean the better ideas and discard the less workable. After the 3rd or 4th round, the few remaining items have the support of most in the group and are considered the most viable given the iterative review process. In short, Delphi goes from many down to a few. What he is REALLY demonstrating is .... wait for it ... brainstorming using written input instead of verbal outbursts. A good WBS needs the broadest view possible to uncover the most sensitive or highest risk task, as well as as thorough a compilation of tasks needed. Case closed ...
Thanks for joining the discussion, Steve. Yeah, you're correct. It's not anything close to a pure Delphi. I learned it as "delphi" and taught it as such for some time. Over the years I've found many other names/techniques that have similarities to the idea we're trying to get across (such as brain writing, nominal group technique, and others). But your way of summarizing it gets to the core. For anyone who wants more on what Steve is talking about, some potential further reading are at www.projectsmart.co.uk/delphi-technique-a-step-by-step-guide.php and pmbasics101.com/delphi-technique-in-project-management/
Hah! I suppose that's true, Frank! An observation many people have about documentaries is that they're almost always too long, and the same thing can be true of training videos. Some people find this content obvious--others find it revolutionary. A constant challenge for me is to find the balance. I appreciate you sharing your feedback--it will encourage me to always strive to keep things as concise as possible.
Extreme learning within few minutes with fun... thanks Andy.
I have an assignment in my project management unit where I have to compile a WBS for a hypothetical project. Thank you so much for this, this has been more useful than the two and a half video lecture I sat through
Ah, thank you so much for the kind comments about the video! Hope your class goes great!
Andy, this was very helpful. I love the post it notes method of creating a WBS and I can't wait to use it with my colleagues on our next project. Thank you!
Thanks for the feedback! Let me know how it goes! If you lead teams and projects, you may find our podcast helpful as well. See PeopleAndProjectsPodcast.com. I wish you much continued success!
Thanks Andy! Very practical advice, really helped me!
Thanks Ulrich! I appreciate you taking the time to reply!
PeopleAndProjectsPodcast.com
Again, ,thank you for your videos on how to create and use a WBS! I agree, Post-its are great for brainstorming. They're so "low tech", they don't seem an intimidating tool, making it easier for folks to engage. Also, love the creativity on how to use the Delphi approach :)
Thanks Lara! Let me know how it goes when you try it in a project!
PeopleAndProjectsPodcast.com
This was great, other than 8 yrs of technology advances, the content was educational. cheers
thats some high quality mic and speaking tonality right there sir!
thx for the lecture
Thanks for the feedback! Much appreciated!
This is a great video! Thanks Andy
Thank you, Manolo! Much appreciated!
Just perfect!!!
Thank you
Thanks, Mike! I appreciate the feedback!
Great practical video! Cheers!
Thank you!
thank you much appreciated.
Thanks, like your attitude.
Thanks! My pleasure to share this!
Thx Andy ... Nice one
thank you so much and i hope see more helpful videos like that
Thanks for the kind feedback, Mohamed! I appreciate it! We have some additional videos on sequencing/network diagram (ua-cam.com/video/H-1Ab30_rrM/v-deo.html) and critical path (ua-cam.com/video/oP9RiG7vSrk/v-deo.html). Let me know if you find them helpful!
Andy
PeopleAndProjectsPodcast.com
Good. Short and to the point (delphi). True, although half the time the decision makers (stakeholders) are too busy.
Thanks Yasar!
Thank you !!!!!!!
Liked it! Thanks!
Thanks Maya!
Hey Andy
Thank you for sharing this
I particularly like the Before-During-After overall structure
I'm curious: what steps would you recommend to enable one use the WBS to design an effective organization/team?
Thanks again
Hi! Such an interesting question! Technically, a WBS is used to decompose the scope--to understand the work to be done for a project. But it's really just a way to do a top-down breakdown of anything. A typical organizational chart is rather similar so I suppose you could use some variation of it to design an organization. Before you do a WBS, you have a project charter and scope statement. The rough equivalent for an organization/team is to make sure, ahead of time, that you understand things like mission, strategy, etc. From there you could breakdown the organization in whatever manner that would best serve the mission and strategy. It's an intriguing idea! Thanks!
@@PeopleAndProjectsPodcast Thank you for your brilliant input
I'm grateful
My pleasure! Have a great week!
Thank you Andy, any tips for doing this on a conf call?
Thanks Patrick! One way virtual teams handle this is by using some cloud-based collaborative tools, such as Trello and Asana. You could also do a video conference where you share the desktop of someone that is using your in-house tool. Nothing beats face-to-face, but sometimes an organization will have technology that can be leveraged to help. Let me know what follow-up questions you have! PeopleAndProjectsPodcast.com
Nice presentation; however, I am still trying to figure out why would you place activities on a WBS when it really should be a list of Deliverables. Thanks.
That is a great observation, Taffy! Thank you for mentioning that! Technically, activities do not show up on a work breakdown structure. In practice, it happens all the time, especially for smaller projects. By design, the lowest level of a WBS is a work package. Some organizations only include deliverables, as you mention. But the big picture remains: use a WBS to decompose the project. Thanks again for adding your voice to the conversation, Taffy!
Got it... Fantastic stuff!
Thanks again for asking the question, Taffy! If you're studying for the exam, I wish you much success! Let me know if you have any follow-up questions!
Nice video. thanks! I like visual tools. what you construct by making things visible and discussing it with the group is a 'shared mental model'. You might take a look into this psychological concept.
Thanks! I will definitely look into that shared mental model idea. Thank you!
Helpful article to reinforce your point: hbr.org/2011/06/building-a-shared-mental-model. Thanks again!
Great
I can use this on my honeymoon lol
I personally love that idea! Pass the link to your fiance! Hah!
Andy Kaufman Thanks Andy! I used your videos to help me pass my Comptia Project +. I plan on moving to the CAPM next.
expect a naked guy next when changing clothes..haha
The video is not clear (murky)
Hi, Tavinee. Thanks for leaving feedback. Are you saying the video quality is murky? Or the explanation of the topic? I'd be glad to answer any questions you have if it's the latter. Thanks!
Charell Williams was here. I got the pen and I got the pad. LETS GTFOH. Lol another lefty.
Long live lefties! Hah!
Dorothy Effect ahahahahahahahahahahaha!!!!!
Hah! I wish I could take credit for the joke! I'm not sure who came up with it, but I see it all the time! :)
Delphi? Really? Delphi is an iterative process in which the participants do a second round to glean the better ideas and discard the less workable. After the 3rd or 4th round, the few remaining items have the support of most in the group and are considered the most viable given the iterative review process. In short, Delphi goes from many down to a few. What he is REALLY demonstrating is .... wait for it ... brainstorming using written input instead of verbal outbursts. A good WBS needs the broadest view possible to uncover the most sensitive or highest risk task, as well as as thorough a compilation of tasks needed. Case closed ...
Thanks for joining the discussion, Steve. Yeah, you're correct. It's not anything close to a pure Delphi. I learned it as "delphi" and taught it as such for some time. Over the years I've found many other names/techniques that have similarities to the idea we're trying to get across (such as brain writing, nominal group technique, and others). But your way of summarizing it gets to the core.
For anyone who wants more on what Steve is talking about, some potential further reading are at www.projectsmart.co.uk/delphi-technique-a-step-by-step-guide.php and pmbasics101.com/delphi-technique-in-project-management/
you rambled on and on and on
Hah! I suppose that's true, Frank! An observation many people have about documentaries is that they're almost always too long, and the same thing can be true of training videos. Some people find this content obvious--others find it revolutionary. A constant challenge for me is to find the balance. I appreciate you sharing your feedback--it will encourage me to always strive to keep things as concise as possible.
hi Andy, please can i get your email?