Project scope statement - Revision history

Tkokotas at 15:37, 16 November 2018

2018-11-16T15:37:11Z

← Older revision		Revision as of 15:37, 16 November 2018
Line 1:		Line 1:
			''Developed by Ína Salome Sturludóttir''


	==Abstract==		==Abstract==
	Defining a project scope statement is an essential part of any project. It is an output of the define scope process and used to identify the main deliverables of a project along with the key milestones, boundaries, constraints, and assumptions. This statement documents also the responsibilities of each member of the project team and procedures for verifications and approves of completed work. Both the project team and all of the stakeholders have to agree with all of the terms suggested in the scope statement before the actual project work begins.<ref name="PMG"> William R. Duncan. (2013). A Guide to The Project Management Body of Knowledge (PMBOK® Guide). 5th ed. Pennsylvania: Project Management Institute.</ref> <sup>(p.123)</sup> Even though the project scope statement is supposed to head the project in the right direction the situation can change as the project progresses. The changed situation has to be assessed on all aspects of the project and necessary changes have to be proposed to the project scope statement and verified. The scope statement needs to be adjusted if the changes are approved.<ref name="R1"> Margaret Rouse. (January 2018). Project scope. [online].Available at: http://searchcio.techtarget.com/definition/project-scope</ref> A well-written scope statement is an important part to achieve a successful project and the six main aspects which a good statement should include are a product scope description, acceptance criteria, deliverables, project exclusion, constraints, and assumptions.<ref name="PMG"/> <sup>(p.123-124)</sup> These aspects will be discussed in more details in the following article, along with general guidelines of how to write a project statement and at last, the limitations of writing a project scope statement will be discussed.		Defining a project scope statement is an essential part of any project. It is an output of the define scope process and used to identify the main deliverables of a project along with the key milestones, boundaries, constraints, and assumptions. This statement documents also the responsibilities of each member of the project team and procedures for verifications and approves of completed work. Both the project team and all of the stakeholders have to agree with all of the terms suggested in the scope statement before the actual project work begins.<ref name="PMG"> William R. Duncan. (2013). A Guide to The Project Management Body of Knowledge (PMBOK® Guide). 5th ed. Pennsylvania: Project Management Institute.</ref> <sup>(p.123)</sup> Even though the project scope statement is supposed to head the project in the right direction the situation can change as the project progresses. The changed situation has to be assessed on all aspects of the project and necessary changes have to be proposed to the project scope statement and verified. The scope statement needs to be adjusted if the changes are approved.<ref name="R1"> Margaret Rouse. (January 2018). Project scope. [online].Available at: http://searchcio.techtarget.com/definition/project-scope</ref> A well-written scope statement is an important part to achieve a successful project and the six main aspects which a good statement should include are a product scope description, acceptance criteria, deliverables, project exclusion, constraints, and assumptions.<ref name="PMG"/> <sup>(p.123-124)</sup> These aspects will be discussed in more details in the following article, along with general guidelines of how to write a project statement and at last, the limitations of writing a project scope statement will be discussed.

Ina: /* Practical Guidelines */

2018-02-28T20:01:48Z

Practical Guidelines

← Older revision		Revision as of 20:01, 28 February 2018
Line 54:		Line 54:
	Writing a project scope statement can sometimes be an overwhelming and time-consuming task, but most important thing when writing a project scope statement is being '''S'''pecific. First, choose a very concise name for the project. Second, write a clear description of the project deliverables and use simple language expression. Be precise when the project will be complete, that it is '''M'''easurable. Beware of if the project is '''A'''chievable, that the project can be accomplished with the existing resources and the right skilled people. Keep in mind or be sensible about what can be achieved or expected in the project process, be '''R'''ealistic. Lastly, know the timeline of the project, in what '''T'''ime has the project to be finished. These criteria are good to take into consideration when the project scope statement is written and they are known guidance in the project management process, their acronym is '''SMART'''.<ref name="SMART"> Duncan Haughey. (2014). A Brief History of SMART Goals. Available at: https://www.projectsmart.co.uk/brief-history-of-smart-goals.php</ref>		Writing a project scope statement can sometimes be an overwhelming and time-consuming task, but most important thing when writing a project scope statement is being '''S'''pecific. First, choose a very concise name for the project. Second, write a clear description of the project deliverables and use simple language expression. Be precise when the project will be complete, that it is '''M'''easurable. Beware of if the project is '''A'''chievable, that the project can be accomplished with the existing resources and the right skilled people. Keep in mind or be sensible about what can be achieved or expected in the project process, be '''R'''ealistic. Lastly, know the timeline of the project, in what '''T'''ime has the project to be finished. These criteria are good to take into consideration when the project scope statement is written and they are known guidance in the project management process, their acronym is '''SMART'''.<ref name="SMART"> Duncan Haughey. (2014). A Brief History of SMART Goals. Available at: https://www.projectsmart.co.uk/brief-history-of-smart-goals.php</ref>

	According to the PMBOK® Guide, the definition of a good project scope statement, which is capable to deliver a successful project, need to consist of six main aspects. These aspects are the product scope description, the acceptance criteria, the deliverables, the project exclusion, the constraints, and the assumptions. <ref name="PMG"/> <sup>(p.123 - 124)</sup> By implementing these aspects into the project scope statement are everyone who participates in the project process aware of what falls within the project scope. These aspects also structure the baseline for determining how to manage the rest of activities in the project process.<ref name="PSS"> SkillBrief. (2016). Project Scope Statement. Available at: https://library.skillport.com/courseware/Content/cca/proj_21_a01_bs_enus/output/html/sb/sbproj_21_a01_bs_enus018022.html </ref> The six main aspects are explained here below in details.		According to the PMBOK® Guide, the definition of a good project scope statement, which is capable to deliver a successful project, need to consist of six main aspects. These aspects are the product scope description, the acceptance criteria, the deliverables, the project exclusion, the constraints, and the assumptions.<ref name="PMG"/> <sup>(p.123 - 124)</sup> By implementing these aspects into the project scope statement are everyone who participates in the project process aware of what falls within the project scope. These aspects also structure the baseline for determining how to manage the rest of activities in the project process.<ref name="PSS"> SkillBrief. (2016). Project Scope Statement. Available at: https://library.skillport.com/courseware/Content/cca/proj_21_a01_bs_enus/output/html/sb/sbproj_21_a01_bs_enus018022.html </ref> The six main aspects are explained here below in details.

