There was no system for managing and tracking projects and tasks, and it was left to the managers of each team to handle project parameterization, 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.
OSDL (Systems Development Life Cycle) The Life Cycle for this particular project did not exactly match the order of the phases as described in the Systems Development Life Cycle concept. Because of the immediate reorganization of the IT organization, current projects encountered delays and the IT procedures and tasks were disrupted. This prompted a need for a quick reshuffling of work between the new groups and a quick and dirty way to manage the work at hand and Incoming work until a better system Is Implemented.
Inhalation The initiation of a system (or project) begins when a business need or opportunity is identified. This happened for this project when a CIO was appointed to head the new IT organization and was asked to reduce head count by pooling the resources while at the same time still provide timely and effective service to the business users of the IT systems and applications. System Concept Development Phase In this phase of OSDL, the business need has been approved and the approaches for accomplishing the concept are reviewed for feasibility and appropriateness.
Several approaches were considered for tackling the problem In the IT department. The first approach was an Excel spreadsheet to list all IT personnel and their assigned tasks house developed web based system was also considered and was in fact implemented but was cancelled since it was not flexible enough to handle the different tasks of the different IT groupings and the different sources of work requests. The last approach was either to buy an existing package that would fit the requirements and customize it for the IT organization’s structure and procedures or develop one in-house.
Planning Phase In the planning phase, the concept/approach is further developed to describe how he business will operate once the approved system is implemented, and to define project resources, activities, schedules, tools, and reviews to ensure the products and lord services provide the required capability on-time and within budget. The planning phase for this particular project was being done while simple solutions were being used and implemented since there were time constraints and something had to be in place right away.
A team was assembled to look into existing applications within the company or packages out in the market that would fit the acquirement and assess its flexibility and long term viability for the organization. That team also had to come up with a process flow of how work will be handled in the new IT structure to help in the use of the short-term solutions and to help in finding a long-term solution. Finally, two long term approaches were proposed.
One was that of customizing the packaged software that was currently being used by the Help Desk to track PC and Mainframe work requests for PC Technicians and Mainframe System Programmers, which was from a company called Remedy. The other was to develop a ark flow system in-house. Requirements Analysis Phase 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 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 requester, 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 physical characteristics of the system are designed during this phase. For this reject, 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 team, it has already proven itself as a flexible and reliable system to use. As a help desk software it allows entry of work request, assigns work, allows a way to log the progress of a request and stores all the history regarding a request. Design was simply a matter of finding out the customizable options and features in Remedy and designing it for the different IT groups formed.
Since help desk work was different as compared to application development work, two type of request were designed and one was for support/problems and one was an enhancement to the system or major project that have subtasks and involved lots of people with different roles and responsibilities. For the IT staff a client server platform was needed for faster execution, and for accessibility and ease of use, a simple web-based interface was designed for the business users since they don’t need to see too much detail.
Since company wide communications was done through mail, work assignment, status and results need to be communicated through this medium. Development, Integration , Test and Implementation Phase 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 roll, 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. Conclusion The project as a whole went through a couple of cycles of the OSDL due to different implementations.