Challenge01Your IT department or vendor aren't able to express your needs.
- Possible causes:
-
- When screening user requests, the screening shall not be based on explicit standards.
- The vendor may not insert user demands into the system requirements.
- When system requirements are compiled, any conditions pertaining to user demands should be clarified.
Prescription
- Establish a requirement management flow.
- Assess requirements from the perspective of total optimization and gain the approval of both users and the IT department.
| PMO Service (Atypical Operations Support) |
Challenge02Information system does not fit current requirements and is difficult to use.
- Possible causes:
-
- The information system cannot be modified to stay current with changes in operations and a gap has developed.
- The information system cannot cope with atypical situations.
Prescription
- Establish a requirement management flow and regularly assess ITreform .
- Delineate atypical operations flow and clarify information system management.
- Discuss IT reform in the areas most estranged from operations.
| PMO Service (Atypical Operations Support) |
Challenge03You can't understand why you are getting so little return from your IT investment.
- Possible causes:
-
- The service level in your contract is unclear.
- You are unable to skillfully discuss estimates with vendors.
Prescription
- Negotiate with vendor and clarify service level.
- Grasp industry standards and market rates via other-company examples.
- Regularly assess and 'take stock' of your current situation.
| PMO Service (Atypical Operations Support) |








