Suny Old Westbury RESPOND TO BOTH OF THE PEER QUESTION(S)

Description

Prompt: In responding to your peers, select one of the post implementation items in their post and provide a failure scenario for the post implementation item and a possible resolution for the runners as well as management, assuming the item fails to resolve the problem. For example, an implementation item can be a checkpoint in the first five days in order to ensure runners can reset passwords. A failure scenario may be that runners that had logins created prior to the production going live will be unable to reset their passwords. Assuming there is an issue where runners are unable to reset passwords, management can resolve the issue. However, management must resolve the issue by approving the database team to run a script to reset all user IDs with create dates, prior to going live.

PEER POST # 1

“Post-implementation evaluation An assessment of the overall quality of the information system. The evaluation verifies that the new system meets specified requirements, complies with user objectives, and achieves the anticipated benefits.” (Tilley, 2016)

Five days: Was the project launched as planned? Were there any delays? Users should have full use of the app, sign on, account information, and scheduled or registered races showing correctly. If there are issues, users can provide feedback through the app. “A project constraint is any limitation that can affect a project’s ability to be completed successfully.” (Schwartz, 2024) This process also examines time, scope, cost, and risk constraints.

Four weeks: Any issues identified during the first five days should have been addressed and fixed during this timeframe. Users should now be able to view their statistics and create reports for previous marathons accurately. A gap analysis should be conducted, how did the projected plan differ from the actual launch? “A cost-benefit analysis can determine if the project’s benefits outweigh its costs.” (Schwartz, 2024) A cost-benefit analysis should also be conducted during this time frame. Was the project cost more or less than the actual cost? Also, comparing actual cost to estimated costs would be beneficial during the four-week post-implementation.

Six months: Detailed reports for all marathons completed should be available now, and runners’ information should be correct. A lesson-learned document should be created to assess what worked and what should not be utilized for future projects. A post-implementation review report is a more detailed report that should be made available to all stakeholders for future projects.

PEER POST # 2

First Five Days: During this period of time, user training needs to be completed as a part of the initial rollout exposure of users to the new system. FAQs are a great resource to outline during the training. The data that has been collected prior to the system implementation and afterwards needs to be verified to ensure a seamless experience for the users when receiving future reports. This is also when customer support is vital to success of the system. It should be made a top priority during this phase.

First Four Weeks: During this time, customer support will still be provided but perhaps, it can be relaxed somewhat after going through the first week of user exposure. Support requests will still be on-going, but it shouldn’t be as frequent. This is also the time where any system issues that were experienced or encountered should be fixed, or at a minimum, be worked on. Some of the issues brought up could take some time to fix which would result in longer maintenance of the system. Lastly, in general terms of the system, data and controls monitoring should continue.

First Six Months: This timeframe is intended for user performance reporting. An individual should be able to login to the system and view a breakdown of their performance by race and as a cumulative summary. The continuation of system monitoring should be evident. Not only should suggested enhancements be looked at for implementation during this period, but things like user access monitoring and validation should be done to ensure that unless someone has administrative access, they should only be able to see their individual performance evaluations and reports. Customer support is still evident during this time, but it should be even less during this time than what it was during the initial week or month – a gradual decrease in support.