Ina: /* Practical Guidelines */

2018-02-28T20:00:14Z

Practical Guidelines

← Older revision		Revision as of 20:00, 28 February 2018
Line 50:		Line 50:
	The project scope statement can be developed into different forms of template depending on the characteristics of the project executed and the distinguishing features of the organization. The scale and the complexity of the project may be different, but the more accurate the statement will be the better clarity it will provide about what the project will deliver.<ref name="AW"> Adrienne Watt. (2014). Project Management. B.C. Open Textbook Project.</ref> The person who is responsible or in charge of writing the project scope statement is the project manager. His or her primary task is to gather the requirements, prepare the list of deliverables and formulate the constraints and assumptions. The project team members participate in those tasks but they are usually not part of approving the project scope statement. Other important participants in developing and creating the project scope statement are the clients or the project sponsor, the stakeholders and the suppliers, their input can have a significant influence on its creation. The project scope statement is considered to be an official agreement, both among the stakeholders and the project team, and all of the terms in it needs to be accepted by the key players before the real project begins. A well-written project scope statement should include a clear identification of the project's deliverables, the work necessary to successfully deliver them and also the work that is not necessary. It should as well include a description of the product or service, the key milestones, the constraints and the assumptions of the project.		The project scope statement can be developed into different forms of template depending on the characteristics of the project executed and the distinguishing features of the organization. The scale and the complexity of the project may be different, but the more accurate the statement will be the better clarity it will provide about what the project will deliver.<ref name="AW"> Adrienne Watt. (2014). Project Management. B.C. Open Textbook Project.</ref> The person who is responsible or in charge of writing the project scope statement is the project manager. His or her primary task is to gather the requirements, prepare the list of deliverables and formulate the constraints and assumptions. The project team members participate in those tasks but they are usually not part of approving the project scope statement. Other important participants in developing and creating the project scope statement are the clients or the project sponsor, the stakeholders and the suppliers, their input can have a significant influence on its creation. The project scope statement is considered to be an official agreement, both among the stakeholders and the project team, and all of the terms in it needs to be accepted by the key players before the real project begins. A well-written project scope statement should include a clear identification of the project's deliverables, the work necessary to successfully deliver them and also the work that is not necessary. It should as well include a description of the product or service, the key milestones, the constraints and the assumptions of the project.
	The project scope statement is used as a guide throughout the project process for the project team where it sets a baseline for the project scope. The scope baseline is used to evaluate all the change requests, which is an effective way to control a scope creep.		The project scope statement is used as a guide throughout the project process for the project team where it sets a baseline for the project scope. The scope baseline is used to evaluate all the change requests, which is an effective way to control a scope creep.
	In addition to being a useful guide and setting the baseline to evaluate changes, the project scope statement is helpful to make a common understanding of the project among the stakeholders. By setting appropriated expectations along with the stakeholders, no confusion between the project team and the stakeholders can appear. It can also represent a communication tool when the project needs to be presented to the higher set of managers or other departments.		In addition to being a useful guide and setting the baseline to evaluate changes, the project scope statement is helpful to make a common understanding of the project among the stakeholders. By setting appropriated expectations along with the stakeholders, no confusion between the project team and the stakeholders can appear. It can also represent a communication tool when the project needs to be presented to the higher set of managers or other departments.<ref name="R10"> Burek, P. (2006). Developing a complete project scope statement in 2 days. Paper presented at PMI® Global Congress 2006—North America, Seattle, WA. Newtown Square, PA: Project Management Institute. https://www.pmi.org/learning/library/project-scope-statement-skills-tools-7981</ref> <ref name="PMG"/>
	<ref name="R10"> Burek, P. (2006). Developing a complete project scope statement in 2 days. Paper presented at PMI® Global Congress 2006—North America, Seattle, WA. Newtown Square, PA: Project Management Institute. https://www.pmi.org/learning/library/project-scope-statement-skills-tools-7981</ref> <ref name="PMG"/>

	Writing a project scope statement can sometimes be an overwhelming and time-consuming task, but most important thing when writing a project scope statement is being '''S'''pecific. First, choose a very concise name for the project. Second, write a clear description of the project deliverables and use simple language expression. Be precise when the project will be complete, that it is '''M'''easurable. Beware of if the project is '''A'''chievable, that the project can be accomplished with the existing resources and the right skilled people. Keep in mind or be sensible about what can be achieved or expected in the project process, be '''R'''ealistic. Lastly, know the timeline of the project, in what '''T'''ime has the project to be finished. These criteria are good to take into consideration when the project scope statement is written and they are known guidance in the project management process, their acronym is '''SMART'''.<ref name="SMART"> Duncan Haughey. (2014). A Brief History of SMART Goals. Available at: https://www.projectsmart.co.uk/brief-history-of-smart-goals.php</ref>		Writing a project scope statement can sometimes be an overwhelming and time-consuming task, but most important thing when writing a project scope statement is being '''S'''pecific. First, choose a very concise name for the project. Second, write a clear description of the project deliverables and use simple language expression. Be precise when the project will be complete, that it is '''M'''easurable. Beware of if the project is '''A'''chievable, that the project can be accomplished with the existing resources and the right skilled people. Keep in mind or be sensible about what can be achieved or expected in the project process, be '''R'''ealistic. Lastly, know the timeline of the project, in what '''T'''ime has the project to be finished. These criteria are good to take into consideration when the project scope statement is written and they are known guidance in the project management process, their acronym is '''SMART'''.<ref name="SMART"> Duncan Haughey. (2014). A Brief History of SMART Goals. Available at: https://www.projectsmart.co.uk/brief-history-of-smart-goals.php</ref>

Ina: /* Abstract */

2018-02-28T19:59:32Z

Abstract

← Older revision		Revision as of 19:59, 28 February 2018
Line 1:		Line 1:
	==Abstract==		==Abstract==
	Defining a project scope statement is an essential part of any project. It is an output of the define scope process and used to identify the main deliverables of a project along with the key milestones, boundaries, constraints, and assumptions. This statement documents also the responsibilities of each member of the project team and procedures for verifications and approves of completed work. Both the project team and all of the stakeholders have to agree with all of the terms suggested in the scope statement before the actual project work begins. <ref name="PMG"> William R. Duncan. (2013). A Guide to The Project Management Body of Knowledge (PMBOK® Guide). 5th ed. Pennsylvania: Project Management Institute.</ref> <sup>(p.123)</sup> Even though the project scope statement is supposed to head the project in the right direction the situation can change as the project progresses. The changed situation has to be assessed on all aspects of the project and necessary changes have to be proposed to the project scope statement and verified. The scope statement needs to be adjusted if the changes are approved.<ref name="R1"> Margaret Rouse. (January 2018). Project scope. [online].Available at: http://searchcio.techtarget.com/definition/project-scope</ref> A well-written scope statement is an important part to achieve a successful project and the six main aspects which a good statement should include are a product scope description, acceptance criteria, deliverables, project exclusion, constraints, and assumptions.<ref name="PMG"/> <sup>(p.123-124)</sup> These aspects will be discussed in more details in the following article, along with general guidelines of how to write a project statement and at last, the limitations of writing a project scope statement will be discussed.		Defining a project scope statement is an essential part of any project. It is an output of the define scope process and used to identify the main deliverables of a project along with the key milestones, boundaries, constraints, and assumptions. This statement documents also the responsibilities of each member of the project team and procedures for verifications and approves of completed work. Both the project team and all of the stakeholders have to agree with all of the terms suggested in the scope statement before the actual project work begins.<ref name="PMG"> William R. Duncan. (2013). A Guide to The Project Management Body of Knowledge (PMBOK® Guide). 5th ed. Pennsylvania: Project Management Institute.</ref> <sup>(p.123)</sup> Even though the project scope statement is supposed to head the project in the right direction the situation can change as the project progresses. The changed situation has to be assessed on all aspects of the project and necessary changes have to be proposed to the project scope statement and verified. The scope statement needs to be adjusted if the changes are approved.<ref name="R1"> Margaret Rouse. (January 2018). Project scope. [online].Available at: http://searchcio.techtarget.com/definition/project-scope</ref> A well-written scope statement is an important part to achieve a successful project and the six main aspects which a good statement should include are a product scope description, acceptance criteria, deliverables, project exclusion, constraints, and assumptions.<ref name="PMG"/> <sup>(p.123-124)</sup> These aspects will be discussed in more details in the following article, along with general guidelines of how to write a project statement and at last, the limitations of writing a project scope statement will be discussed.

	==Introduction==		==Introduction==

Ina: /* Limitations */

2018-02-28T19:58:50Z

Limitations

← Older revision		Revision as of 19:58, 28 February 2018
Line 75:		Line 75:
	== Limitations ==		== Limitations ==

	The method described above about how to write a good project scope statement may look like a simple and easy way to follow. However, in ~~the~~ real life, the project scope statement can be quite complicated to write. Nobody can predict the future, so defining the project scope and document all of the aspect of the project scope statement can be a difficult task. The main limitation though of writing a project scope statement is agreeing on what should be included in it. The persons who are involved in writing the project scope statement can have different opinions on many things and ~~a disagreement~~ about many aspects of the project. This can have a great impact on how to decide what should be included in the project scope statement and can delay the whole process. But with clear communication and a good project ~~managment~~ skills, everyone should be able to work together and come to a conclusion about what should be included in the project scope statement and what ~~not~~. Good teamwork is also essential in developing and writing the project scope statement to deliver an efficient work and project scope statement.		The method described above about how to write a good project scope statement may look like a simple and easy way to follow. However, in real life, the project scope statement can be quite complicated to write. Nobody can predict the future, so defining the project scope and document all of the aspect of the project scope statement can be a difficult task. The main limitation though of writing a project scope statement is agreeing on what should be included in it. The persons who are involved in writing the project scope statement can have different opinions on many things and have disagreements about many aspects of the project. This can have a great impact on how to decide what should be included in the project scope statement and can delay the whole process. But with clear communication and a good project management skills, everyone should be able to work together and come to a conclusion about what should be included in the project scope statement and what should be avoided. Good teamwork is also essential in developing and writing the project scope statement to deliver an efficient work and project scope statement.

	==Reference==		==Reference==

Ina: /* Practical Guidelines */

2018-02-28T19:54:48Z

Practical Guidelines

