The sessions with all staff before deployment and

The software might not be compatible with handheld devices
thereby limiting its scope. The software
doesn’t have a mobile version available yet.       Incompatibility
would interfere with the usability of the software. Some pressing issues may
not be solved due to inaccessibility to the platform.

The manage engine system might fail      Incorrect assumptions regarding both hardware and software
requirements for the project. Issues can’t
be resolved if the system is down. It will reduce the efficiency of the
department.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

The complexity of the system might bar many staff members
from fully exploiting its potential.   Poor
development practices and user interface.       Staff
members might resist to change and continue using the old method, i.e. email or
phone.

Insufficient knowledge on how to use the software.         Lack of interest or improper training
and induction processes.                Staff
members would not fully exploit the software’s potential.

Delayed Completion of the project due to the presence of
concurrent projects/tasks.       Improper
planning and failure to prioritize projects/tasks.         Interference with deployment and post-deployment stages.

The privacy of the staff members using the platform might be
breached. Insufficient IT management best
practices since such system can easily be hacked. Users might not feel comfortable using an insecure help-desk
platform.

Resistance to change by the staff members for whom the
software is intended.  Non- acquaintance
with the system.                The
project would not achieve its purpose and would be a failure as no one would be
willing to use the new software to log IT requests/issues.

High IT expenses.            Inadequate
or improper planning.            The
project might not be completed to the expected standards and timeframe leading
to design or performance errors.

Designing and implementing additional capabilities on the
software so it can run on all commonly used devices (Desktops and mobile).

Proper implementation and support for the software through
intensive research and planning while eliminating any programs that might lead
to system failure through rigorous testing.       

Designing a user-friendly interface that would be easily
accessible to the users.  

Conducting thorough training sessions with all staff before
deployment and regular refresher sessions after the system goes live.             

All stages of the development of the help-desk software and
its implementation will be planned and followed prior to execution. The early
start (ES), early finish (EF), late start (LS), late finish (LF), critical path
and crash projects will be determined.     

Enhancing the security of the software and our own system to
ensure that it cannot be hacked or misused.           

The probability of resistance to change is quite low, especially
if everyone has been well trained on the new software. Therefore, there are no
plans for this risk.            

All stages of the development of the help-desk software and
its implementation will be planned and followed prior to execution. The early
start (ES), early finish (EF), late start (LS), late finish (LF), critical path
and crash projects will be determined.     

x

Hi!
I'm Harold!

Would you like to get a custom essay? How about receiving a customized one?

Check it out