Project configuration steps - Control - Cronologia

Maxime.sottini: /* Executing milestones */

2016-03-10T16:14:28Z

‎Executing milestones

Maxime.sottini: /* Executing milestones */

2016-03-10T16:07:14Z

‎Executing milestones

Maxime.sottini: /* Executing milestones */

2016-03-09T20:39:08Z

‎Executing milestones

Maxime.sottini: /* Scheduling a control plan */

2016-03-09T20:37:47Z

‎Scheduling a control plan

Maxime.sottini: /* Scheduling a control plan */

2016-03-09T20:22:36Z

‎Scheduling a control plan

Maxime.sottini: /* Scheduling a control plan */

2016-03-08T21:39:35Z

‎Scheduling a control plan

Maxime.sottini: /* Scheduling a control plan */

2016-03-08T21:32:42Z

‎Scheduling a control plan

Maxime.sottini il 21:31, 8 mar 2016

2016-03-08T21:31:06Z

Maxime.sottini: /* Scheduling a control plan */

2016-03-08T21:29:52Z

‎Scheduling a control plan

Maxime.sottini: /* Scheduling a control plan */

2016-03-08T21:26:16Z

‎Scheduling a control plan

← Versione meno recente		Versione delle 16:14, 10 mar 2016
Riga 140:		Riga 140:
	''[[glossary\|Project milestones]]'' are a key management element of ''[[glossary\|projects]]''. They are important check points where the progress of the project can be verified and 'certified' to become the basis of reporting and analysis.		''[[glossary\|Project milestones]]'' are a key management element of ''[[glossary\|projects]]''. They are important check points where the progress of the project can be verified and 'certified' to become the basis of reporting and analysis.

−	Executing a ''[[glossary\|project milestone]]'' is a straightforward process: it's enough to save the ''[[glossary\|project milestone]]'' after changing its <u>Status</u> to "Executed". It is important to remember that after executing the ''[[glossary\|project milestone]]'' IT WON'T BE POSSIBLE TO UPDATE ITS CONTENT. So remember to carefully check that all information about the ''[[glossary\|project milestone]]'' are correct before proceeding.	+	Executing a ''[[glossary\|project milestone]]'' is a straightforward process: it's enough to save the ''[[glossary\|project milestone]]'' after changing its <u>Status</u> to "Executed". It is important to remember that after executing the ''[[glossary\|project milestone]]'' IT WON'T BE POSSIBLE TO UPDATE ITS CONTENT. So remember to carefully check that all information about the ''[[glossary\|project milestone]]'' are correct before proceeding. The information to be updated are those contained explained in the previous paragraph. Additionally, it is important to link an ''[[glossary\|estimation]]'' to the ''[[glossary\|project milestone]]''. This can be done using the '''CERTIFY''' command in the ''[[glossary\|project milestone]]'' form. It will allow to browse the ''[[glossary\|estimation repository]]'' in search of the [[glossary\|estimation]] to link to the ''[[glossary\|project milestone]]''.
−
−	he information T

← Versione meno recente		Versione delle 16:07, 10 mar 2016
Riga 138:		Riga 138:

	== Executing milestones ==		== Executing milestones ==
−	''[[glossary\|Project milestones]]'' are a key management element of ''[[glossary\|projects]]'' .....	+	''[[glossary\|Project milestones]]'' are a key management element of ''[[glossary\|projects]]''. They are important check points where the progress of the project can be verified and 'certified' to become the basis of reporting and analysis.
		+
		+	Executing a ''[[glossary\|project milestone]]'' is a straightforward process: it's enough to save the ''[[glossary\|project milestone]]'' after changing its <u>Status</u> to "Executed". It is important to remember that after executing the ''[[glossary\|project milestone]]'' IT WON'T BE POSSIBLE TO UPDATE ITS CONTENT. So remember to carefully check that all information about the ''[[glossary\|project milestone]]'' are correct before proceeding.
		+
		+	he information T