← Older revision		Revision as of 19:54, 28 February 2018
Line 49:		Line 49:

	The project scope statement can be developed into different forms of template depending on the characteristics of the project executed and the distinguishing features of the organization. The scale and the complexity of the project may be different, but the more accurate the statement will be the better clarity it will provide about what the project will deliver.<ref name="AW"> Adrienne Watt. (2014). Project Management. B.C. Open Textbook Project.</ref> The person who is responsible or in charge of writing the project scope statement is the project manager. His or her primary task is to gather the requirements, prepare the list of deliverables and formulate the constraints and assumptions. The project team members participate in those tasks but they are usually not part of approving the project scope statement. Other important participants in developing and creating the project scope statement are the clients or the project sponsor, the stakeholders and the suppliers, their input can have a significant influence on its creation. The project scope statement is considered to be an official agreement, both among the stakeholders and the project team, and all of the terms in it needs to be accepted by the key players before the real project begins. A well-written project scope statement should include a clear identification of the project's deliverables, the work necessary to successfully deliver them and also the work that is not necessary. It should as well include a description of the product or service, the key milestones, the constraints and the assumptions of the project.		The project scope statement can be developed into different forms of template depending on the characteristics of the project executed and the distinguishing features of the organization. The scale and the complexity of the project may be different, but the more accurate the statement will be the better clarity it will provide about what the project will deliver.<ref name="AW"> Adrienne Watt. (2014). Project Management. B.C. Open Textbook Project.</ref> The person who is responsible or in charge of writing the project scope statement is the project manager. His or her primary task is to gather the requirements, prepare the list of deliverables and formulate the constraints and assumptions. The project team members participate in those tasks but they are usually not part of approving the project scope statement. Other important participants in developing and creating the project scope statement are the clients or the project sponsor, the stakeholders and the suppliers, their input can have a significant influence on its creation. The project scope statement is considered to be an official agreement, both among the stakeholders and the project team, and all of the terms in it needs to be accepted by the key players before the real project begins. A well-written project scope statement should include a clear identification of the project's deliverables, the work necessary to successfully deliver them and also the work that is not necessary. It should as well include a description of the product or service, the key milestones, the constraints and the assumptions of the project.
	The project scope statement is used as a guide throughout the project process for the project team ~~and~~ it sets a baseline for the project scope. The scope baseline is used to evaluate all the change requests, which is an effective way to control scope creep.		The project scope statement is used as a guide throughout the project process for the project team where it sets a baseline for the project scope. The scope baseline is used to evaluate all the change requests, which is an effective way to control a scope creep.
	In addition to being a useful guide and setting the baseline to evaluate changes, the project scope statement is helpful to make a common understanding of the project among the stakeholders~~, by~~ setting appropriated expectations along with the stakeholders, so no confusion between the project team and the stakeholders can appear. It can also represent a communication tool when the project needs to be presented to the higher set of managers or other departments.		In addition to being a useful guide and setting the baseline to evaluate changes, the project scope statement is helpful to make a common understanding of the project among the stakeholders. By setting appropriated expectations along with the stakeholders, no confusion between the project team and the stakeholders can appear. It can also represent a communication tool when the project needs to be presented to the higher set of managers or other departments.
	<ref name="R10"> Burek, P. (2006). Developing a complete project scope statement in 2 days. Paper presented at PMI® Global Congress 2006—North America, Seattle, WA. Newtown Square, PA: Project Management Institute. https://www.pmi.org/learning/library/project-scope-statement-skills-tools-7981</ref> <ref name="PMG"/>		<ref name="R10"> Burek, P. (2006). Developing a complete project scope statement in 2 days. Paper presented at PMI® Global Congress 2006—North America, Seattle, WA. Newtown Square, PA: Project Management Institute. https://www.pmi.org/learning/library/project-scope-statement-skills-tools-7981</ref> <ref name="PMG"/>

	Writing a project scope statement can sometimes be an overwhelming and time-consuming task, but most important thing when writing a project scope statement is being '''S'''pecific. First, ~~chose~~ a very concise name for the project. Second, write a clear description of the project deliverables and use simple language expression. Be precise when the project will be complete, that it is '''M'''easurable. Beware of if the project is '''A'''chievable, that the project can be accomplished with the existing resources and the right skilled people. Keep in mind or be sensible about what can be achieved or expected in the project process, be '''R'''ealistic. Lastly, know the timeline of the project, in what '''T'''ime has the project to be finished. These criteria are good to take into consideration when the project scope statement is written and they are known guidance in the project management process, their acronym is '''SMART'''.<ref name="SMART"> Duncan Haughey. (2014). A Brief History of SMART Goals. Available at: https://www.projectsmart.co.uk/brief-history-of-smart-goals.php</ref>		Writing a project scope statement can sometimes be an overwhelming and time-consuming task, but most important thing when writing a project scope statement is being '''S'''pecific. First, choose a very concise name for the project. Second, write a clear description of the project deliverables and use simple language expression. Be precise when the project will be complete, that it is '''M'''easurable. Beware of if the project is '''A'''chievable, that the project can be accomplished with the existing resources and the right skilled people. Keep in mind or be sensible about what can be achieved or expected in the project process, be '''R'''ealistic. Lastly, know the timeline of the project, in what '''T'''ime has the project to be finished. These criteria are good to take into consideration when the project scope statement is written and they are known guidance in the project management process, their acronym is '''SMART'''.<ref name="SMART"> Duncan Haughey. (2014). A Brief History of SMART Goals. Available at: https://www.projectsmart.co.uk/brief-history-of-smart-goals.php</ref>

	According to the PMBOK® Guide, the definition of a good project scope statement, which is capable to deliver a successful project, need to consist of six main aspects. These aspects are the product scope description, the acceptance criteria, the deliverables, the project exclusion, the constraints, and the assumptions. <ref name="PMG"/> <sup>(p.123 - 124)</sup> By implementing these aspects into the project scope statement are everyone who participates in the project process aware of what falls within the project scope. These aspects also structure the baseline for determining how to manage the rest of activities in the project process.<ref name="PSS"> SkillBrief. (2016). Project Scope Statement. Available at: https://library.skillport.com/courseware/Content/cca/proj_21_a01_bs_enus/output/html/sb/sbproj_21_a01_bs_enus018022.html </ref> The six main aspects are explained here below in details.		According to the PMBOK® Guide, the definition of a good project scope statement, which is capable to deliver a successful project, need to consist of six main aspects. These aspects are the product scope description, the acceptance criteria, the deliverables, the project exclusion, the constraints, and the assumptions. <ref name="PMG"/> <sup>(p.123 - 124)</sup> By implementing these aspects into the project scope statement are everyone who participates in the project process aware of what falls within the project scope. These aspects also structure the baseline for determining how to manage the rest of activities in the project process.<ref name="PSS"> SkillBrief. (2016). Project Scope Statement. Available at: https://library.skillport.com/courseware/Content/cca/proj_21_a01_bs_enus/output/html/sb/sbproj_21_a01_bs_enus018022.html </ref> The six main aspects are explained here below in details.
