Riordan Manufacturing Key Stakeholders Essay Example for Free

Riordan Manufacturing Key Stakeholders Essay There are several stakeholders at Riordan Manufacturing to gather requirements from to provide a clear picture of the final project. The first stakeholder to gain input would come from the Chief Operations Officer, he was the requestor of the system upgrade, is responsible for the budget, which includes payroll. The Chief Legal Officer oversees the legal aspects of the human resources programs. The individual human resources managers within the individual facilities are the stakeholders who recruit and handle benefits for employees. Each facility has an accountant that oversees payroll and bonuses as well as the payroll specialist (Apollo, 2011). Information-gathering techniques and systems analysis tools Interviews will be the first form of information gathering that will be used. Interviews and survey forms are a very effective way to gather information. Through the user’s impressions, personal experiences, task related ideas, and attitudes on the current system can give a baseline for needs. The interviews will aid in forming a definition of the scope of the system requirements. Interviews will also allow the system analyst to understand what boundaries by which to take into consideration (Havelka and Lee, April 25, 2002). A checklist will be prepared prior to any interviews. It is important to prepare an interview guide so that interviewer knows what order to ask questions and the amount of time that should be spent on each area of the interview. The interview guide will include open-ended questions that will allow for follow-up discussions. The guide can also double as an outline for a summary of what comes out of the interviews (Havelka and Lee, April 25, 2002). The second information gathering technique will be to observe the stakeholders. Many managers plan their day without taking into account interruptions from phone calls or meetings. During the interview stage, an employee may state he or she is busy with e-mails throughout the day, but by observing the employee, it could be determined that he or she receives minimal e-mails. Observing behavioral measures allow for a more accurate reflection of current system operations and future requirements (Havelka and Lee, April 25, 2002). Gathering and analyzing procedures and other company documents is the third information gathering technique. Close examination of the systems and organizational documentation is another way to determining system requirements. This can lead to discovering defined details relating to current systems and the organizations they support. By analyzing documentation, the analyst can identify problems with existing systems, such as redundant steps or incomplete information. Analyzing allows for determining organizational direction that can influence information systems requirements, such as attempting to link corporate managers to local managers. Analyzing also allows for the identification of titles and names of important individuals who have an interest to the current existing systems (Havelka and Lee, April 25, 2002). Key factors too help ensure the information required for the project is gathered successfully. The first step in the information system development or modification process is to gather requirements. Information system requirements are frequently unreliable and insufficient. The reasons for failure usually are at the fault of management and people involved. Not necessary due to technology but more so due with improper planning (Havelka and Lee, April 25, 2002). Utilizing JAD (Joint Application Design) technique will improve the determining systems requirement process. JAD is a structured process where analysts, managers, and, users work together for several days in a series of intensive meetings to review system requirements. Organizations gather affected individuals that are affected by information systems together to agree on system requirements and design details (Valacich, 2012). A good facilitator should be able to keep the focus of stakeholders and the IT (Information Technology) department participants on the goal of specifying the system requirements. Another option managers have to improve interaction is the care in assignment of members to the project team. The selection of stakeholders and IT personnel with personal interest in the new system improves the chances for success (Havelka and Lee, April 25, 2002). Another factor to ensure success is to train the IT personnel on the system’s applications and processes. How well the IT personnel understand the systems is extremely relevant to the success of system implementation. The involvement of IT personnel, who have knowledge regarding the application requirements, increases the ability of the team to correctly and quickly specify the requirements. Experienced IT personnel on a team help ensure others understand terminology and have more of an understanding of the stakeholders needs (Havelka and Lee, April 25, 2002). Project scope and Why it is Important Project scope defines the goals of the project and the budget of both time and money that has been allocated to achieve the objectives. For the best results to be achieved, both the definition and the allocated budget must be precise and detailed. A good process scope document will define specifically the tasks to be completed or the delivered results. The project scope is important because it will define the specific date for which the deliverables will be due and list the allocated budget for them. The project scope will also list specific items not part of the project scope and are excluded from the work to be delivered (Reh, 2013). Areas of project feasibility that are examined in the analysis phase of the SCLC Project feasibility is examined during the systems analysis and requirements definition phase of the SCLC. This phase involves the setting of specific project goals, which defines the functions and operations, to be included in the project to achieve completion of the project. The project goals should be based on the analysis of the stakeholders information needs. This phase can also be called the feasibility study because it also defines personnel assignments, funds, schedule, goal dates, performances, and interfaces (India, May 18, 2012). References Apollo Group, Inc. (2011). Riordan Manufacturing. Retrieved from BSA/375 course. Havelka, D. and Lee, S (April 25, 2002). Critical Success Factors for Information Requirements Gathering. Retrieved from http://www.techrepublic.com/article/critical-success-factors- for-information-requirements-gathering/1060122 Reh, J. (2013). Project Scope. Retrieved from http://management.about.com/od/PMterms/g/Project-Scope.htm Rose India (May 18, 2012). System Development Life Cycle. Retrieved from www.roseindia.net Valacich, J. S., George, J. F., Hoffer, J. A. (2012). Essentials of systems analysis and design (5th ed.). Upper Saddle River, NJ: Pearson Education