Differenze tra le versioni di "Managing Change"
(Etichetta: visualeditor) |
(→Managing change using project RFCs) (Etichetta: visualeditor) |
||
| Riga 5: | Riga 5: | ||
== Managing change using ''[[glossary|project RFCs]]'' == | == 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''. | ||
| + | |||
| + | ee S | ||
== Managing change using ''[[glossary|workflows]]'' == | == 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]]. | |
Versione delle 07:44, 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
In project Issues/Risks section it is possible to manage a special type of record: "RFC". These elements can be used to manage the changes to the project.
ee S
Managing change using workflows
A more advanced and flexible approach consists of configuring and using workflows in order to support the execution of project changes lifecycle. However, the use of workflows requires the activation of the SM - Service Desk and Service Management module.
