Differenze tra le versioni di "Project configuration steps - Control"
(→Scheduling a control plan) (Etichetta: visualeditor) |
(→Scheduling a control plan) (Etichetta: visualeditor) |
||
| Riga 38: | Riga 38: | ||
|- | |- | ||
| − | | <u>Creation Date</u>|| || | + | | <u>Creation Date</u>|| The creation date of the ''[[glossary|project milestone]]''. |
| + | || Automatically updated by the system. | ||
|- | |- | ||
| − | | <u>Creation User</u>|| || | + | | <u>Creation User</u>|| The creation [[glossary|user]] of the ''[[glossary|project milestone]]''. |
| + | || Automatically updated by the system. | ||
|- | |- | ||
| Riga 61: | Riga 63: | ||
|- | |- | ||
| − | | <u>Number</u> || || | + | | <u>Number</u> || The identification number of the ''[[glossary|project milestone]]''. |
| + | || Automatically created by the system. | ||
|- | |- | ||
Versione delle 12:20, 8 mar 2016
It is possible to control the progress and performances of the project. This can be done using the key performance indicators (see semaphores for more information) of the current loaded project estimation or by scheduling and executing check points which are called project milestones.
We will now explain hot to configure and execute a control plan.
Basic settings
The key elements of the control plan are the check points, named project milestones. There are some settings, in General/Projects/Milestones, to be completed concerning project milestones before starting with the scheduling of a control plan. In particular it is required to define the categories of project milestone which will be available (e.g. kick-off, progress, closure) and the relationships among them,
For each project milestone category, it is required to define the following parameters as shown in the table below.
| Field | Description | Comment
|
|---|---|---|
| Name | This is the name of the project milestone category. | This will be shown in the categories of available project milestones when adding a project milestone in the control plan. |
| Type | This is the type of the project milestone and it can be chosen among those predefined ("kick-off", "Closing" and "Others"). | There can be only one project milestone category of Type "Kick-off" and of Type "Closing". There can be many of Type "Others". |
| List of predecessors | This field will contain the list of project milestone categories which can be predecessors of the currently edited one. | This is used to force the correct schedule of project milestones in the project control plan. For example to avoid that a kick-off meeting is scheduled after a project closing meeting. |
Scheduling a control plan
A control plan consists of a sequence of scheduled project milestones. This can be defined in the Milestones project section. A sample control plan is shown in the image below.
It is possible to add, update and delete project milestones in the control plan with the grid mode functionalities. It is possible to filter the list with the FILTER command (see filters management).
The following table explains the project milestone information to be managed.
| Field | Description | Comment
|
|---|---|---|
| Creation Date | The creation date of the project milestone. | Automatically updated by the system. |
| Creation User | The creation user of the project milestone. | Automatically updated by the system. |
| Modification Date | ||
| Modification User |
| |
| Estimation Date | ||
| Estimation |
| |
| Description | ||
| Number | The identification number of the project milestone. | Automatically created by the system. |
| Type | ||
| Result | ||
| Is Internal | ||
| Publish in Portfolio | ||
| Status | ||
| Scheduled Execution Date | ||
| Actual Execution Date | ||
| Full Description | ||
| Period Accomplishments | ||
| Accomplishments not Met | ||
| Creation Date | ||
| Next Goals | ||
| Creation Date | ||
| Internal Comments | ||
| Creation Date | ||
| Comments in Portfolio |