Line 60:		Line 60:
	*''' Product scope description''' - Identifies all the characteristics of the outcome of the project, the product or the service. It is a detailed description of the project scope elaborated from the project charter and the requirements documentation.<ref name="PMG"/> <sup>(p.123)</sup>		*''' Product scope description''' - Identifies all the characteristics of the outcome of the project, the product or the service. It is a detailed description of the project scope elaborated from the project charter and the requirements documentation.<ref name="PMG"/> <sup>(p.123)</sup>

	*'''Acceptance criteria''' - Requirements that need to be met before the project deliverables are accepted. They are decided together by the project team and the key stakeholders and are applied to verify the scope, to evaluate deliverables and to confirm completion. It is crucial to have accurate acceptance criteria in order that ~~everyone will agree that~~ the requirements ~~have been met~~.<ref name="PSS"/>		*'''Acceptance criteria''' - Requirements that need to be met before the project deliverables are accepted. They are decided together by the project team and the key stakeholders and are applied to verify the scope, to evaluate deliverables and to confirm completion. It is crucial to have accurate acceptance criteria in order for key players agreeing on that deliverables has met the requirements.<ref name="PSS"/>

	*'''Deliverable''' - A unique and verifiable product or service which is a small part of the overall project scope. The deliverables need to be listed in the project scope statement and this list will make it clear to the stakeholders what can be expected, throughout the project and at the end of it.<ref name="PSS"/>		*'''Deliverable''' - A unique and verifiable product or service which is a small part of the overall project scope. The deliverables need to be listed in the project scope statement and this list will make it clear to the stakeholders what can be expected, throughout the project and at the end of it.<ref name="PSS"/>

Ina: /* Define Scope */

2018-02-28T19:36:54Z

Define Scope

← Older revision		Revision as of 19:36, 28 February 2018
Line 24:		Line 24:
	The following aspects are the inputs to the define scope process, as they appear in the PMBOK® Guide:		The following aspects are the inputs to the define scope process, as they appear in the PMBOK® Guide:
	<ol>		<ol>
	<li>'''Scope management plan''' - Establishes the activities for defining, developing, monitoring, controlling and verifying the scope of the project. These activities include, for example, preparing an accurate project scope statement, organize how the work ~~brake~~ structure (WBS) will be created and then accepted, and controlling how the change requests to the project scope statement will be managed.<ref name="PMG"/> <sup>(p.109)</sup>		<li>'''Scope management plan''' - Establishes the activities for defining, developing, monitoring, controlling and verifying the scope of the project. These activities include, for example, preparing an accurate project scope statement, organize how the work breakdown structure (WBS) will be created and then accepted, and controlling how the change requests to the project scope statement will be managed.<ref name="PMG"/> <sup>(p.109)</sup>
	<li>'''Project charter''' - Provides formal authorization of the project, describes the characteristics of the project and outlines the project objectives. It is a framework for the project and connects the project manager, the project team and the key stakeholders together at the beginning.<ref name="PMG"/> <sup>(p.71)</sup>		<li>'''Project charter''' - Provides formal authorization of the project, describes the characteristics of the project and outlines the project objectives. It is a framework for the project and connects the project manager, the project team and the key stakeholders together at the beginning.<ref name="PMG"/> <sup>(p.71)</sup>
	<li>'''Requirements documentation''' - This document provides all of the requirements needed to produce the final result in the project and is used to select the main requirements that will be included in the project scope statement. These requirements need to be measurable, traceable, consistent and acceptable to the stakeholders.<ref name="AW"/> <ref name="PMG"/> <sup>(p.117)</sup>		<li>'''Requirements documentation''' - This document provides all of the requirements needed to produce the final result in the project and is used to select the main requirements that will be included in the project scope statement. These requirements need to be measurable, traceable, consistent and acceptable to the stakeholders.<ref name="AW"/> <ref name="PMG"/> <sup>(p.117)</sup>

Ina: /* Project Scope Management */

2018-02-28T19:36:04Z

Project Scope Management

