Scope creep - Revision history

Tkokotas: /* Handle Scope Creep */

2018-12-21T15:41:03Z

Handle Scope Creep

← Older revision		Revision as of 15:41, 21 December 2018
Line 43:		Line 43:
	==Handle Scope Creep==		==Handle Scope Creep==

	[[File:~~Scopecreep2~~.png\|400px\|thumb\|right\|Flow chart: How to deal with a scope change request ]]		[[File:scopecreep2.png\|400px\|thumb\|right\|Flow chart: How to deal with a scope change request ]]

	You are in the middle of a project, and small requests from the clients, which by itself seem harmless, are suddenly overwhelming, and the project is now on the road to failure. Scope creep is very much happening. There are a few things to have in mind, when your project is affected by scope creep <ref name="Script"/> . First step is to identify the scope creep. Why is it happening, and what is the impact of the scope creep? When the scope creep is identified you need to re-organize your work, so the creep can be managed and your project can get back on track. Decisions have to be made: what is necessary to do? Does the scope need to change, obtain more resources, or is it essential to delay the project release date? An important tool to handle scope creep is to make it the costumer’s cost creep. Set a new price on all the new requirements, so the scope creep translates to a financial issue on the costumer’s side. The final step when dealing with scope creep is communication: communicate the changes in the project, regardless if it is changes in scope, time or workload. It is important to keep the team motivated, even though the project is changing during the work period.		You are in the middle of a project, and small requests from the clients, which by itself seem harmless, are suddenly overwhelming, and the project is now on the road to failure. Scope creep is very much happening. There are a few things to have in mind, when your project is affected by scope creep <ref name="Script"/> . First step is to identify the scope creep. Why is it happening, and what is the impact of the scope creep? When the scope creep is identified you need to re-organize your work, so the creep can be managed and your project can get back on track. Decisions have to be made: what is necessary to do? Does the scope need to change, obtain more resources, or is it essential to delay the project release date? An important tool to handle scope creep is to make it the costumer’s cost creep. Set a new price on all the new requirements, so the scope creep translates to a financial issue on the costumer’s side. The final step when dealing with scope creep is communication: communicate the changes in the project, regardless if it is changes in scope, time or workload. It is important to keep the team motivated, even though the project is changing during the work period.

Tkokotas: /* Handle Scope Creep */

2018-12-21T15:40:38Z

Handle Scope Creep

← Older revision		Revision as of 15:40, 21 December 2018
Line 43:		Line 43:
	==Handle Scope Creep==		==Handle Scope Creep==

	[[File:~~Scopecreep~~.png\|400px\|thumb\|right\|Flow chart: How to deal with a scope change request ]]		[[File:Scopecreep2.png\|400px\|thumb\|right\|Flow chart: How to deal with a scope change request ]]

	You are in the middle of a project, and small requests from the clients, which by itself seem harmless, are suddenly overwhelming, and the project is now on the road to failure. Scope creep is very much happening. There are a few things to have in mind, when your project is affected by scope creep <ref name="Script"/> . First step is to identify the scope creep. Why is it happening, and what is the impact of the scope creep? When the scope creep is identified you need to re-organize your work, so the creep can be managed and your project can get back on track. Decisions have to be made: what is necessary to do? Does the scope need to change, obtain more resources, or is it essential to delay the project release date? An important tool to handle scope creep is to make it the costumer’s cost creep. Set a new price on all the new requirements, so the scope creep translates to a financial issue on the costumer’s side. The final step when dealing with scope creep is communication: communicate the changes in the project, regardless if it is changes in scope, time or workload. It is important to keep the team motivated, even though the project is changing during the work period.		You are in the middle of a project, and small requests from the clients, which by itself seem harmless, are suddenly overwhelming, and the project is now on the road to failure. Scope creep is very much happening. There are a few things to have in mind, when your project is affected by scope creep <ref name="Script"/> . First step is to identify the scope creep. Why is it happening, and what is the impact of the scope creep? When the scope creep is identified you need to re-organize your work, so the creep can be managed and your project can get back on track. Decisions have to be made: what is necessary to do? Does the scope need to change, obtain more resources, or is it essential to delay the project release date? An important tool to handle scope creep is to make it the costumer’s cost creep. Set a new price on all the new requirements, so the scope creep translates to a financial issue on the costumer’s side. The final step when dealing with scope creep is communication: communicate the changes in the project, regardless if it is changes in scope, time or workload. It is important to keep the team motivated, even though the project is changing during the work period.

