Project Management for Developing a Paperless Interface

Running head: PROJECT MANAGEMENT FOR DEVELOPING PAPERLESS INTERFACE
Developing a paperless application to smoothen the workflow
Name of the Student:
Name of the University:

1PROJECT MANAGEMENT FOR DEVELOPING A PAPERLESS INTERFACE
Abstract
In this new technical era, most of the complex and long terms projects are failing to live
up to the guarantee and producing disappointing outcomes after the finish of the project. It is
determined that efficiency of production operation and functions are relies on workflow. It helps
saving employee time and make sure that team is working effectively. PRINCE2 project
management methodology is the best suited approach that reduces the chances of project related
errors. The reasons for which mainly projects fail to reach preliminary expectations are: poorly
defined project scope statement, improper risk management plan, inappropriate identification of
project key assumptions, lack of training and experiences among the project team associates and
supervisor, ineffective communication strategies, poor management plan etc.
Introduction
The aim of Software IT Company “Fingent” is to “develop a paperless interface” for
improving their business effectiveness, operational and functional excellence.
It is obligation of the Information Technology project director to grant the new software
program as soon as the Chief Executive Officer (CEO) granted the system in details. However,
after reading the paper it has been identified some issues with the program those were required to
be solved as immediately as possible without any kinds of delay. It is important to protect the
allowance and bunged the system being introduced (Aga, Noorderhaven & Vallejo, 2016). It is
identified some risks with the interface related to time management, cost management,
communication, and quality and stakeholder engagement.

2PROJECT MANAGEMENT FOR DEVELOPING A PAPERLESS INTERFACE
Potential causes of success/failure
Being the IT manager I would like to identify the triggers of project success and failure.
In this paper the reasons for which theses risks are occurred all over the project expansion life
cycle. After reading the paper document different risks are identified and it is also realized that,
that the working team members are not focused to their assigned responsibilities as they are all
asking for further extension. If feasibility study is not conducted at the project initiation stage
then failure may occur. Similarly, lack of knowledge among the project team associates,
communication gaps, cultural barriers are the triggers cause project level risks. Before initiating
any project both time and budget are estimated and approved by project manager and executives.
Similarly for this project also the time and budget are preliminarily estimated (Serrador &
Turner, 2015). However, due to asking for extension in time the early estimation get exceed
which caused failure in time management.
Delay in project delivery is referred to as one of the most serious risks which require
attention of the project executive and rest team members. The engineer working for the project
was lagging enough of knowledge and skills which requires major attention. Not only this but
also, the team was failed to track the progress of the project throughout the development life
cycle period. As the team asked for additional time thus, it caused additional budget as well. The
triggers of project success and failure will help to justify the way through which project running
methodology would assist to address them.
Potential causes of project failure
It is realized that, project achievement and breakdown is dependent on performance of
the project supervisor and other working team associates. The reasons for project failure are
elaborated below: