|
| |
|
Establishing the IT Project Office |
|
|
| |
The Need: |
| |
|
|
|
| |
Continued
project failures brought about by inconsistent approaches, inaccurate
progress reports, poor communication and lack of plans and procedures. |
| |
|
|
|
| |
The
Objective: |
| |
|
|
|
| |
To establish
a department responsible for instituting and enforcing project standards,
procedures, methods and reporting. |
| |
|
| |
Approach: |
|
| |
|
|
| |
|
Ø |
People -
Utilization and time reporting, resource availability |
|
| |
|
Ø |
Processes -
Project initiation an authorization, system development life-cycle
methodology, post-implementation reviews |
|
| |
|
|
| |
|
Ø |
Schedule -
Project time-line, critical path, estimate to complete |
|
| |
|
Ø |
Cost - People
and equipment, budget vs. actual, project development and system life cycle
cost |
|
|
|
|
|
|
|
| |
Results: |
|
| |
|
|
| |
Improved
stability, consistency and visibility over project status and resource use. |
|
| |
|
|
| |
Benefits: |
|
| |
|
|
| |
Establishing
the project office reduces the risk of project failure and prevents losses
incurred through missed deadlines and project failure. |
|
|
To see an example of this service in
action, click on the button below to view Success Stories: |
| |
 |
Retail Bank |
| |
|
Middle East
Government Authority |
| |
|
|
|