Tkokotas: /* Handle Scope Creep */

2018-12-21T15:38:34Z

Handle Scope Creep

← Older revision		Revision as of 15:38, 21 December 2018
Line 43:		Line 43:
	==Handle Scope Creep==		==Handle Scope Creep==

	[[File:~~scopecreep~~.png\|400px\|thumb\|right\|Flow chart: How to deal with a scope change request ]]		[[File:Scopecreep.png\|400px\|thumb\|right\|Flow chart: How to deal with a scope change request ]]

	You are in the middle of a project, and small requests from the clients, which by itself seem harmless, are suddenly overwhelming, and the project is now on the road to failure. Scope creep is very much happening. There are a few things to have in mind, when your project is affected by scope creep <ref name="Script"/> . First step is to identify the scope creep. Why is it happening, and what is the impact of the scope creep? When the scope creep is identified you need to re-organize your work, so the creep can be managed and your project can get back on track. Decisions have to be made: what is necessary to do? Does the scope need to change, obtain more resources, or is it essential to delay the project release date? An important tool to handle scope creep is to make it the costumer’s cost creep. Set a new price on all the new requirements, so the scope creep translates to a financial issue on the costumer’s side. The final step when dealing with scope creep is communication: communicate the changes in the project, regardless if it is changes in scope, time or workload. It is important to keep the team motivated, even though the project is changing during the work period.		You are in the middle of a project, and small requests from the clients, which by itself seem harmless, are suddenly overwhelming, and the project is now on the road to failure. Scope creep is very much happening. There are a few things to have in mind, when your project is affected by scope creep <ref name="Script"/> . First step is to identify the scope creep. Why is it happening, and what is the impact of the scope creep? When the scope creep is identified you need to re-organize your work, so the creep can be managed and your project can get back on track. Decisions have to be made: what is necessary to do? Does the scope need to change, obtain more resources, or is it essential to delay the project release date? An important tool to handle scope creep is to make it the costumer’s cost creep. Set a new price on all the new requirements, so the scope creep translates to a financial issue on the costumer’s side. The final step when dealing with scope creep is communication: communicate the changes in the project, regardless if it is changes in scope, time or workload. It is important to keep the team motivated, even though the project is changing during the work period.

	The local pizza guy is suddenly overwhelmed by all the new add-ons to the pizza order. He is experiencing scope creep. He has identified the scope creep and the impacts are both slip in cost and time. He can either refuse the costumer’s order change or he can make it the costumer’s cost creep. Tell the costumer “''yes, I will add fresh tomatoes to your pizza, but you need to pay 10 DKK extra''”. The costumer is now aware of the cost consequence followed by the add-on. Last the changes in scope need to be communicated to both the costumer and the rest of the team. Tell the costumer that the change in order leads to an extended waiting time, and tell the rest of the pizza team due to unexpected changes you will be delayed working on this particular order.		The local pizza guy is suddenly overwhelmed by all the new add-ons to the pizza order. He is experiencing scope creep. He has identified the scope creep and the impacts are both slip in cost and time. He can either refuse the costumer’s order change or he can make it the costumer’s cost creep. Tell the costumer “''yes, I will add fresh tomatoes to your pizza, but you need to pay 10 DKK extra''”. The costumer is now aware of the cost consequence followed by the add-on. Last the changes in scope need to be communicated to both the costumer and the rest of the team. Tell the costumer that the change in order leads to an extended waiting time, and tell the rest of the pizza team due to unexpected changes you will be delayed working on this particular order.


	==Is Scope Creep Always Bad?==		==Is Scope Creep Always Bad?==

Tkokotas at 11:54, 9 November 2018

2018-11-09T11:54:37Z

