Risultati della ricerca
Da itm wiki.
Crea la pagina "Project Management" su questo wiki! Vedi anche i risultati della ricerca
- ''[[Glossary|Change Management]]'' process is supported by a ''[[Glossary|SM]]'' ''[[Glossary|workflow car ...nly one of the possible configuration to deal with the ''[[Glossary|change management]]'' process. The need for a different behaviour of the process may be fulfi39 KB (5 855 parole) - 11:20, 18 lug 2015
- ''[[Glossary#C|Change Management]]'' process is supported by a ''[[Glossary|SM]]'' ''[[Glossary|workflow car ...nly one of the possible configuration to deal with the ''[[Glossary|change management]]'' process. The need for a different behaviour of the process may be fulfi33 KB (4 961 parole) - 15:01, 10 mag 2016
- ''[[Glossary|Release and Deployment Management]]'' process is supported by a ''[[Glossary|SM]]'' ''[[Glossary|workflow car ...ossible configuration to deal with the ''[[Glossary|release and deployment management]]'' process. The need for a different behaviour of the process may be fulfi31 KB (4 499 parole) - 10:15, 27 apr 2017
- ...tc.). The process is therefore triggered by the ''[[Release and Deployment Management]]'' process itself and returns the feedback on its result. ...ction]]'' automatically gives a feedback to the ''[[Release and Deployment Management]]'' process.16 KB (2 520 parole) - 17:53, 28 ott 2015
- == List management and creation == ...hich will be configured. || The available values are "Knowledge", "News", "Project/Service" and "Ticket".7 KB (1 078 parole) - 10:08, 4 nov 2017
- <u>''Form Designer''</u>, located in <u>''Grant Management''</u> tab, allows to define the layout of the main, <u>''General''</u>, tab ...''[[glossary|roles]],'' ''[[glossary|workflow status]]'' and ''[[glossary|project/service]]'' for which rendering the form.4 KB (704 parole) - 21:19, 10 gen 2016
- ...event is triggered when the predefined ''[[glossary|workflow field]]'' <u>Project/Service</u> is changed ...own in the figure below. In order to unlock this configuration, select the project/services desired check boxes next to them (they will get colored red) and p5 KB (736 parole) - 21:29, 14 gen 2016
- ...are managed mainly through the <u>''Deliveries''</u> tab of a ''[[glossary|project]]''. Here, it is possible to define the ''[[glossary|product breakdown stru ...ry|delivery]]'' which is produced outside of the scope of the ''[[glossary|project]]''). This is a descriptive but mandatory field.4 KB (691 parole) - 22:42, 7 feb 2016
- ...''[[glossary|user]]'' is person enabled to access itmSUITE®. The project management module manages ''[[glossary|resources]]'', not ''[[glossary|users]]'', but ...u> ''tab allows to assign the ''[[glossary|resources]]'' to a ''[[glossary|project]]''. The '''ADD NEW''' command allows to add them. Once added, the list of3 KB (544 parole) - 22:53, 16 feb 2016
- A plan of the activities of the ''[[glossary|project]]'' can be created and managed in the ''<u>Activities</u>'' tab. == Gantt and tree view of the project activities ==17 KB (2 726 parole) - 21:29, 25 feb 2016
- ...of working days and financials (to manage financials, the [[FM - Financial Management]] module is required). ...occurrences]]''. [[File:Project estimation view.JPG|none|thumb|850x850px|Project estimation screen.]]18 KB (2 991 parole) - 09:41, 6 apr 2016
- ...or by scheduling and executing check points which are called ''[[glossary|project milestones]]''. ...lan. In particular it is required to define the categories of ''[[glossary|project milestone]]'' which will be available (e.g. kick-off, progress, closure) an9 KB (1 494 parole) - 16:14, 10 mar 2016
- In order to properly deal with a ''project'', it can be needed/useful to manage additional information. ...y|Cost occurrences]]'' management is possible only if the [[FM - Financial Management]] module is active.15 KB (2 432 parole) - 20:23, 4 apr 2016
- The itmSUITE® provides a complete filter management system that implements items (ticket, timesheet, etc...) searching accordin |''Project'' || || '''X''' || '''X'''10 KB (1 383 parole) - 10:07, 16 ott 2018
- ...circumstances, a business case should be established for the ''[[glossary|project]]''. ...g. background and reasons) may also be copied and recorded in ''[[glossary|project]]'' specific fields (e.g. <u>Objectives</u> and <u>Background and Reasons</5 KB (761 parole) - 15:06, 5 apr 2016
- ...activities are performed concerning quality management for a ''[[glossary|project]]'': quality planning and quality control. ...nt strategy (which specifies the quality management system and key quality management responsibilities) and of product descriptions (including quality expectatio3 KB (396 parole) - 17:02, 5 apr 2016
- Changes to a ''[[glossary|project]]'' can be managed with different approaches. == Managing change using ''[[glossary|project activities]]'' ==1 KB (204 parole) - 07:57, 7 apr 2016
- ...] has no specific features for detailed ''[[glossary|projects]]'' benefits management currently. However, the delivery of dedicated functionalities is planned in Nevertheless basic information about ''[[glossary|project]]'' benefits may be handled in the following ways:700 byte (102 parole) - 20:44, 7 apr 2016
- ...n). Basic reporting about ''[[glossary|project issues]]'' and ''[[glossary|project risks]]'' is included in "Tree-Report" and "Summary report" available in '' ...e [[SM - Service Desk and Service Management|SM - Service Desk and Service Management module]] is activated.848 byte (139 parole) - 20:55, 7 apr 2016
- Document Management is a key feature of itmSUITE® which acts as a repository for documents. | "Project" || ''Documents'' are stored and related to ''projects''.5 KB (802 parole) - 21:14, 1 mag 2016
Vedi (precedenti 20 | successivi 20) (20 | 50 | 100 | 250 | 500).
