Work Breakdown Structure in Project Management

From apppm
(Difference between revisions)
Jump to: navigation, search
(Abstract)
(References)
Line 13: Line 13:
 
==References==
 
==References==
  
*References Cite link: [http://www.mediawiki.org/wiki/Extension:Cite Cite]
+
 
**To create a reference link in the text like this <ref>[http://www.facstaff.bucknell.edu/ttoole/Toole%20PM%20Causal%20Loop%20Diagram.pdf  A project management causal loop diagram, Toole, Michael, 2005.] </ref> write <nowiki><ref>[''link/title''] ''Name of link'' </ref></nowiki>
+
 
<references/>
 
<references/>

Revision as of 14:33, 13 February 2022

Contents

Abstract

Project Management is often a complex process involving Stakeholders, Teams, Development Approaches, Planning, Project Work, Delivery, Measurement, and Uncertainty. As part of Planning and Delivery it is important to define the Scope and Requirements in order to break down the complex tasks into manageable sub-tasks of the whole project (PMBOK; Seventh Edition, 2021, p. 81)[1]. Therefore, in this Wiki article, the Work Breakdown Structure (WBS) will be presented as a Project Management method used to reduce the complexity of a project by delimiting the whole project plan into manageable sub-tasks. This Wiki article will cover application on WBS along with its principles, advantages and limitations.

Historical Applications

Application

Advantages

Limitations

References

  1. Project Management Institute. “A Guide to the Project Management Body of Knowledge (PMBOK)”- Seventh Edition, 2021, p. 81
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox