WBS - Work Breakdown Structure - Revision history

Manuelavazquez: /* Annotated bibliography */

2023-05-08T16:51:27Z

Annotated bibliography

← Older revision		Revision as of 16:51, 8 May 2023
Line 179:		Line 179:
	It is a comprehensive guide that can be applied to all types of NASA projects and activities, such as research, development, construction, testing, evaluation, and operations. <ref name="NASA" />		It is a comprehensive guide that can be applied to all types of NASA projects and activities, such as research, development, construction, testing, evaluation, and operations. <ref name="NASA" />

	Although this document was built by NASA and dedicated to its projects, it includes ~~general~~ guidelines ~~and tips about~~ the WBS that can be applied to any project no matter the field.		Although this document was built by NASA and is dedicated to its projects, it includes generic recommendations and guidelines regarding the WBS that can be applied to any project no matter the field.

	== References ==		== References ==
	<references />		<references />

Manuelavazquez: /* Annotated bibliography */

2023-05-08T16:49:31Z

Annotated bibliography

← Older revision		Revision as of 16:49, 8 May 2023
Line 177:		Line 177:
	* “NASA Work Breakdown Structure (WBS) Handbook“, October 2016		* “NASA Work Breakdown Structure (WBS) Handbook“, October 2016
	This document aims to offer program and project teams with essential directions and recommendations on the most effective methods for creating and utilizing a WBS and a WBS dictionary.		This document aims to offer program and project teams with essential directions and recommendations on the most effective methods for creating and utilizing a WBS and a WBS dictionary.
	It is a comprehensive guide that can be applied to all types of NASA projects and activities, such as research, development, construction, testing, evaluation, and operations.		It is a comprehensive guide that can be applied to all types of NASA projects and activities, such as research, development, construction, testing, evaluation, and operations. <ref name="NASA" />
	~~It assists project teams in the development of effective WBS and gives all project components a foundation for common reference~~. <ref name="NASA" />

	Although this document was built by NASA and dedicated to its projects, it includes general guidelines and tips about the WBS that can be applied to any project no matter the field.		Although this document was built by NASA and dedicated to its projects, it includes general guidelines and tips about the WBS that can be applied to any project no matter the field.

Manuelavazquez: /* Annotated bibliography */

2023-05-08T16:49:01Z

Annotated bibliography

← Older revision		Revision as of 16:49, 8 May 2023
Line 178:		Line 178:
	This document aims to offer program and project teams with essential directions and recommendations on the most effective methods for creating and utilizing a WBS and a WBS dictionary.		This document aims to offer program and project teams with essential directions and recommendations on the most effective methods for creating and utilizing a WBS and a WBS dictionary.
	It is a comprehensive guide that can be applied to all types of NASA projects and activities, such as research, development, construction, testing, evaluation, and operations.		It is a comprehensive guide that can be applied to all types of NASA projects and activities, such as research, development, construction, testing, evaluation, and operations.
	It assists project teams in the development of effective WBS and gives all project components a foundation for common reference.		It assists project teams in the development of effective WBS and gives all project components a foundation for common reference. <ref name="NASA" />

	Although this document was built by NASA and dedicated to its projects, it includes general guidelines and tips about the WBS that can be applied to any project no matter the field.		Although this document was built by NASA and dedicated to its projects, it includes general guidelines and tips about the WBS that can be applied to any project no matter the field.

	== References ==		== References ==
	<references />		<references />

Manuelavazquez: /* Annotated bibliography */

2023-05-08T16:47:57Z

Annotated bibliography

← Older revision		Revision as of 16:47, 8 May 2023
Line 176:		Line 176:

	* “NASA Work Breakdown Structure (WBS) Handbook“, October 2016		* “NASA Work Breakdown Structure (WBS) Handbook“, October 2016
	This document aims to offer program and project teams with essential directions and recommendations on the most effective methods for creating and utilizing a WBS and a WBS dictionary ~~for managing project implementation and control~~.		This document aims to offer program and project teams with essential directions and recommendations on the most effective methods for creating and utilizing a WBS and a WBS dictionary.
	It is a comprehensive guide that can be applied to all types of NASA projects and activities, such as research, development, construction, testing, evaluation, and operations.		It is a comprehensive guide that can be applied to all types of NASA projects and activities, such as research, development, construction, testing, evaluation, and operations.
	It assists project teams in the development of effective WBS and gives all project components a foundation for common reference.		It assists project teams in the development of effective WBS and gives all project components a foundation for common reference.

Manuelavazquez: /* Annotated bibliography */

2023-05-08T16:47:22Z

Annotated bibliography

← Older revision		Revision as of 16:47, 8 May 2023
Line 175:		Line 175:
	This document offers direction on work breakdown structures for organizations involved in project or program management. It is suitable for any organization, regardless of its type, size, or sector, as well as for any project or program in terms of complexity, size, or duration. The document includes definitions, concepts, characteristics, benefits, uses, integration, and relationships relevant to WBS. <ref name="ISO"/>		This document offers direction on work breakdown structures for organizations involved in project or program management. It is suitable for any organization, regardless of its type, size, or sector, as well as for any project or program in terms of complexity, size, or duration. The document includes definitions, concepts, characteristics, benefits, uses, integration, and relationships relevant to WBS. <ref name="ISO"/>

	* “NASA Work Breakdown Structure (WBS) Handbook“, ~~January 2010~~		* “NASA Work Breakdown Structure (WBS) Handbook“, October 2016
			This document aims to offer program and project teams with essential directions and recommendations on the most effective methods for creating and utilizing a WBS and a WBS dictionary for managing project implementation and control.
			It is a comprehensive guide that can be applied to all types of NASA projects and activities, such as research, development, construction, testing, evaluation, and operations.
			It assists project teams in the development of effective WBS and gives all project components a foundation for common reference.
			Although this document was built by NASA and dedicated to its projects, it includes general guidelines and tips about the WBS that can be applied to any project no matter the field.

	== References ==		== References ==
	<references />		<references />

Manuelavazquez: /* How to create a WBS */

2023-05-08T16:41:12Z

How to create a WBS

← Older revision		Revision as of 16:41, 8 May 2023
Line 65:		Line 65:
	Even though there is no single "correct way" to prepare a WBS, some generally recommended guidelines can be followed by the project team to ensure that proper WBS characteristics exist for any project. Considering the following general guidelines will assist in creating and implementing the WBS:		Even though there is no single "correct way" to prepare a WBS, some generally recommended guidelines can be followed by the project team to ensure that proper WBS characteristics exist for any project. Considering the following general guidelines will assist in creating and implementing the WBS:

	# The WBS is prepared as early as the project definition will permit <ref name="NASA"> ''NASA Work Breakdown Structure (WBS) Handbook'', ~~January 2010~~, NASA/SP-~~2010~~-3404. Retrieved from: https://ntrs.nasa.gov/citations/20160014629 </ref>.		# The WBS is prepared as early as the project definition will permit <ref name="NASA"> ''NASA Work Breakdown Structure (WBS) Handbook'', October 2016, NASA/SP-2016-3404/REV1. Retrieved from: https://ntrs.nasa.gov/citations/20160014629 </ref>.
	# A preliminary WBS is initially developed early in project formulation to define the top levels of a WBS. These preliminary elements should reflect the entire scope of the project including project definition, development, launch, and operations <ref name="NASA" />.		# A preliminary WBS is initially developed early in project formulation to define the top levels of a WBS. These preliminary elements should reflect the entire scope of the project including project definition, development, launch, and operations <ref name="NASA" />.
	# A brainstorming session should be organized with the various departments involved in the project, inviting all relevant stakeholders. Furthermore, involvement in planning leads to motivation to carry out the plan <ref name="Webster"> Webster, F. M. (1994).''The WBS''. PM Network, 8(12), 40–46.</ref>. All relevant stakeholders need to be involved to ensure that proper planning is done and that all parties agree on the final WBS prior to approval.<ref name="NASA" />.		# A brainstorming session should be organized with the various departments involved in the project, inviting all relevant stakeholders. Furthermore, involvement in planning leads to motivation to carry out the plan <ref name="Webster"> Webster, F. M. (1994).''The WBS''. PM Network, 8(12), 40–46.</ref>. All relevant stakeholders need to be involved to ensure that proper planning is done and that all parties agree on the final WBS prior to approval.<ref name="NASA" />.

Manuelavazquez: /* Annotated bibliography */

2023-05-08T16:39:35Z

Annotated bibliography

← Older revision		Revision as of 16:39, 8 May 2023
Line 174:		Line 174:
	* ISO 21511:2018, "Work breakdown structures for project and programme management"		* ISO 21511:2018, "Work breakdown structures for project and programme management"
	This document offers direction on work breakdown structures for organizations involved in project or program management. It is suitable for any organization, regardless of its type, size, or sector, as well as for any project or program in terms of complexity, size, or duration. The document includes definitions, concepts, characteristics, benefits, uses, integration, and relationships relevant to WBS. <ref name="ISO"/>		This document offers direction on work breakdown structures for organizations involved in project or program management. It is suitable for any organization, regardless of its type, size, or sector, as well as for any project or program in terms of complexity, size, or duration. The document includes definitions, concepts, characteristics, benefits, uses, integration, and relationships relevant to WBS. <ref name="ISO"/>

			* “NASA Work Breakdown Structure (WBS) Handbook“, January 2010

	== References ==		== References ==
	<references />		<references />

Manuelavazquez: /* How to create a WBS */

2023-05-08T16:36:45Z

How to create a WBS

← Older revision		Revision as of 16:36, 8 May 2023
Line 65:		Line 65:
	Even though there is no single "correct way" to prepare a WBS, some generally recommended guidelines can be followed by the project team to ensure that proper WBS characteristics exist for any project. Considering the following general guidelines will assist in creating and implementing the WBS:		Even though there is no single "correct way" to prepare a WBS, some generally recommended guidelines can be followed by the project team to ensure that proper WBS characteristics exist for any project. Considering the following general guidelines will assist in creating and implementing the WBS:

	# The WBS is prepared as early as the project definition will permit <ref name="NASA"> ''NASA Work Breakdown Structure (WBS) Handbook'', January 2010, NASA/SP-2010-3404 </ref>.		# The WBS is prepared as early as the project definition will permit <ref name="NASA"> ''NASA Work Breakdown Structure (WBS) Handbook'', January 2010, NASA/SP-2010-3404. Retrieved from: https://ntrs.nasa.gov/citations/20160014629 </ref>.
	# A preliminary WBS is initially developed early in project formulation to define the top levels of a WBS. These preliminary elements should reflect the entire scope of the project including project definition, development, launch, and operations <ref name="NASA" />.		# A preliminary WBS is initially developed early in project formulation to define the top levels of a WBS. These preliminary elements should reflect the entire scope of the project including project definition, development, launch, and operations <ref name="NASA" />.
	# A brainstorming session should be organized with the various departments involved in the project, inviting all relevant stakeholders. Furthermore, involvement in planning leads to motivation to carry out the plan <ref name="Webster"> Webster, F. M. (1994).''The WBS''. PM Network, 8(12), 40–46.</ref>. All relevant stakeholders need to be involved to ensure that proper planning is done and that all parties agree on the final WBS prior to approval.<ref name="NASA" />.		# A brainstorming session should be organized with the various departments involved in the project, inviting all relevant stakeholders. Furthermore, involvement in planning leads to motivation to carry out the plan <ref name="Webster"> Webster, F. M. (1994).''The WBS''. PM Network, 8(12), 40–46.</ref>. All relevant stakeholders need to be involved to ensure that proper planning is done and that all parties agree on the final WBS prior to approval.<ref name="NASA" />.