← Older revision		Revision as of 19:36, 28 February 2018
Line 10:		Line 10:
	As outlined in the abstract, the project scope statement is an output of the defined scope process, which is a part of the project scope management process. The project scope management process refers to the set of processes required to ensure that a project includes all the necessary work, and just the amount of work necessary, to successfully complete a project. It is primarily concerned with defining and controlling what is or what is not a part of the project. Therefore the project scope can be defined as the work that must be done to deliver a product with the specified features and functions, according to the PMBOK® Guide.<ref name="PMG"/> <sup>(p.51)</sup> In Figure 1 the six major processes of the project scope management can be seen and their tasks description.		As outlined in the abstract, the project scope statement is an output of the defined scope process, which is a part of the project scope management process. The project scope management process refers to the set of processes required to ensure that a project includes all the necessary work, and just the amount of work necessary, to successfully complete a project. It is primarily concerned with defining and controlling what is or what is not a part of the project. Therefore the project scope can be defined as the work that must be done to deliver a product with the specified features and functions, according to the PMBOK® Guide.<ref name="PMG"/> <sup>(p.51)</sup> In Figure 1 the six major processes of the project scope management can be seen and their tasks description.

	Each of these six processes interacts with each other and each ~~process usually affects the next process which comes after the~~ other. The first process in the project scope management is the planned scope management process. This process formally authorizes a new project and creates the scope management plan that records how the scope of the project will be managed. The planned scope management process influences the defined scope process, which develops the project scope statement, by linking the output of it to the input of the define scope process. Between these processes is an important process which is referred to as collecting requirements process. The collecting requirements process determines, documents and manages the project requirements that reflect on stakeholders needs to meet project objectives. These requirements selected to be part of the scope baseline are generally decided by the project governance, the project sponsor, the project management team, the project's customer and inputs from different stakeholders, who are considered to be important.<ref name="PMG"/>		Each of these six processes interacts with each other and they usually affect each other in a sequentially way. The first process in the project scope management is the planned scope management process. This process formally authorizes a new project and creates the scope management plan that records how the scope of the project will be managed. The planned scope management process influences the defined scope process, which develops the project scope statement, by linking the output of it to the input of the define scope process. Between these processes is an important process which is referred to as collecting requirements process. The collecting requirements process determines, documents and manages the project requirements that reflect on stakeholders needs to meet project objectives. These requirements selected to be part of the scope baseline are generally decided by the project governance, the project sponsor, the project management team, the project's customer and inputs from different stakeholders, who are considered to be important.<ref name="PMG"/>

	The identification process of who the project stakeholders are is an important early step in the scope planning. Project ~~stakeholder~~ can consist of ~~persons~~ or organizations that are actively involved in the project or if their interests may be affected by the project. These stakeholders can be, for instance, sponsors, customers, suppliers, and shareholders.<ref name="ISO">Danish Standards Foundation. (2012). International Standard ISO 21500 - Guidance on project management. København: Danish Standards Foundation.</ref> <sup>(p.6-7)</sup> It is important for the project manager of a project to set proper expectations with their stakeholders at the beginning, to ensure that no misunderstandings can ~~appear~~ later on. These expectations can be about how the requirements or the scope of the project is managed, controlled and verified and these expectations are one of the elements in the project scope statement that needs to be well defined.<ref name="PMG"/> The documentation of the requirements will be discussed further in the next section of the define scope process where it is an input and an essential element of the involvement of establishing the project scope statement.		The identification process of who the project stakeholders are is an important early step in the scope planning. Project stakeholders can consist of individuals or organizations that are actively involved in the project or if their interests may be affected by the project. These stakeholders can be, for instance, sponsors, customers, suppliers, and shareholders.<ref name="ISO">Danish Standards Foundation. (2012). International Standard ISO 21500 - Guidance on project management. København: Danish Standards Foundation.</ref> <sup>(p.6-7)</sup> It is important for the project manager of a project to set proper expectations with their stakeholders at the beginning, to ensure that no misunderstandings can occur later on. These expectations can be about how the requirements or the scope of the project is managed, controlled and verified and these expectations are one of the elements in the project scope statement that needs to be well defined.<ref name="PMG"/> The documentation of the requirements will be discussed further in the next section of the define scope process where it is an input and an essential element of the involvement of establishing the project scope statement.

	====Define Scope====		====Define Scope====

Ina: /* Abstract */

2018-02-28T19:25:39Z

Abstract

