Managing Project Organization - Cronologia

Maxime.sottini il 21:40, 4 apr 2016

2016-04-04T21:40:11Z

Maxime.sottini il 21:39, 4 apr 2016

2016-04-04T21:39:22Z

Maxime.sottini il 21:27, 4 apr 2016

2016-04-04T21:27:58Z

Maxime.sottini il 21:19, 4 apr 2016

2016-04-04T21:19:37Z

Maxime.sottini il 21:18, 4 apr 2016

2016-04-04T21:18:11Z

Maxime.sottini il 21:03, 4 apr 2016

2016-04-04T21:03:08Z

Maxime.sottini il 20:41, 4 apr 2016

2016-04-04T20:41:16Z

Maxime.sottini il 20:39, 4 apr 2016

2016-04-04T20:39:52Z

Maxime.sottini il 20:33, 4 apr 2016

2016-04-04T20:33:45Z

Maxime.sottini il 20:29, 4 apr 2016

2016-04-04T20:29:30Z

@@ Riga 17: / Riga 17: @@
 Profiles corresponding to the needed privileges for a role can be designed in ''<u>Resource Grants Templates</u>'' of <u>''Module Options''</u> of '''''General/Company/Company Info'''''. In particular it is possible to assign view or modify privileges for any section of the ''[[glossary|project]]''. A ''[[glossary|resource]]'' associated with the ''[[glossary|user]]'' can be assigned to the ''[[glossary|project]]'' (e.g. by the ''[[glossary|project manager]]'', a ''[[glossary|manager]]'' or a ''[[glossary|user]]'' with a customized role and privileges on the ''[[glossary|project]]'') with a target profile (this is done in the <u>''Resources''</u> section of the ''[[Glossary|project]]'').
-The customization of a role can be completed assigning ''[[glossary|reports]]'' and visibility of general functionalities. In order to do so, first create a ''[[glossary|group]]'' corresponding to the profile ('''''General/Tickets/Groups'''''). Then you can use the ''[[glossary|group]]'' to assign to it ''[[glossary|reports]]'' and menu functionalities visibility ('''''General/Company/Main Navigation Menu''''').
+The customization of a role can be completed assigning ''[[glossary|reports]]'' and visibility of general functionalities. In order to do so, first create a ''[[glossary|group]]'' corresponding to the profile ('''''General/Tickets/Groups'''''). Then you can use the ''[[glossary|group]]'' to assign to it ''[[glossary|reports]]'' (see [[REP - Reporting|REP - Reporting module]]) and menu functionalities visibility ('''''General/Company/Main Navigation Menu''''').
 |}

@@ Riga 15: / Riga 15: @@
 | Customized role (e.g. Project Board member, Executive, Senior Use, Senior Supplier, Change Authority, Project Support, Team Manager, Team Member, etc.) ||Any ''[[glossary|user]]'' associated with an ''[[glossary|application level role]]'' "Manager", "Project Manager" or "Resource" can be granted privileges to view and or manage ''[[glossary|project]]'' data and information.
-Profiles corresponding to the needed privileges for a role can be designed in ''<u>Resource Grants Templates</u>'' of <u>''Module Options''</u> of '''''General/Company/Company Info'''''. In particular it is possible to assign view or modify privileges for any section of the ''[[glossary|project]]''. A ''[[glossary|resource]]'' associated with the ''[[glossary|user]]'' can be assigned to the ''[[glossary|project]]'' (e.g. by the ''[[glossary|project manager]]'', a ''[[glossary|manager]]'' or a ''[[glossary|user]]'' with a customized role and privileges on the ''[[glossary|project]]'').
+Profiles corresponding to the needed privileges for a role can be designed in ''<u>Resource Grants Templates</u>'' of <u>''Module Options''</u> of '''''General/Company/Company Info'''''. In particular it is possible to assign view or modify privileges for any section of the ''[[glossary|project]]''. A ''[[glossary|resource]]'' associated with the ''[[glossary|user]]'' can be assigned to the ''[[glossary|project]]'' (e.g. by the ''[[glossary|project manager]]'', a ''[[glossary|manager]]'' or a ''[[glossary|user]]'' with a customized role and privileges on the ''[[glossary|project]]'') with a target profile (this is done in the <u>''Resources''</u> section of the ''[[Glossary|project]]'').
 |}

@@ Riga 14: / Riga 14: @@
 |-
 | Customized role (e.g. Project Board member, Executive, Senior Use, Senior Supplier, Change Authority, Project Support, Team Manager, Team Member, etc.) ||Any ''[[glossary|user]]'' associated with an ''[[glossary|application level role]]'' "Manager", "Project Manager" or "Resource" can be granted privileges to view and or manage ''[[glossary|project]]'' data and information.
-rofiles corresponding to the P
 |}

