Managing Change - Cronologia

Maxime.sottini: /* Managing change using project RFCs */

2016-04-07T07:57:58Z

‎Managing change using project RFCs

Maxime.sottini il 07:54, 7 apr 2016

2016-04-07T07:54:26Z

Maxime.sottini: /* Managing change using project RFCs */

2016-04-07T07:44:00Z

‎Managing change using project RFCs

Maxime.sottini il 06:21, 7 apr 2016

2016-04-07T06:21:00Z

Maxime.sottini il 06:11, 7 apr 2016

2016-04-07T06:11:49Z

Maxime.sottini il 06:10, 7 apr 2016

2016-04-07T06:10:09Z

Maxime.sottini: Created page with "Changes to a ''project'' can be managed with different approaches. Using projec This can be done with two approaches. The easiest consists of using ''project..."

2016-04-06T10:21:52Z

Created page with "Changes to a ''project'' can be managed with different approaches. Using projec This can be done with two approaches. The easiest consists of using ''project..."

Nuova pagina

Changes to a ''[[glossary|project]]'' can be managed with different approaches.

Using projec

This can be done with two approaches. The easiest consists of using ''project activities'' (managed in project ''Activities'' section) to plan and track the results of quality methods (e.g. the execution of a test). Specific quality related information can be added to ''project activities'' in ''Activities''section. A more advanced and flexible approach consists of configuring and using ''workflows'' in order to support the execution of quality methods. For example a specific workflow could be designed to execute a product quality inspection. The ''workflow'' records (and associated reporting) can be used to implement the quality register concept. However, the use of ''workflows ''requires the activation of the SM - Service Desk and Service Management module.

@@ Riga 5: / Riga 5: @@
 == Managing change using ''[[glossary|project RFCs]]'' ==
-In ''[[glossary|project]]'' ''<u>Issues/Risks</u>'' section it is possible to manage a special type of record: "RFC". These elements can be used to manage the changes to the ''project''. See
+In ''[[glossary|project]]'' ''<u>Issues/Risks</u>'' section it is possible to manage a special type of record: "RFC". These elements can be used to manage the changes to the ''project''. See the [[Project configuration steps - Others#Issues/Risks|issues/risks configuration page]] for additional details.
 == Managing change using ''[[glossary|workflows]]'' ==
 A more advanced and flexible approach consists of configuring and using ''workflows'' in order to support the execution of ''[[glossary|project]]'' changes lifecycle. However, the use of ''[[glossary|workflows]] ''requires the activation of the [[SM - Service Desk and Service Management|SM - Service Desk and Service Management module]].

@@ Riga 5: / Riga 5: @@
 == Managing change using ''[[glossary|project RFCs]]'' ==
-In ''[[glossary|project]]'' ''<u>Issues/Risks</u>'' section it is possible to manage a special type of record: "RFC". These elements can be used to manage the changes to the ''project''.
+In ''[[glossary|project]]'' ''<u>Issues/Risks</u>'' section it is possible to manage a special type of record: "RFC". These elements can be used to manage the changes to the ''project''. See
 == Managing change using ''[[glossary|workflows]]'' ==
 A more advanced and flexible approach consists of configuring and using ''workflows'' in order to support the execution of ''[[glossary|project]]'' changes lifecycle. However, the use of ''[[glossary|workflows]] ''requires the activation of the [[SM - Service Desk and Service Management|SM - Service Desk and Service Management module]].

@@ Riga 5: / Riga 5: @@
 == Managing change using ''[[glossary|project RFCs]]'' ==
 == Managing change using ''[[glossary|workflows]]'' ==
-This can be done with two approaches. The easiest consists of using ''project activities'' (managed in project ''Activities'' section) to plan and track the results of quality methods (e.g. the execution of a test). Specific quality related information can be added to ''project activities'' in ''Activities''section. A more advanced and flexible approach consists of configuring and using ''workflows'' in order to support the execution of quality methods. For example a specific workflow could be designed to execute a product quality inspection. The ''workflow'' records (and associated reporting) can be used to implement the quality register concept. However, the use of ''workflows ''requires the activation of the SM - Service Desk and Service Management module.
+A more advanced and flexible approach consists of configuring and using ''workflows'' in order to support the execution of ''[[glossary|project]]'' changes lifecycle. However, the use of ''[[glossary|workflows]] ''requires the activation of the [[SM - Service Desk and Service Management|SM - Service Desk and Service Management module]].

@@ Riga 1: / Riga 1: @@
 Changes to a ''[[glossary|project]]'' can be managed with different approaches.
-Using project activities
+== Managing change using ''[[glossary|project activities]]'' ==
-Using project RFCs
+== Managing change using ''[[glossary|project RFCs]]'' ==
 This can be done with two approaches. The easiest consists of using ''project activities'' (managed in project ''Activities'' section) to plan and track the results of quality methods (e.g. the execution of a test). Specific quality related information can be added to ''project activities'' in ''Activities''section. A more advanced and flexible approach consists of configuring and using ''workflows'' in order to support the execution of quality methods. For example a specific workflow could be designed to execute a product quality inspection. The ''workflow'' records (and associated reporting) can be used to implement the quality register concept. However, the use of ''workflows ''requires the activation of the SM - Service Desk and Service Management module.

@@ Riga 1: / Riga 1: @@
 Changes to a ''[[glossary|project]]'' can be managed with different approaches.
-Using projec
+Using project activities
+Using project RFCs
-FCs
+Using workflow management
 This can be done with two approaches. The easiest consists of using ''project activities'' (managed in project ''Activities'' section) to plan and track the results of quality methods (e.g. the execution of a test). Specific quality related information can be added to ''project activities'' in ''Activities''section. A more advanced and flexible approach consists of configuring and using ''workflows'' in order to support the execution of quality methods. For example a specific workflow could be designed to execute a product quality inspection. The ''workflow'' records (and associated reporting) can be used to implement the quality register concept. However, the use of ''workflows ''requires the activation of the SM - Service Desk and Service Management module.

← Versione meno recente		Versione delle 06:10, 7 apr 2016
Riga 2:		Riga 2:

	Using projec		Using projec
		+
		+	R
		+
		+	FCs

	This can be done with two approaches. The easiest consists of using ''project activities'' (managed in project ''Activities'' section) to plan and track the results of quality methods (e.g. the execution of a test). Specific quality related information can be added to ''project activities'' in ''Activities''section. A more advanced and flexible approach consists of configuring and using ''workflows'' in order to support the execution of quality methods. For example a specific workflow could be designed to execute a product quality inspection. The ''workflow'' records (and associated reporting) can be used to implement the quality register concept. However, the use of ''workflows ''requires the activation of the SM - Service Desk and Service Management module.		This can be done with two approaches. The easiest consists of using ''project activities'' (managed in project ''Activities'' section) to plan and track the results of quality methods (e.g. the execution of a test). Specific quality related information can be added to ''project activities'' in ''Activities''section. A more advanced and flexible approach consists of configuring and using ''workflows'' in order to support the execution of quality methods. For example a specific workflow could be designed to execute a product quality inspection. The ''workflow'' records (and associated reporting) can be used to implement the quality register concept. However, the use of ''workflows ''requires the activation of the SM - Service Desk and Service Management module.