Differenze tra le versioni di "Managing Change"
(Etichetta: visualeditor) |
|||
| Riga 1: | Riga 1: | ||
Changes to a ''[[glossary|project]]'' can be managed with different approaches. | Changes to a ''[[glossary|project]]'' can be managed with different approaches. | ||
| − | + | == Managing change using ''[[glossary|project activities]]'' == | |
| + | An easy approach to manage changes is to use ''[[glossary|project activities]]''. These can be categorized ('''''General/Projects/Activity Types''''') and change activities could be assigned a specific type , eg. "Project change". Information about the changes can be stored and managed in the related ''[[glossary|project activities]]'' (see [[Project configuration steps - Activity plan|project activities configuration page]] for more information). | ||
| − | + | == 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. | 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 delle 06:21, 7 apr 2016
Changes to a project can be managed with different approaches.
Managing change using project activities
An easy approach to manage changes is to use project activities. These can be categorized (General/Projects/Activity Types) and change activities could be assigned a specific type , eg. "Project change". Information about the changes can be stored and managed in the related project activities (see project activities configuration page for more information).
Managing change using project RFCs
Managing change using 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 Activitiessection. 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.
