(WBS) - Work Breakdown Structure - Revision history

LukasBonitz: /* Benefits and limitation of WBS */

2023-05-09T21:57:30Z

Benefits and limitation of WBS

← Older revision		Revision as of 21:57, 9 May 2023
Line 95:		Line 95:
	[[File:Unbenannt3 wbs.PNG\|thumb\|none\|400px\|Figure 4: Illustration of Outline Structure. <ref name="PMI"/>.]]		[[File:Unbenannt3 wbs.PNG\|thumb\|none\|400px\|Figure 4: Illustration of Outline Structure. <ref name="PMI"/>.]]

	== Benefits and ~~limitation~~ of WBS ==		== Benefits and Limitation of WBS ==
	With the help of a WBS project planners can more easily identify the work and the specific tasks that make up the project's overall scope. Furthermore, the WBS can be used as a communication tool, that can give stakeholders an overview of the project at any level of detail. In addition, WBS provides a foundation for other project management tasks. The only disadvantage of the WBS is that it does not show how difficult the tasks are. Along with funding, you won't have access to the materials your team needs to execute. To use a work breakdown structure as efficiently as possible, it is advisable to use other tools in parallel.		With the help of a WBS project planners can more easily identify the work and the specific tasks that make up the project's overall scope. Furthermore, the WBS can be used as a communication tool, that can give stakeholders an overview of the project at any level of detail. In addition, WBS provides a foundation for other project management tasks. The only disadvantage of the WBS is that it does not show how difficult the tasks are. Along with funding, you won't have access to the materials your team needs to execute. To use a work breakdown structure as efficiently as possible, it is advisable to use other tools in parallel.

LukasBonitz: /* Further WBS Rules */

2023-05-09T21:55:32Z

Further WBS Rules

← Older revision		Revision as of 21:55, 9 May 2023
Line 53:		Line 53:
	#A WBS has no limit of levels of decomposition. However, a parent level must always have at least two child components.		#A WBS has no limit of levels of decomposition. However, a parent level must always have at least two child components.
	#The WBS elements do not: <ref name="WBS"/>		#The WBS elements do not: <ref name="WBS"/>
	*contain cost		*contain cost
	*are assigned resources.		*are assigned resources.
	*account for sequences or time		*account for sequences or time
	*show relationships		*show relationships
	*imply importance		*imply importance
	*overlap		*overlap

	== How to Create a Work Breakdown ==		== How to Create a Work Breakdown ==

LukasBonitz: /* Further WBS Rules */

2023-05-09T21:55:12Z

Further WBS Rules

← Older revision		Revision as of 21:55, 9 May 2023
Line 53:		Line 53:
	#A WBS has no limit of levels of decomposition. However, a parent level must always have at least two child components.		#A WBS has no limit of levels of decomposition. However, a parent level must always have at least two child components.
	#The WBS elements do not: <ref name="WBS"/>		#The WBS elements do not: <ref name="WBS"/>
	*contain cost		*contain cost
	*are assigned resources.		*are assigned resources.
	*account for sequences or time		*account for sequences or time
	*show relationships		*show relationships
	*imply importance		*imply importance
	*overlap		*overlap

	== How to Create a Work Breakdown ==		== How to Create a Work Breakdown ==

LukasBonitz: /* Further WBS Rules */

2023-05-09T21:54:01Z

Further WBS Rules

← Older revision		Revision as of 21:54, 9 May 2023
Line 53:		Line 53:
	#A WBS has no limit of levels of decomposition. However, a parent level must always have at least two child components.		#A WBS has no limit of levels of decomposition. However, a parent level must always have at least two child components.
	#The WBS elements do not: <ref name="WBS"/>		#The WBS elements do not: <ref name="WBS"/>
	contain cost		*contain cost
	are assigned resources.		*are assigned resources.
	account for sequences or time		*account for sequences or time
	show relationships		*show relationships
	imply importance		*imply importance
	overlap		*overlap

	== How to Create a Work Breakdown ==		== How to Create a Work Breakdown ==

LukasBonitz: /* 100% Rule */

2023-05-09T21:53:23Z

100% Rule

@@ Line 48: / Line 48: @@
 === 100% Rule ===
 The 100% rule states that the top level of the WBS must cover the entire scope of the project in its entirety. In addition, each decomposition level of the WBS must contain all elements that constitute 100% of the parent available product.<ref name="WBSI"/> <ref name="ABC"/>
 == How to Create a Work Breakdown ==

LukasBonitz: /* 100% Rule */

2023-05-09T21:44:39Z

100% Rule

← Older revision		Revision as of 21:44, 9 May 2023
Line 47:		Line 47:

	=== 100% Rule ===		=== 100% Rule ===
	The 100% rule states that the top level of the WBS must cover the entire scope of the project in its entirety. In addition, each decomposition level of the WBS must contain all elements that constitute 100% of the parent available product.		The 100% rule states that the top level of the WBS must cover the entire scope of the project in its entirety. In addition, each decomposition level of the WBS must contain all elements that constitute 100% of the parent available product.<ref name="WBSI"/> <ref name="ABC"/>

	== How to Create a Work Breakdown ==		== How to Create a Work Breakdown ==

