Cmgt 410 Riordan Manufacturing Systems Integration Project

...

Technical Requirements

1. Integrated software and applications with existing systems.

2. Systems training modules.

3. Hardware supporting new systems.

Limits and Exclusions

1. Does not include upgrades to other systems to integrate.

2. Budget limitations on hardware and software cost.

3. Overtime costs not included

4. Support from other districts costs not included.

Customer Review

Hugh McCauley, COO

Resources and Proposed Cost. The cost of the total project’s resources will be $120,000. This does not include any purchases of software or hardware. Hardware and software purchases realize expected implementation during the design phase of the project. A scheduled project date is set for anywhere from 7 months to 8 months. A meeting at the end of the project will have a lessons learned topic, which will end the HR project.

Key Stakeholders in Riordan. As with any project, the planning phase is the most important step towards beginning. The SDLC divides four general categories: Systems Planning and Selection, Systems Analysis, Systems Design, and Systems Implementations and Operations. During this time, the systems planning and selection phase, the developers, stakeholders, and managers sit down and plan exactly what they are trying to accomplish. This is the time where needs, functions, behaviors, performance, interfacing, and requirements are established. To have a successful end of project, the more it has to be thorough and detailed. Under normal SDLC circumstances, the stakeholders consist of the Organizations Leaders and the Developer’s Leaders. Due to the full overhaul of the HR department and the size of the company, there will be more stakeholders involved in this entire plan.

The first thing looked at is the hierarchy of the HR department. The director of HR will be the one to approach to gather information, because that person is the residential expert in this field. Each stakeholder is important because of the responsibility for the labor that makes the company function. It is important to avoid overlooking this aspect, because this could lead to confusion in the various jobs at Riordan. It is also important to note that web conferencing, conference calls, and joint staff meetings will need scheduling more often so that each stakeholder is present and can voice their opinion and concerns, thereby staying informed with up-to date-information. Additionally by doing this, it will save time and money, and there will not be a repeat of a meeting regarding the same subject. Communication (clear, concise and often) will be required in order for the success of the project at all times, especially during the planning phase. The preliminary information-gathering phase should start at the initial step because of the size of the project.

According to the project’s review and development, it should take 45 days to complete the functional specifications by the development team. Once the system is in place, migration of the data should take 12 days with testing to follow for 7 days. Once all the requirements of testing have been established, the training of the system shall take place and continue for 15 days so that it can train all users all over as well as China. The total time of the development and implementation process shall take up to 140 days. This will include all of the documentation as well.

Project Approach. The project must follow a series of steps and phases during the stages of production. Milestone achievement reflects achievement of future goals for each task and shall detail the resources required to achieve this goal. The collaboration and brainstorming from the members will determine the path that has the most consistency for the duration of the project. The phase of development for the project includes the Project Charter. The Project Charter contains directions and guidelines that will be the rule for the project.

Detailed testing with even more detailed notes will be beginning in this phase. During this stage, we aim to locate compatibility issues, bugs, improvements, as well as make sure every requirement meets expectations. The testing concept involves sampling small compendiums of data taken from each legacy system, cleansing and aligning the data to ensure healthy transition during the integration process. A significant milestone recognizes proof of concept in the event this method is successful. Success achieved, a continuation to extract, cleanse, and align small compendiums of data in this manner until all legacy systems integrate into one state-of-the-art technological powerhouse system for the Human Resource department. As the point of presentation of the project arrives, the first step would be rolling out the project in minimal and controlled delivery, via phased implementation and delivery within each portion of the HR office. The transition must be smooth to be successful; also, milestones settings used to reduce risk of the project. End users will be involved in this process to ensure acceptability of the user interface, thereby avoiding latent and expensive modifications. Focal points are this juncture is the evaluation of the delivered product. Every aspect monitored, all along providing the support needed for transitioning, and assuring all functionality as well as providing the modifications, if necessary. Efficiency will be the strong point and focus of this project.

Risk Mitigation Strategy. During the progression of a project, it is possible that the scope may deviate from its original boundaries, or it may even rise above the cusp outside the projects original plan. If this occurs, an evaluation distinguishes the cause from within the project. A projects trend may change and call for a need to adjust the scope slightly and yet remain acceptable in deviation standards. To assure the deviation being acceptable, the Project Manager will perform some risk reporting and inform the stakeholders the status of the project. The project manager also needs to assure everyone involved that it is an isolated incident. Issues occur in a project, which is why the best planning practices to identify and recover beforehand are important.

Issuing bi-weekly reports to the stakeholders will keep a respectable level of confidence in the team. Not only does this keep the stakeholders outlook a positive one, it also keeps everyone