← Versione meno recente		Versione delle 20:39, 9 mar 2016
Riga 136:		Riga 136:

	\|}		\|}
−
−	~~Wizard....~~

	== Executing milestones ==		== Executing milestones ==
		+	''[[glossary\|Project milestones]]'' are a key management element of ''[[glossary\|projects]]'' .....

@@ Riga 29: / Riga 29: @@
 == Scheduling a control plan ==
 A control plan consists of a sequence of scheduled ''[[glossary|project milestones]]''. This can be defined in the ''<u>Milestones</u>'' ''[[glossary|project]]'' section. A sample control plan is shown in the image below.
-[[File:Project control plan.JPG|none|thumb|850x850px|Project control plan]]It is possible to add, update and delete ''[[glossary|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]]).
+[[File:Project control plan.JPG|none|thumb|850x850px|Project control plan]]It is possible to add, update and delete ''[[glossary|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]]). However, it is also possible to massively add ''[[glossary|project milestones]]''. This can be done by focusing with the mouse on a ''[[glossary|project milestone]]'' in grid and choosing the '''Add New Wizard''' or '''Insert Before Wizard''' command from the mouse right button enabled menu. This will open a form which allows to enter the parameters used to generate a set of ''[[glossary|project milestones]]'' automatically. After the ''[[glossary|project milestones]]'' are added to the grid, it is finally possible to refine them by editing directly in the grid or in the details form.
 The following table explains the ''[[glossary|project milestone]]'' information to be managed.

@@ Riga 30: / Riga 30: @@
 A control plan consists of a sequence of scheduled ''[[glossary|project milestones]]''. This can be defined in the ''<u>Milestones</u>'' ''[[glossary|project]]'' section. A sample control plan is shown in the image below.
 [[File:Project control plan.JPG|none|thumb|850x850px|Project control plan]]It is possible to add, update and delete ''[[glossary|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 ''[[glossary|project milestone]]'' information to be managed.

@@ Riga 124: / Riga 124: @@
 |-
-| <u>Documents</u> ||           ||
+| <u>''Documents''</u> ||           A section where documents related to the ''[[glossary|project milestone]]'' can be added. See also [[Documents management|document management]].
 |-
-| <u>Deliveries</u> ||           ||
+| <u>''Deliveries''</u> ||           A section where one or more ''[[glossary|project deliveries]]'' can be linked to the ''[[glossary|project milestone]]''.
 |-
-| <u>Messages</u> ||           ||
+| <u>''Messages''</u> ||           A section where one or more ''[[glossary|messages]]'' related to the ''[[glossary|project milestone]]'' can be exchanged. See also [[message management]].
 |}

@@ Riga 122: / Riga 122: @@
 | <u>Comments in Portfolio</u> ||           A text for comments.
 ||   This comment is visible in published in the ''[[glossary|project portfolio]]''.
 |}

@@ Riga 112: / Riga 112: @@
 |-
-| <u>Next Goals</u> ||           ||
+| <u>Next Goals</u> ||           A text which can be used to describe the goals set for the period of time from the current ''[[glossary|project milestone]]'' to the next one.
 |-
-| <u>Internal Comments</u> ||           ||
+| <u>Internal Comments</u> ||           A text for comments.
 |-
-| <u>Comments in Portfolio</u> ||           ||
+| <u>Comments in Portfolio</u> ||           A text for comments.
 |}

@@ Riga 110: / Riga 110: @@
 | <u>Accomplishments not Met</u> ||           A text which can be used to describe the ''[[glossary|project]] ''accomplishments not achieved in the period from the previous ''[[glossary|project milestone]] ''to the current one.
 ||
 |-
 | <u>Next Goals</u> ||           ||
 |-
 | <u>Internal Comments</u> ||           ||
 |-
@@ Riga 131: / Riga 121: @@
 |}
 Wizard....
 == Executing milestones ==