Information System Assignment (Doc)

Added on - 21 Apr 2020

  • 17


  • 3191


  • 3


  • 0


Showing pages 1 to 4 of 17 pages
Running head: INFORMATION SYSTEMSInformation systemsName of the studentName of the UniversityAuthor Note
1INFORMATION SYSTEMSAnswer to question 1:The information and communication technology is associated to an essential part of eachorganization or business companies. This is also associated to the way the communication occursamong the various entities related to each other. In addition, the use of information systems isalso associated in providing quality and value in our lives (Kerzner, 2013). For all the developedand the developing countries, are accepting the innovations in technologies which are causingrapid changes in every emerging fields. The use of information systems is the core operations inany kinds of businesses. The spending amount for adopting this process is considered to bebillion dollars which have led to the adoption of information and communication processes incompanies and business organizations. However, in spite of the adopted practices in theinformation sector for development and efficient advancements, their applications areexperiencing failures which is the cause for concern among various developing countries as well.The need for adopting these innovations are increasing in a day a by day interval and thefailure rate of their implementation process is also increasing at the same rate (Burke, 2013). Themain reason for the failure of IT projects is mainly due to being unable to comply with the threerules for project development. These are the timely delivery, meeting of budget criteria andefficient working of them. These criteria are important and every project must meet them inorder to get an industrially approved solutions. There are various reasons for which a projectbecomes unable to meet these criteria.The first reason for a project failure is the lack of users getting involved. This reason hasbeen the cause for failure from a long time. Without the involvement of a user, people engagedin a project do not feel committed to the system and thus a project gets failed (Larson & Gray,
2INFORMATION SYSTEMS2013). For addressing this requirement, the senior management personnel and end-users of asystem should show more engagement on the project. This increases the time and the effortrequired for handling pressures which in turn increases the priorities on these projects therebyincreasing the efficiency. Thus, the senior management must support the whole process ofproject development to make it a clear priority among the personnel responsible for it.Another reason which accounts for the failures in systematic project development is thelong time scale for a project. This causes a long scheduled time table for achieving short asks andthus the availability and efficiency often reduces due to this. The main objective for a projectmust include shorter time scale which can be used cover the whole aspect of the project in a shorttime usually by dividing the key components into many (Schwalbe, 2015). Although, thisprocess of agile methodology is a much acceptable solution for project development, they aresaid to have much disadvantages as well. However, a time scale is always made by the projectmanager considering a general review of the project and not by careful evaluation. As a result theproject that is being delivered usually has short deliverables or do not meet the efficient criteria.In extreme cases, they are also delivered late due to this problem. For addressing such problems,the project manager or the senior management team must watch and review the requirements of aproject and allot a time scale effectively so that all the project criteria are met.The third reason for project failures is the lack of requirements or limited access. Due tothis problem, many times it is seen that the project developers get no access for the requirementsand usually deliver a project which is way off the charts. Additionally, it have also been reportedthat the project is developed without meeting any set criteria or any definitions (Fleming &Koppelman, 2016). These are a great cause for project failures which greatly affects a system. Inextreme cases, a business loses their relationship with their clients and leads to loss of revenue
3INFORMATION SYSTEMSmade. To address these requirements, user responsible for the project must specify the clearobjectives and the developers must also clear the criteria before proceeding with their task.The fourth reason responsible for project failures are the scope creep. A scope of aproject defines the deliverable of a project which must be present in the outcome of the project.This is the most required deliverable and must be addressed by managers as well. However, dueto changes in the scope, project outcomes become very difficult to achieve (Walker, 2015). Thisis termed as scope creep. For example, in case a company wants to build an information systemwhich will be able to add customer records or view them, the next scope gets changed to theproject being able to access customer data and send the data via online communications to thecustomers themselves, causes changes in the scope and it becomes unable to achieve. This is anexample of scope creeps. To address these solutions, the management of the project must bedone effectively and the personnel responsible for this must identify clear objectives and set cleartimescales to achieve the required changes in criteria.Another reason for the occurrence of failures in projects is the lack of control for changesin the system. Although, business is changing at a rapid rate, the need for managing the changesis a necessity. Lack of such management leads to grave amount of threats within the systemwhich is another cause for failures in project development. This causes a need for a shortduration of time scales and an approach that is phased to meet the necessary requirements(Leach, 2014). The various businesses must identify and analyze the parameters of changes interms of effects, cost and mitigations which can be referenced in the project managementlifecycles.
You’re reading a preview

To View Complete Document

Become a Desklib Library Member.
Subscribe to our plans

Download This Document