The work breakdown structure in project management - Revision history

Tkokotas: /* The work breakdown structure */

2019-05-13T09:41:15Z

The work breakdown structure

← Older revision		Revision as of 09:41, 13 May 2019
Line 51:		Line 51:
	\|'''Cost'''		\|'''Cost'''
	\|Cost is an essential part when planning a project. The cost within WBS involves budgeting and an integrated earned value management system (EVMS) also known as Earned value management (EVM). EVM is a project management technique for measuring the project performance and progress. EVM has the ability to combine measurements of the project management triangle which includes scope, time and costs. Furthermore, EVM is able to provide accurate forecasts of project performance problems.		\|Cost is an essential part when planning a project. The cost within WBS involves budgeting and an integrated earned value management system (EVMS) also known as Earned value management (EVM). EVM is a project management technique for measuring the project performance and progress. EVM has the ability to combine measurements of the project management triangle which includes scope, time and costs. Furthermore, EVM is able to provide accurate forecasts of project performance problems.
	~~\|[[File:EVM-Status-chart.jpg\|thumb\|caption\|Figure 2: ''An illustration of earned value management''\|250px]]~~
	\|-		\|-
	\|'''Resources'''		\|'''Resources'''

Tkokotas at 00:32, 6 November 2018

2018-11-06T00:32:14Z

← Older revision		Revision as of 00:32, 6 November 2018
Line 1:		Line 1:
	''Developed by Sheren Agbarie''		''Developed by Sheren Agbarie''
	[[Category:Work Breakdown Structure]]		[[Category:Work Breakdown Structure]]


	The work breakdown structure (WBS) were first used by the U.S. Department of Defense for the development of missile systems in the mid- 1960s. WBS was initially developed by the U.S. Department of Defense (DoD) and the National Aeronautics and Space Administration (NASA) for the purpose of planning and controlling large acquisition projects.<ref>Eric S. Norman, Shelly A. Brotherton, Robert T. Fired (2008): Work breakdown structures: The foundation of project Management Excellence page 4.</ref> Today, WBS is a modern management technique, which may determine the success of a project in an organization. The approach of WBS allows the project team to visually see the work that is needed in order to complete a project. It is defined as being a deliverable- oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. Furthermore, WBS can prove pivotal within project management planning processes by partitioning projects into stages, deliverables and work packages. If the management tool is used correctly, it can have a positive impact on other project management processes, such as activity definition, project schedule, risk analysis and response, control tools or project organization. Moreover, the WBS do not only help the project team to scope the work into deliverables but do also look into activities and tasks required to complete a project. WBS is essential since It reduces the number of surprises and furthermore, improves the ability to manage future projects in an organization.		The work breakdown structure (WBS) were first used by the U.S. Department of Defense for the development of missile systems in the mid- 1960s. WBS was initially developed by the U.S. Department of Defense (DoD) and the National Aeronautics and Space Administration (NASA) for the purpose of planning and controlling large acquisition projects.<ref>Eric S. Norman, Shelly A. Brotherton, Robert T. Fired (2008): Work breakdown structures: The foundation of project Management Excellence page 4.</ref> Today, WBS is a modern management technique, which may determine the success of a project in an organization. The approach of WBS allows the project team to visually see the work that is needed in order to complete a project. It is defined as being a deliverable- oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. Furthermore, WBS can prove pivotal within project management planning processes by partitioning projects into stages, deliverables and work packages. If the management tool is used correctly, it can have a positive impact on other project management processes, such as activity definition, project schedule, risk analysis and response, control tools or project organization. Moreover, the WBS do not only help the project team to scope the work into deliverables but do also look into activities and tasks required to complete a project. WBS is essential since It reduces the number of surprises and furthermore, improves the ability to manage future projects in an organization.

Tkokotas at 00:31, 6 November 2018

2018-11-06T00:31:59Z

← Older revision		Revision as of 00:31, 6 November 2018
Line 1:		Line 1:
			''Developed by Sheren Agbarie''
	[[Category:Work Breakdown Structure]]		[[Category:Work Breakdown Structure]]