@@ Riga 14: / Riga 14: @@
 |-
 | Customized role (e.g. Project Board member, Executive, Senior Use, Senior Supplier, Change Authority, Project Support, Team Manager, Team Member, etc.) ||Any ''[[glossary|user]]'' associated with an ''[[glossary|application level role]]'' "Manager", "Project Manager" or "Resource" can be granted privileges to view and or manage ''[[glossary|project]]'' data and information.
 |}

@@ Riga 7: / Riga 7: @@
 |-
-| Project Manager ||This is a built-in role. Assign the ''[[glossary|application level role]]'' "Project Manager" to the ''[[glossary|resource]]''  who shall act as a project manager. This shall be done by an ''[[glossary|administrator]]''. Then, specifically assign the ''[[glossary|resource]]''  as ''[[glossary|project manager]]'' for one or more ''[[glossary|projects]]''. This is done by setting <u>Project Manager</u> in ''[[glossary|project]]'' ''<u>General</u>'' section. This can be done either by a ''[[glossary|manager]]'' with privileges on the ''[[glossary|project]] ''or by the ''[[glossary|project manager]]'' at ''[[glossary|project]]'' creation time or    customized role with privileges (see later).The ''project manager'' has the privileges  manage any aspect of its ''[[glossary|project]]''(s).
+| Project Manager ||This is a built-in role. Assign the ''[[glossary|application level role]]'' "Project Manager" to the ''[[glossary|user]]''  who shall act as a project manager. This shall be done by an ''[[glossary|administrator]]''. Then, specifically assign the ''[[glossary|resource]]''  as ''[[glossary|project manager]]'' for one or more ''[[glossary|projects]]''. This is done by setting <u>Project Manager</u> in ''[[glossary|project]]'' ''<u>General</u>'' section. This can be done either by a ''[[glossary|manager]]'' with privileges on the ''[[glossary|project]] ''or by the ''[[glossary|project manager]]'' at ''[[glossary|project]]'' creation time or    customized role with privileges (see later).The ''project manager'' has the privileges  manage any aspect of its ''[[glossary|project]]''(s).
 |-
-| Team Resource ||This is a built-in role. Assign the [[glossary|''application level role'']] "Resource" to the ''[[glossary|resource]]'' who shall act as a project team member. This is usually
+| Team Resource ||This is a built-in role. Assign a ''[[glossary|resource]]'' to the ''project ''first and, optionally, to ''[[glossary|project activities]]'' later. This can be done by the ''[[glossary|project manager]]'' but also by a ''[[glossary|manager]]'' or any customized role with privileges (see later). This will make it possible to budget/forecast or add balance working time and expenses for the team resource. Balance data can be input directly by the team resource if associated to a ''[[glossary|user]]''.
 |-
-| Customized role (e.g. Project Board member, Executive, Senior Use, Senior Supplier, Change Authority, Project Support, Team Manager, etc.) ||
+| Customized role (e.g. Project Board member, Executive, Senior Use, Senior Supplier, Change Authority, Project Support, Team Manager, Team Member, etc.) ||Any ''[[glossary|user]]'' associated with an ''[[glossary|application level role]]'' "Manager", "Project Manager" or "Resource" can be granted privileges to view and or manage ''[[glossary|project]]'' data and information.
 |}

← Versione meno recente		Versione delle 20:39, 4 apr 2016
Riga 2:		Riga 2:

	The following is a list of possible ''[[glossary\|project]]'' roles and how to fit/manage them in itmSUITE®.		The following is a list of possible ''[[glossary\|project]]'' roles and how to fit/manage them in itmSUITE®.
		+
		+	{\| class="wikitable"
		+	! Project role !! How to manage
		+
		+	\|-
		+	\| Project Board member, Executive, Senior Use, Senior Supplier, Change Authority, Project Support \|\|
		+
		+	\|-
		+	\| Project Manager \|\|
		+
		+	\|-
		+	\| Team Manager, Team Resource \|\|
		+
		+	\|}

← Versione meno recente		Versione delle 20:33, 4 apr 2016
Riga 1:		Riga 1:
	''[[glossary\|Project]]'' organizational structure (roles and responsibilities) will certainly depends on the characteristics of the ''[[glossary\|project]]'' itself (e.g. size, complexity, etc.).		''[[glossary\|Project]]'' organizational structure (roles and responsibilities) will certainly depends on the characteristics of the ''[[glossary\|project]]'' itself (e.g. size, complexity, etc.).

−	The following is a list of ~~typical~~ ''[[glossary\|project]]'' roles and how to fit/manage them in itmSUITE®.	+	The following is a list of possible ''[[glossary\|project]]'' roles and how to fit/manage them in itmSUITE®.

← Versione meno recente		Versione delle 20:29, 4 apr 2016
Riga 1:		Riga 1:
−	~~Complete~~	+	''[[glossary\|Project]]'' organizational structure (roles and responsibilities) will certainly depends on the characteristics of the ''[[glossary\|project]]'' itself (e.g. size, complexity, etc.).
		+
		+	The following is a list of typical ''[[glossary\|project]]'' roles and how to fit/manage them in itmSUITE®.