LukasBonitz: /* 100% Rule */

2023-05-09T21:44:04Z

100% Rule

← Older revision		Revision as of 21:44, 9 May 2023
Line 47:		Line 47:

	=== 100% Rule ===		=== 100% Rule ===
	The 100% rule states that each decomposition level in the ~~work breakdown structure~~ must contain all ~~deliverable items~~ that ~~comprise~~ 100% of the parent ~~deliverable~~ product.		The 100% rule states that the top level of the WBS must cover the entire scope of the project in its entirety. In addition, each decomposition level of the WBS must contain all elements that constitute 100% of the parent available product.

	== How to Create a Work Breakdown ==		== How to Create a Work Breakdown ==

LukasBonitz: /* 100% Rule */

2023-05-09T21:40:20Z

100% Rule

← Older revision		Revision as of 21:40, 9 May 2023
Line 47:		Line 47:

	=== 100% Rule ===		=== 100% Rule ===
			The 100% rule states that each decomposition level in the work breakdown structure must contain all deliverable items that comprise 100% of the parent deliverable product.




	== How to Create a Work Breakdown ==		== How to Create a Work Breakdown ==

LukasBonitz: /* WBS in Project Management */

2023-05-09T21:34:30Z

WBS in Project Management

← Older revision		Revision as of 21:34, 9 May 2023
Line 14:		Line 14:
	According to PMI, a WBS is defined as follows: "The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. The WBS organizes and defines the total scope of the project and represents the work specified in the current approved project scope statement".<ref name="PMBOK"/> The WBS is used to explicitly describe the project scope, the deliverables and the outcome of a project. It answers the question of the "what ?" of the project. The processes that lead to the results, the "how ?", as well as the schedule witch determines the exact time of the production of a deliverable, the "when ?", are not answered by using a WBS. <ref name="WBS"/>.		According to PMI, a WBS is defined as follows: "The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. The WBS organizes and defines the total scope of the project and represents the work specified in the current approved project scope statement".<ref name="PMBOK"/> The WBS is used to explicitly describe the project scope, the deliverables and the outcome of a project. It answers the question of the "what ?" of the project. The processes that lead to the results, the "how ?", as well as the schedule witch determines the exact time of the production of a deliverable, the "when ?", are not answered by using a WBS. <ref name="WBS"/>.

	By using a WBS, the consistency and completeness of scope can be verified and duplicates of work or deliverables can be avoided. Furthermore, a WBS functions as a communication mechanism that helps to communicate the scope of work to all stakeholders involved in the project and create a shared understanding. Because project management communication has been proven to be one of the biggest influences on project success, the use of the work breakdown structure is an essential part of any project planning process, regardless of the project type, industry, project deliverables, or project life cycle type. After the creation of a WBS, the defined outcome can be used as a basis for defining further planning processes, such as defining activities, estimating costs and activity resources and identifying risks. Moreover, WBS establishes frameworks for the controlling and execution of the project's work.<ref name="PMI"/> Poorly executed WBS, on the other hand, can also lead to adverse project results including scope creep or unmanageable, frequently changing scope, unclear work assignments, ongoing, repeated project rescheduling and extensions, budget overrun, missed deadlines and unusable new products or delivered features. <ref name="Muk"/>		By using a WBS, the consistency and completeness of scope can be verified and duplicates of work or deliverables can be avoided. Furthermore, a WBS functions as a communication mechanism that helps to communicate the scope of work to all stakeholders involved in the project and create a shared understanding. Because project management communication has been proven to be one of the biggest influences on project success, the use of the work breakdown structure is an essential part of any project planning process, regardless of the project type, industry, project deliverables, or project life cycle type. After the creation of a WBS, the defined outcome can be used as a basis for defining further planning processes, such as defining activities, estimating costs and activity resources and identifying risks. Moreover, WBS establishes frameworks for the controlling and execution of the project's work.<ref name="PMI"/> Poorly executed WBS, on the other hand, can also lead to adverse project results including scope creep or unmanageable, frequently changing scope, unclear work assignments, ongoing, repeated project rescheduling and extensions, budget overrun, missed deadlines and unusable new products or delivered features. <ref name="Muk"/> <ref name="CH12"/>

	== WBS Structure ==		== WBS Structure ==

LukasBonitz: /* Representation of WBS */

2023-05-09T21:31:29Z

Representation of WBS

← Older revision		Revision as of 21:31, 9 May 2023
Line 81:		Line 81:
	==Representation of WBS ==		==Representation of WBS ==

	There is no single or correct way to present WBS. Common representations include the tree structure, outline and tabular shown in the figure below.<ref name="PMI"/>		There is no single or correct way to present WBS. Common representations include the tree structure, outline and tabular shown in the figure below. All three presentation forms describe the exact same WBS. Depending on the needs of the audience or the stakeholders present, the usage ridge of the different presentation forms varies from case to case. <ref name="PMI"/>

	[[File:Unbenannt1 WBS.PNG\|thumb\|none\|400px\|Figure 2: Illustration of Tree Structure. <ref name="PMI"/> .]]		[[File:Unbenannt1 WBS.PNG\|thumb\|none\|400px\|Figure 2: Illustration of Tree Structure. <ref name="PMI"/> .]]