Tkokotas at 16:43, 23 October 2018

2018-10-23T16:43:07Z

← Older revision		Revision as of 16:43, 23 October 2018
Line 31:		Line 31:
	To get an understanding of the hierarchy of the WBS it is important to understand the main structure of the management tool. When setting up the model it is modeled after four different areas. ''Scope'', ''Time'', ''Cost'' and ''Resources''. After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.		To get an understanding of the hierarchy of the WBS it is important to understand the main structure of the management tool. When setting up the model it is modeled after four different areas. ''Scope'', ''Time'', ''Cost'' and ''Resources''. After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.

	[[Category:~~''The work breakdown structure hierarchy''~~]]		[[Category:Work Breakdown Structure]]

	{\| class="wikitable sortable"		{\| class="wikitable sortable"
Line 61:		Line 61:
	After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.		After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.

	[[Category:~~''The work breakdown structure hierarchy''~~]]		[[Category:Work Breakdown Structure]]

	== The work breakdown structure hierarchy==		== The work breakdown structure hierarchy==
Line 90:		Line 90:
	If the different tasks within the management tool is properly subordinated, most of the WBS will automatically number tasks using the above mentioned points.		If the different tasks within the management tool is properly subordinated, most of the WBS will automatically number tasks using the above mentioned points.

	[[Category:~~''Reflections on the use of WBS''~~]]		[[Category:Work Breakdown Structure]]

	== Reflections on the use of WBS ==		== Reflections on the use of WBS ==
Line 107:		Line 107:
	\|}		\|}

	[[Category:''Work ~~breakdown structure video''~~]]		[[Category:Work Breakdown Structure]]

	== Work breakdown structure video ==		== Work breakdown structure video ==