← Older revision		Revision as of 19:25, 28 February 2018
Line 1:		Line 1:
	==Abstract==		==Abstract==
	Defining a project scope statement is an essential part of any project. It is an output of the define scope process and used to identify the main deliverables of a project along with the key milestones, ~~the~~ boundaries, constraints, and assumptions. This statement documents also the responsibilities of each member of the project team and procedures for verifications and approves of completed work. Both the project team and all of the stakeholders have to agree with all of the terms suggested in the scope statement before the actual project work begins. <ref name="PMG"> William R. Duncan. (2013). A Guide to The Project Management Body of Knowledge (PMBOK® Guide). 5th ed. Pennsylvania: Project Management Institute.</ref> <sup>(p.123)</sup> Even though the project scope statement is supposed to head the project in the right direction the situation can change as the project progresses. The changed situation has to be assessed on all aspects of the project and necessary changes have to be proposed to the project scope statement. The scope statement needs to be adjusted if the changes are approved.<ref name="R1"> Margaret Rouse. (January, 2018). Project scope. [online].Available at: http://searchcio.techtarget.com/definition/project-scope</ref> A well-written scope statement is an important part to achieve a successful project and the six main aspects which a good statement should include are a product scope description, acceptance criteria, deliverables, project exclusion, constraints, and assumptions.<ref name="PMG"/> <sup>(p.123-124)</sup> These aspects will be discussed in more details in the following article, along with general guidelines of how to write a project statement and at last, the limitations of writing a project scope statement will be discussed.		Defining a project scope statement is an essential part of any project. It is an output of the define scope process and used to identify the main deliverables of a project along with the key milestones, boundaries, constraints, and assumptions. This statement documents also the responsibilities of each member of the project team and procedures for verifications and approves of completed work. Both the project team and all of the stakeholders have to agree with all of the terms suggested in the scope statement before the actual project work begins. <ref name="PMG"> William R. Duncan. (2013). A Guide to The Project Management Body of Knowledge (PMBOK® Guide). 5th ed. Pennsylvania: Project Management Institute.</ref> <sup>(p.123)</sup> Even though the project scope statement is supposed to head the project in the right direction the situation can change as the project progresses. The changed situation has to be assessed on all aspects of the project and necessary changes have to be proposed to the project scope statement and verified. The scope statement needs to be adjusted if the changes are approved.<ref name="R1"> Margaret Rouse. (January 2018). Project scope. [online].Available at: http://searchcio.techtarget.com/definition/project-scope</ref> A well-written scope statement is an important part to achieve a successful project and the six main aspects which a good statement should include are a product scope description, acceptance criteria, deliverables, project exclusion, constraints, and assumptions.<ref name="PMG"/> <sup>(p.123-124)</sup> These aspects will be discussed in more details in the following article, along with general guidelines of how to write a project statement and at last, the limitations of writing a project scope statement will be discussed.

	==Introduction==		==Introduction==

Ina: /* Introduction */

2018-02-26T21:50:09Z

Introduction

← Older revision		Revision as of 21:50, 26 February 2018
Line 12:		Line 12:
	Each of these six processes interacts with each other and each process usually affects the next process which comes after the other. The first process in the project scope management is the planned scope management process. This process formally authorizes a new project and creates the scope management plan that records how the scope of the project will be managed. The planned scope management process influences the defined scope process, which develops the project scope statement, by linking the output of it to the input of the define scope process. Between these processes is an important process which is referred to as collecting requirements process. The collecting requirements process determines, documents and manages the project requirements that reflect on stakeholders needs to meet project objectives. These requirements selected to be part of the scope baseline are generally decided by the project governance, the project sponsor, the project management team, the project's customer and inputs from different stakeholders, who are considered to be important.<ref name="PMG"/>		Each of these six processes interacts with each other and each process usually affects the next process which comes after the other. The first process in the project scope management is the planned scope management process. This process formally authorizes a new project and creates the scope management plan that records how the scope of the project will be managed. The planned scope management process influences the defined scope process, which develops the project scope statement, by linking the output of it to the input of the define scope process. Between these processes is an important process which is referred to as collecting requirements process. The collecting requirements process determines, documents and manages the project requirements that reflect on stakeholders needs to meet project objectives. These requirements selected to be part of the scope baseline are generally decided by the project governance, the project sponsor, the project management team, the project's customer and inputs from different stakeholders, who are considered to be important.<ref name="PMG"/>

	The identification process of who the project stakeholders are is an important early step in the scope planning. Project stakeholder can consist of persons or organizations that are actively involved in the project or if their interests may be affected by the project. These stakeholders can be, for instance, sponsors, customers, suppliers, and shareholders.<ref name="ISO">Danish Standards Foundation. (2012). ''International Standard ISO 21500 - Guidance on project management''. København: Danish Standards Foundation.</ref> <sup>(p.6-7)</sup> It is important for the project manager of a project to set proper expectations with their stakeholders at the beginning, to ensure that no misunderstandings can appear later on. These expectations can be about how the requirements or the scope of the project is managed, controlled and verified and these expectations are one of the elements in the project scope statement that needs to be well defined.<ref name="PMG"/> The documentation of the requirements will be discussed further in the next section of the define scope process where it is an input and an essential element of the involvement of establishing the project scope statement.		The identification process of who the project stakeholders are is an important early step in the scope planning. Project stakeholder can consist of persons or organizations that are actively involved in the project or if their interests may be affected by the project. These stakeholders can be, for instance, sponsors, customers, suppliers, and shareholders.<ref name="ISO">Danish Standards Foundation. (2012). International Standard ISO 21500 - Guidance on project management. København: Danish Standards Foundation.</ref> <sup>(p.6-7)</sup> It is important for the project manager of a project to set proper expectations with their stakeholders at the beginning, to ensure that no misunderstandings can appear later on. These expectations can be about how the requirements or the scope of the project is managed, controlled and verified and these expectations are one of the elements in the project scope statement that needs to be well defined.<ref name="PMG"/> The documentation of the requirements will be discussed further in the next section of the define scope process where it is an input and an essential element of the involvement of establishing the project scope statement.

	====Define Scope====		====Define Scope====