Why do we need to create a WBS for our projects? What purpose does it serve? Why should I waste my time writing on post-it notes and drawing charts when I could be getting my team started on the actual work of the project? Now, I know everyone reading this is a great project manager or team member, so I am sure none of you have ever said comments such as these, but I am sure you have heard them from those "other" project managers who will remain nameless.
However, before we get too deep into how to actually create a WBS let's first look at its purpose. Creating a quality WBS will require a substantial amount of energy, time, and people, but in the end is not rocket science.
It is not nearly as daunting as it sounds. Wow! That is a lot of buzz words and jargon, but do not worry. The Work Breakdown Structure (WBS) is defined by A Guide to the Project Management Body of Knowledge 3rd Edition (PMBOK Guide) as:Ī deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. In this article we are going to look at what many project managers and project management professionals refer to as the "foundation" of the project, or at least the foundation of project planning.
0 kommentar(er)