Line 113:		Line 113:
	{{#ev:youtube\|https://www.youtube.com/watch?v=lHMOQaKrXeg#action=share}}		{{#ev:youtube\|https://www.youtube.com/watch?v=lHMOQaKrXeg#action=share}}

	[[Category:~~''Annotations''~~]]		[[Category:Work Breakdown Structure]]

	== Annotations ==		== Annotations ==

Tkokotas at 16:41, 23 October 2018

2018-10-23T16:41:56Z

← Older revision		Revision as of 16:41, 23 October 2018
Line 3:		Line 3:
	The work breakdown structure (WBS) were first used by the U.S. Department of Defense for the development of missile systems in the mid- 1960s. WBS was initially developed by the U.S. Department of Defense (DoD) and the National Aeronautics and Space Administration (NASA) for the purpose of planning and controlling large acquisition projects.<ref>Eric S. Norman, Shelly A. Brotherton, Robert T. Fired (2008): Work breakdown structures: The foundation of project Management Excellence page 4.</ref> Today, WBS is a modern management technique, which may determine the success of a project in an organization. The approach of WBS allows the project team to visually see the work that is needed in order to complete a project. It is defined as being a deliverable- oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. Furthermore, WBS can prove pivotal within project management planning processes by partitioning projects into stages, deliverables and work packages. If the management tool is used correctly, it can have a positive impact on other project management processes, such as activity definition, project schedule, risk analysis and response, control tools or project organization. Moreover, the WBS do not only help the project team to scope the work into deliverables but do also look into activities and tasks required to complete a project. WBS is essential since It reduces the number of surprises and furthermore, improves the ability to manage future projects in an organization.		The work breakdown structure (WBS) were first used by the U.S. Department of Defense for the development of missile systems in the mid- 1960s. WBS was initially developed by the U.S. Department of Defense (DoD) and the National Aeronautics and Space Administration (NASA) for the purpose of planning and controlling large acquisition projects.<ref>Eric S. Norman, Shelly A. Brotherton, Robert T. Fired (2008): Work breakdown structures: The foundation of project Management Excellence page 4.</ref> Today, WBS is a modern management technique, which may determine the success of a project in an organization. The approach of WBS allows the project team to visually see the work that is needed in order to complete a project. It is defined as being a deliverable- oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. Furthermore, WBS can prove pivotal within project management planning processes by partitioning projects into stages, deliverables and work packages. If the management tool is used correctly, it can have a positive impact on other project management processes, such as activity definition, project schedule, risk analysis and response, control tools or project organization. Moreover, the WBS do not only help the project team to scope the work into deliverables but do also look into activities and tasks required to complete a project. WBS is essential since It reduces the number of surprises and furthermore, improves the ability to manage future projects in an organization.

	[[Category:~~''Why is work breakdown structure important?''~~]]		[[Category:Work Breakdown Structure]]

	== Why is work breakdown structure important?==		== Why is work breakdown structure important?==

Tkokotas at 16:41, 23 October 2018

2018-10-23T16:41:02Z

← Older revision		Revision as of 16:41, 23 October 2018
Line 1:		Line 1:
	[[Category:~~''The work breakdown structure in project management''~~]]		[[Category:Work Breakdown Structure]]

	The work breakdown structure (WBS) were first used by the U.S. Department of Defense for the development of missile systems in the mid- 1960s. WBS was initially developed by the U.S. Department of Defense (DoD) and the National Aeronautics and Space Administration (NASA) for the purpose of planning and controlling large acquisition projects.<ref>Eric S. Norman, Shelly A. Brotherton, Robert T. Fired (2008): Work breakdown structures: The foundation of project Management Excellence page 4.</ref> Today, WBS is a modern management technique, which may determine the success of a project in an organization. The approach of WBS allows the project team to visually see the work that is needed in order to complete a project. It is defined as being a deliverable- oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. Furthermore, WBS can prove pivotal within project management planning processes by partitioning projects into stages, deliverables and work packages. If the management tool is used correctly, it can have a positive impact on other project management processes, such as activity definition, project schedule, risk analysis and response, control tools or project organization. Moreover, the WBS do not only help the project team to scope the work into deliverables but do also look into activities and tasks required to complete a project. WBS is essential since It reduces the number of surprises and furthermore, improves the ability to manage future projects in an organization.		The work breakdown structure (WBS) were first used by the U.S. Department of Defense for the development of missile systems in the mid- 1960s. WBS was initially developed by the U.S. Department of Defense (DoD) and the National Aeronautics and Space Administration (NASA) for the purpose of planning and controlling large acquisition projects.<ref>Eric S. Norman, Shelly A. Brotherton, Robert T. Fired (2008): Work breakdown structures: The foundation of project Management Excellence page 4.</ref> Today, WBS is a modern management technique, which may determine the success of a project in an organization. The approach of WBS allows the project team to visually see the work that is needed in order to complete a project. It is defined as being a deliverable- oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. Furthermore, WBS can prove pivotal within project management planning processes by partitioning projects into stages, deliverables and work packages. If the management tool is used correctly, it can have a positive impact on other project management processes, such as activity definition, project schedule, risk analysis and response, control tools or project organization. Moreover, the WBS do not only help the project team to scope the work into deliverables but do also look into activities and tasks required to complete a project. WBS is essential since It reduces the number of surprises and furthermore, improves the ability to manage future projects in an organization.

S163647 at 23:03, 26 September 2016

2016-09-26T23:03:51Z

← Older revision		Revision as of 23:03, 26 September 2016
Line 49:		Line 49:
	\|'''Cost'''		\|'''Cost'''
	\|Cost is an essential part when planning a project. The cost within WBS involves budgeting and an integrated earned value management system (EVMS) also known as Earned value management (EVM). EVM is a project management technique for measuring the project performance and progress. EVM has the ability to combine measurements of the project management triangle which includes scope, time and costs. Furthermore, EVM is able to provide accurate forecasts of project performance problems.		\|Cost is an essential part when planning a project. The cost within WBS involves budgeting and an integrated earned value management system (EVMS) also known as Earned value management (EVM). EVM is a project management technique for measuring the project performance and progress. EVM has the ability to combine measurements of the project management triangle which includes scope, time and costs. Furthermore, EVM is able to provide accurate forecasts of project performance problems.
	\|[[File:EVM-Status-chart.jpg\|thumb\|caption\|Figure 2:''An illustration of earned value management''\|250px]]		\|[[File:EVM-Status-chart.jpg\|thumb\|caption\|Figure 2: ''An illustration of earned value management''\|250px]]
	\|-		\|-
	\|'''Resources'''		\|'''Resources'''
Line 57:		Line 57:
	'''C''' - Consult		'''C''' - Consult
	'''I''' - Inform		'''I''' - Inform
	\|[[File:Responsible matrix.png\|thumb\|caption\|Figure 3:''An illustration of the responsible matrix''\|250px]]		\|[[File:Responsible matrix.png\|thumb\|caption\|Figure 3: ''An illustration of the responsible matrix''\|250px]]
	\|}		\|}
	After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.		After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.
Line 68:		Line 68:
	WBS should begin in two stages. The first stage is to hold a team meeting. The teams meeting consists of that the member begins planning the first hierarchy level and furthermore, makes the project title. After this has been done the second level of the hierarchy begins. The second level in the WBS hierarchy stage contains descriptive details of all the deliverables that needs to be performed in order to complete the project and determine the timeline of the project. It is important that everything within the scope statement and the project plan is defined before starting the project. When the first and the second level is set, a decomposition and a breakdown of the deliverables of the project and its timeline can begin. The deliverables, which is attached in a tree form to the hierarchy are considered work packages. It is important that the work packages are constantly reviewed and monitored by the project manager and given a timeline upfront. The work packages are completed by different team members, which produce the deliverables which eventually fulfills the different phases in the project. The book The PMBOK® Guide – Fourth Edition suggests that a work package should not be less than eight hours but no more than eight hours.		WBS should begin in two stages. The first stage is to hold a team meeting. The teams meeting consists of that the member begins planning the first hierarchy level and furthermore, makes the project title. After this has been done the second level of the hierarchy begins. The second level in the WBS hierarchy stage contains descriptive details of all the deliverables that needs to be performed in order to complete the project and determine the timeline of the project. It is important that everything within the scope statement and the project plan is defined before starting the project. When the first and the second level is set, a decomposition and a breakdown of the deliverables of the project and its timeline can begin. The deliverables, which is attached in a tree form to the hierarchy are considered work packages. It is important that the work packages are constantly reviewed and monitored by the project manager and given a timeline upfront. The work packages are completed by different team members, which produce the deliverables which eventually fulfills the different phases in the project. The book The PMBOK® Guide – Fourth Edition suggests that a work package should not be less than eight hours but no more than eight hours.

	[[File:WBS Hierarchy.png\|thumb\|center\|caption\|Figure 4:''An illustration of the different level in the WBS hierarchy''\|500px]]		[[File:WBS Hierarchy.png\|thumb\|center\|caption\|Figure 4: ''An illustration of the different level in the WBS hierarchy''\|500px]]

	== Example of the work breakdown structure (WBS) ==		== Example of the work breakdown structure (WBS) ==
Line 79:		Line 79:

	The following figure is an example of a work breakdown structure of a banquet.		The following figure is an example of a work breakdown structure of a banquet.
	[[File:WBS Hirarchy example.png\|thumb\|caption\|Figure 5:''An illustration of a work breakdown structure of a banquet''\|center\|800px]]		[[File:WBS Hirarchy example.png\|thumb\|caption\|Figure 5: ''An illustration of a work breakdown structure of a banquet''\|center\|800px]]

	== WBS numbering ==		== WBS numbering ==

S163647 at 23:01, 26 September 2016

2016-09-26T23:01:27Z

← Older revision		Revision as of 23:01, 26 September 2016
Line 28:		Line 28:

	== The work breakdown structure ==		== The work breakdown structure ==
	[[File:WBS Main Structure.png\|thumb\|caption\|Figure 1:''An illustration of the four different areas in WBS''\|250px]]		[[File:WBS Main Structure.png\|thumb\|caption\|Figure 1: ''An illustration of the four different areas in WBS''\|250px]]
	To get an understanding of the hierarchy of the WBS it is important to understand the main structure of the management tool. When setting up the model it is modeled after four different areas. ''Scope'', ''Time'', ''Cost'' and ''Resources''. After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.		To get an understanding of the hierarchy of the WBS it is important to understand the main structure of the management tool. When setting up the model it is modeled after four different areas. ''Scope'', ''Time'', ''Cost'' and ''Resources''. After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.