← Older revision		Revision as of 11:54, 9 November 2018
Line 103:		Line 103:
	A text book written by the famous Harvey Maylor about project management. The book covers many interesting topics of project management, and is divided into two major parts: “''Making sense of the project context''” and “''Managing the project process''” (Define it, Design it, Do it and Develop it). The source is highly relevant in terms of more academic information and includes many real life examples.		A text book written by the famous Harvey Maylor about project management. The book covers many interesting topics of project management, and is divided into two major parts: “''Making sense of the project context''” and “''Managing the project process''” (Define it, Design it, Do it and Develop it). The source is highly relevant in terms of more academic information and includes many real life examples.

	[[~~Categories~~:~~Purpose~~]][[~~Categories~~:~~Scope~~]][[~~Categories~~:~~Project Management~~]]		[[Category:Project Management]][[Category:Purpose]][[Category:Scope]]

Tkokotas at 11:52, 9 November 2018

2018-11-09T11:52:39Z

← Older revision		Revision as of 11:52, 9 November 2018
Line 1:		Line 1:
			''Developed by Nathalie Lückstädt Nielsen''


	==Abstract==		==Abstract==
Line 100:		Line 102:

	A text book written by the famous Harvey Maylor about project management. The book covers many interesting topics of project management, and is divided into two major parts: “''Making sense of the project context''” and “''Managing the project process''” (Define it, Design it, Do it and Develop it). The source is highly relevant in terms of more academic information and includes many real life examples.		A text book written by the famous Harvey Maylor about project management. The book covers many interesting topics of project management, and is divided into two major parts: “''Making sense of the project context''” and “''Managing the project process''” (Define it, Design it, Do it and Develop it). The source is highly relevant in terms of more academic information and includes many real life examples.

			[[Categories:Purpose]][[Categories:Scope]][[Categories:Project Management]]

S130038 at 10:39, 27 September 2017

2017-09-27T10:39:48Z

← Older revision		Revision as of 10:39, 27 September 2017
Line 46:		Line 46:

	The local pizza guy is suddenly overwhelmed by all the new add-ons to the pizza order. He is experiencing scope creep. He has identified the scope creep and the impacts are both slip in cost and time. He can either refuse the costumer’s order change or he can make it the costumer’s cost creep. Tell the costumer “''yes, I will add fresh tomatoes to your pizza, but you need to pay 10 DKK extra''”. The costumer is now aware of the cost consequence followed by the add-on. Last the changes in scope need to be communicated to both the costumer and the rest of the team. Tell the costumer that the change in order leads to an extended waiting time, and tell the rest of the pizza team due to unexpected changes you will be delayed working on this particular order.		The local pizza guy is suddenly overwhelmed by all the new add-ons to the pizza order. He is experiencing scope creep. He has identified the scope creep and the impacts are both slip in cost and time. He can either refuse the costumer’s order change or he can make it the costumer’s cost creep. Tell the costumer “''yes, I will add fresh tomatoes to your pizza, but you need to pay 10 DKK extra''”. The costumer is now aware of the cost consequence followed by the add-on. Last the changes in scope need to be communicated to both the costumer and the rest of the team. Tell the costumer that the change in order leads to an extended waiting time, and tell the rest of the pizza team due to unexpected changes you will be delayed working on this particular order.


	==Is Scope Creep Always Bad?==		==Is Scope Creep Always Bad?==

S130038 at 10:39, 27 September 2017

2017-09-27T10:39:27Z

← Older revision		Revision as of 10:39, 27 September 2017
Line 36:		Line 36:

	The negative effects of scope creep can with these five suggestions be avoided and handled carefully. The key words in avoiding scope creep are transparency, good planning and overview. The limitations with these five suggestions are that it is always easier to write down suggestion than actually implement them. You and your project team are hired by a costumer and one golden rule is that the costumer is always right. <ref name="Limitations"/> If the customer demands a change in the scope halfway through the project, it is not easy to contradict this demand - a pizza guy refusing to add fresh tomatoes to your pizza does not equal a satisfied costumer. A happy costumer in the end of a project leads to a great reputation and consequently more work in the future.		The negative effects of scope creep can with these five suggestions be avoided and handled carefully. The key words in avoiding scope creep are transparency, good planning and overview. The limitations with these five suggestions are that it is always easier to write down suggestion than actually implement them. You and your project team are hired by a costumer and one golden rule is that the costumer is always right. <ref name="Limitations"/> If the customer demands a change in the scope halfway through the project, it is not easy to contradict this demand - a pizza guy refusing to add fresh tomatoes to your pizza does not equal a satisfied costumer. A happy costumer in the end of a project leads to a great reputation and consequently more work in the future.

