A Case Study of Technology Project
The Project to be studied is an implementation of a work assignment and tracking system in an IT department in a medium sized company. The IT Department before the project was started, had undergone a management change and a reorganization due to corporate cost cutting and restructuring. The previous structure of the IT organization was teams of people that support specific applications in the system, and the business users of a particular application contacted the team assigned to their application for system enhancements and support. There was no system for managing and tracking projects and tasks, and it was left to the managers of each team to handle project prioritization, assignment and tracking. This structure was changed to a pooled resource structure where IT staff people were grouped by functional areas (such as mainframe support group, pc support group, web applications, etc). The IT structure was no longer hierarchical and the work was no longer handed down in a top down approach thus creating a need for a systematic way of managing people and tasks to function effectively.SDLC (Systems Development Life Cycle) The Life Cycle for this particular project did not exactly match the or
The functional user requirements for this project detailed all the different tasks that an IT organization performs and the information that needs to be tracked for each such as requestor, status, assigned IT person etc. One of the main requirements gathered was that of accessibility of the work flow system. Different people will be entering work requests such as business users and help desk personnel and the user interface and performance requirements for the two types would be far different. So the chosen system should have flexible interfaces and need to communicate work status and results back to the requester in a medium that is accessible company wide. Another main requirement is that the system can be implemented quickly and should be flexible enough to easily add features in the future. The four phases for this project was combined into one because of the time constraints and since it was a packaged software approach and the main components no longer needed development and testing. Most of the development involved loading tables that the package uses such as logon ids, departments, user data etc, and the customization of the user interfaces. The necessary components of Remedy were installed and hooked up with the web servers and the email system. Before final rollout, it was given a trial basis by one representative in each IT group and finalized based on the recommendations of each representative. Once the work flow system was ready, the IT staff were trained on how to use it and how work should flow through the organization. In this phase, functional user requirements are formally defined and delineate the requirements in terms of data, system performance, security, and maintainability requirements for the system. The physical characteristics of the system are designed during this phase. For this project, after reviewing the requirements, the only option that would work was an out of the box solution such as the Remedy Action Request System. Since it was already being used by the Help Desk te
Some topics in this essay:
Analysis Phase,
Project Project,
Help Desk,
Implementation Phase,
Planning Phase,
Life Cycle,
Development Phase,
AR System,
According Trepper,
System Programmers,
help desk,
business users,
ar system,
planning phase,
life cycle,
remedy ar,
system implemented,
remedy ar system,
flow system,
functional user requirements,
process management,
systems development life,
system help,
system help desk,
development life cycle,
Join now to see the rest of the essay!
Approximate Word count = 1364
Approximate Pages = 5 (250 words per page double spaced)
More Essays on A Case Study of Technology Project
Professional Papers: |
CUSTOMER SERVICES
|
|
Saved Papers
You haven't saved any papers.
|
Example Essays Home