S163647 at 22:59, 26 September 2016

2016-09-26T22:59:53Z

← Older revision		Revision as of 22:59, 26 September 2016
Line 28:		Line 28:

	== The work breakdown structure ==		== The work breakdown structure ==
	[[File:WBS Main Structure.png\|thumb\|caption\|''An illustration of the four different areas in WBS''\|250px]]		[[File:WBS Main Structure.png\|thumb\|caption\|Figure 1:''An illustration of the four different areas in WBS''\|250px]]
	To get an understanding of the hierarchy of the WBS it is important to understand the main structure of the management tool. When setting up the model it is modeled after four different areas. ''Scope'', ''Time'', ''Cost'' and ''Resources''. After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.		To get an understanding of the hierarchy of the WBS it is important to understand the main structure of the management tool. When setting up the model it is modeled after four different areas. ''Scope'', ''Time'', ''Cost'' and ''Resources''. After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.

Line 49:		Line 49:
	\|'''Cost'''		\|'''Cost'''
	\|Cost is an essential part when planning a project. The cost within WBS involves budgeting and an integrated earned value management system (EVMS) also known as Earned value management (EVM). EVM is a project management technique for measuring the project performance and progress. EVM has the ability to combine measurements of the project management triangle which includes scope, time and costs. Furthermore, EVM is able to provide accurate forecasts of project performance problems.		\|Cost is an essential part when planning a project. The cost within WBS involves budgeting and an integrated earned value management system (EVMS) also known as Earned value management (EVM). EVM is a project management technique for measuring the project performance and progress. EVM has the ability to combine measurements of the project management triangle which includes scope, time and costs. Furthermore, EVM is able to provide accurate forecasts of project performance problems.
	\|[[File:EVM-Status-chart.jpg\|thumb\|caption\|''An illustration of earned value management''\|250px]]		\|[[File:EVM-Status-chart.jpg\|thumb\|caption\|Figure 2:''An illustration of earned value management''\|250px]]
	\|-		\|-
	\|'''Resources'''		\|'''Resources'''
Line 57:		Line 57:
	'''C''' - Consult		'''C''' - Consult
	'''I''' - Inform		'''I''' - Inform
	\|[[File:Responsible matrix.png\|thumb\|caption\|''An illustration of the responsible matrix''\|250px]]		\|[[File:Responsible matrix.png\|thumb\|caption\|Figure 3:''An illustration of the responsible matrix''\|250px]]
	\|}		\|}
	After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.		After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.
Line 68:		Line 68:
	WBS should begin in two stages. The first stage is to hold a team meeting. The teams meeting consists of that the member begins planning the first hierarchy level and furthermore, makes the project title. After this has been done the second level of the hierarchy begins. The second level in the WBS hierarchy stage contains descriptive details of all the deliverables that needs to be performed in order to complete the project and determine the timeline of the project. It is important that everything within the scope statement and the project plan is defined before starting the project. When the first and the second level is set, a decomposition and a breakdown of the deliverables of the project and its timeline can begin. The deliverables, which is attached in a tree form to the hierarchy are considered work packages. It is important that the work packages are constantly reviewed and monitored by the project manager and given a timeline upfront. The work packages are completed by different team members, which produce the deliverables which eventually fulfills the different phases in the project. The book The PMBOK® Guide – Fourth Edition suggests that a work package should not be less than eight hours but no more than eight hours.		WBS should begin in two stages. The first stage is to hold a team meeting. The teams meeting consists of that the member begins planning the first hierarchy level and furthermore, makes the project title. After this has been done the second level of the hierarchy begins. The second level in the WBS hierarchy stage contains descriptive details of all the deliverables that needs to be performed in order to complete the project and determine the timeline of the project. It is important that everything within the scope statement and the project plan is defined before starting the project. When the first and the second level is set, a decomposition and a breakdown of the deliverables of the project and its timeline can begin. The deliverables, which is attached in a tree form to the hierarchy are considered work packages. It is important that the work packages are constantly reviewed and monitored by the project manager and given a timeline upfront. The work packages are completed by different team members, which produce the deliverables which eventually fulfills the different phases in the project. The book The PMBOK® Guide – Fourth Edition suggests that a work package should not be less than eight hours but no more than eight hours.

	[[File:WBS Hierarchy.png\|thumb\|center\|caption\|''An illustration of the different level in the WBS hierarchy''\|500px]]		[[File:WBS Hierarchy.png\|thumb\|center\|caption\|Figure 4:''An illustration of the different level in the WBS hierarchy''\|500px]]

	== Example of the work breakdown structure (WBS) ==		== Example of the work breakdown structure (WBS) ==