S130038 at 10:37, 27 September 2017

2017-09-27T10:37:50Z

← Older revision		Revision as of 10:37, 27 September 2017
Line 1:		Line 1:

	==Abstract==		==Abstract==
	The following article describes the project management phenomenon scope creep. The definitions of project scope and product scope as well as scope creep are discussed. Scope creep is the definition that describes the continuous change in scope during a project phase. Scope creep can happen both in relation to project and product scope. Product scope creep can happen both naturally and when a stakeholder demands a new feature of the product. Project scope creep can happen when a project team is taken a new working direction with a project - both intentionally and unintentionally. Natural changes will happen in project all the time, and a project rarely delivers exactly what was asked for on day one of the project. The key to avoid scope creep is to handle these changes carefully, so this article also discusses tools to avoid scope creep. The key words in avoiding scope creep are transparency, good planning and overview. Suggestions on how to handle scope creep are also given, if this is unavoidable.		The following article describes the project management phenomenon scope creep. The definitions of project scope and product scope as well as scope creep are discussed. Scope creep is the definition that describes the continuous change in scope during a project phase. Scope creep can happen both in relation to project and product scope. Product scope creep can happen both naturally and when a stakeholder demands a new feature of the product. Project scope creep can happen when a project team is taken a new working direction with a project - both intentionally and unintentionally. Natural changes will happen in project all the time, and a project rarely delivers exactly what was asked for on day one of the project. The key to avoid scope creep is to handle these changes carefully, so this article also discusses tools to avoid scope creep. The key words in avoiding scope creep are transparency, good planning and overview. Suggestions on how to handle scope creep are also given, if this is unavoidable.

S130038 at 10:37, 27 September 2017

2017-09-27T10:37:22Z

← Older revision		Revision as of 10:37, 27 September 2017
Line 9:		Line 9:

	Scope creep, also called requirement creep or function creep, happens when these deliverables, along with ineffective change control, are not entirely defined, described and mapped. <ref name="ISO"/>		Scope creep, also called requirement creep or function creep, happens when these deliverables, along with ineffective change control, are not entirely defined, described and mapped. <ref name="ISO"/>


	==Scope Creep==		==Scope Creep==

S130038: /* Scope */

2017-09-27T10:36:34Z

Scope

← Older revision		Revision as of 10:36, 27 September 2017
Line 4:		Line 4:

	==Scope==		==Scope==
	It is important to know the definition of scope before discussing the concept of scope creep. The term scope does in project management imply two different things: ~~Project Scope~~ and ~~Product Scope~~ <ref name="Scoping"/>. Project ~~Scope~~ is the “''how’s''” and is more focused on the work that needs to be completed to deliver a product, result or service. Product scope is on the other hand the “''what’s''” - this is directly compared with the product, result or service and is more focused on the requirements of these. So scope states detailed deliverables and features of a project. <ref name="Scope"/>		It is important to know the definition of scope before discussing the concept of scope creep. The term scope does in project management imply two different things: project scope and product scope <ref name="Scoping"/>. Project scope is the “''how’s''” and is more focused on the work that needs to be completed to deliver a product, result or service. Product scope is on the other hand the “''what’s''” - this is directly compared with the product, result or service and is more focused on the requirements of these. So scope states detailed deliverables and features of a project. <ref name="Scope"/>

	An everyday example of the difference on project and product scope is found in the work of your local pizza place. A costumer comes in to order and bring home a freshly made pizza. The product scope is a pizza with the desired toppings. The project scope is on the other hand the work a pizza requires. This could be making the dough, preparing the toppings, baking the pizza and so on.		An everyday example of the difference on project and product scope is found in the work of your local pizza place. A costumer comes in to order and bring home a freshly made pizza. The product scope is a pizza with the desired toppings. The project scope is on the other hand the work a pizza requires. This could be making the dough, preparing the toppings, baking the pizza and so on.