Manuelavazquez: /* Hierarchical Structure */

2023-05-08T16:22:54Z

Hierarchical Structure

← Older revision		Revision as of 16:22, 8 May 2023
Line 111:		Line 111:

	===== Hierarchical Structure =====		===== Hierarchical Structure =====
	It is also a very common type, in which each child element is connected to its parent element by a line inside a box. The hierarchical breakdown of the project and its constituent parts into progressively smaller parts is made very clear by this representation.		The hierarchical is also a very common type, in which each child element is connected to its parent element by a line inside a box. The hierarchical breakdown of the project and its constituent parts into progressively smaller parts is made very clear by this representation.

	[[File:ejemplo tree.png\|thumb\|none\|950px\|Figure 2: Illustration of Hierarchical Structure. (Own figure, based on Project Management Institute example <ref name="PMI" />).]]		[[File:ejemplo tree.png\|thumb\|none\|950px\|Figure 2: Illustration of Hierarchical Structure. (Own figure, based on Project Management Institute example <ref name="PMI" />).]]

Manuelavazquez: /* How to evaluate a WBS */

2023-05-08T16:15:07Z

How to evaluate a WBS

← Older revision		Revision as of 16:15, 8 May 2023
Line 76:		Line 76:

	After finishing the WBS, there are some questions that the project team can ask themselves to ensure that all main factors have been considered during the development. For example, a checklist could be followed. Some possible questions are presented below:		After finishing the WBS, there are some questions that the project team can ask themselves to ensure that all main factors have been considered during the development. For example, a checklist could be followed. Some possible questions are presented below:
	# It is advisable to break down the work around deliverables or goals, not tasks. Are they task oriented or deliverable oriented? <ref name="slides"> Oehmen, Josef & Thuesen, Christian, Content of the course 42429/30 Project Management at DTU, ''42430 - Week 2 - Part 3 - Complexity slides''.</ref>		# It is advisable to break down the work around deliverables or goals, not tasks. Are they task-oriented or deliverable-oriented? <ref name="slides"> Oehmen, Josef & Thuesen, Christian, Content of the course 42429/30 Project Management at DTU, ''42430 - Week 2 - Part 3 - Complexity slides''.</ref>
	# Does the overall WBS structure include 100% of the project scope of work? The work content of an element must be the sum of the work content of all its immediately subordinate elements <ref name="Webster" />.		# Does the overall WBS structure include 100% of the project scope of work? The work content of an element must be the sum of the work content of all its immediately subordinate elements <ref name="Webster" />.
	# Is it comprehensive? Are all relevant stakeholders able to understand it?		# Is it comprehensive? Are all relevant stakeholders able to understand it?
	# Does the sub-division of WBS elements reflect accurate, logical, and compatible hierarchy of work scope? <ref name="NASA" />		# Does the sub-division of WBS elements reflect an accurate, logical, and compatible hierarchy of work scope? <ref name="NASA" />
	# Do any elements of the WBS overlap? These should be mutually exclusive, meaning that no elements should overlap in scope definition. If ~~there exists~~ an overlap it could duplicate the team’s efforts and/or create confusion around accountability.		# Do any elements of the WBS overlap? These should be mutually exclusive, meaning that no elements should overlap in scope definition. If an overlap exists, it could duplicate the team’s efforts and/or create confusion around accountability. <ref name="NASA" />
	# Does the WBS Dictionary provide complete and explicit content descriptions? <ref name="NASA" />		# Does the WBS Dictionary provide complete and explicit content descriptions? <ref name="NASA" />
	# Does the WBS sub-divide the project scope of work down to an adequate level of detail to provide for effective resource planning, management insight, and performance measurement?<ref name="NASA" /> It should be accurate but not necessarily precise.		# Does the WBS sub-divide the project scope of work down to an adequate level of detail to provide for effective resource planning, management insight, and performance measurement?<ref name="NASA" /> It should be accurate but not necessarily precise.