Line 79:		Line 79:

	The following figure is an example of a work breakdown structure of a banquet.		The following figure is an example of a work breakdown structure of a banquet.
	[[File:WBS Hirarchy example.png\|thumb\|caption\|''An illustration of a work breakdown structure of a banquet''\|center\|800px]]		[[File:WBS Hirarchy example.png\|thumb\|caption\|Figure 5:''An illustration of a work breakdown structure of a banquet''\|center\|800px]]

	== WBS numbering ==		== WBS numbering ==

S163647 at 22:54, 26 September 2016

2016-09-26T22:54:56Z

← Older revision		Revision as of 22:54, 26 September 2016
Line 28:		Line 28:

	== The work breakdown structure ==		== The work breakdown structure ==
	[[File:WBS Main Structure.png\|thumb\|caption\|An illustration of the four different areas in WBS\|250px]]		[[File:WBS Main Structure.png\|thumb\|caption\|''An illustration of the four different areas in WBS''\|250px]]
	To get an understanding of the hierarchy of the WBS it is important to understand the main structure of the management tool. When setting up the model it is modeled after four different areas. ''Scope'', ''Time'', ''Cost'' and ''Resources''. After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.		To get an understanding of the hierarchy of the WBS it is important to understand the main structure of the management tool. When setting up the model it is modeled after four different areas. ''Scope'', ''Time'', ''Cost'' and ''Resources''. After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.

Line 49:		Line 49:
	\|'''Cost'''		\|'''Cost'''
	\|Cost is an essential part when planning a project. The cost within WBS involves budgeting and an integrated earned value management system (EVMS) also known as Earned value management (EVM). EVM is a project management technique for measuring the project performance and progress. EVM has the ability to combine measurements of the project management triangle which includes scope, time and costs. Furthermore, EVM is able to provide accurate forecasts of project performance problems.		\|Cost is an essential part when planning a project. The cost within WBS involves budgeting and an integrated earned value management system (EVMS) also known as Earned value management (EVM). EVM is a project management technique for measuring the project performance and progress. EVM has the ability to combine measurements of the project management triangle which includes scope, time and costs. Furthermore, EVM is able to provide accurate forecasts of project performance problems.
	\|[[File:EVM-Status-chart.jpg\|thumb\|caption\|an illustration of earned value management\|250px]]		\|[[File:EVM-Status-chart.jpg\|thumb\|caption\|''An illustration of earned value management''\|250px]]
	\|-		\|-
	\|'''Resources'''		\|'''Resources'''
Line 57:		Line 57:
	'''C''' - Consult		'''C''' - Consult
	'''I''' - Inform		'''I''' - Inform
	\|[[File:Responsible matrix.png\|thumb\|caption\|''an illustration of the responsible matrix''\|250px]]		\|[[File:Responsible matrix.png\|thumb\|caption\|''An illustration of the responsible matrix''\|250px]]
	\|}		\|}
	After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.		After an explanation of the main structure it is now possible to demonstrate how a work breakdown structure is conducted in a project team.