Support After Software Deployment Discussion
Order ID:89JHGSJE83839 Style:APA/MLA/Harvard/Chicago Pages:5-10 Instructions:
Support After Software Deployment Discussion
CIS510 discussion post responses.
Respond to the colleagues posts regarding:
“Support after Software Deployment” Please respond to the following:
Your software has gone live and in in the production environment. The project gets handed over to the IT support team. Research support after software deployment. What are some of the challenges that can happen?
Have you ever been involved with a new software either in your work place or at home. Please tell us about the personal experience. If you have not been part of new software you can relate a time can when you needed help from a support team?
JS’s post states the following:Top of Form
When new software is launched and has migrated into the production environment; it is imperative that the project when provisioned to the IT support team has been thoroughly researched in terms of the supportive procedural concepts that may affect the software after its deployment. This involves the evaluation of any possible challenge (s) that may occur such as creating a speiclaized IT support team to focus on the operational and functionality of the system. If this process is not implementing effectively the organization must either than develop their own an on-going IT support team or outsource their systems vendor’s IT support department.
As a General Manager I was faced with many instances where a new software was introduced. No matter the feasibility of the system implementation in terms of successful transitional training; it made the launch difficult for many of our end-users. Those who are younger or more experienced with computers found it easy to adapt to but as with all new technologies I found that the older generation found it difficult to transition their cognitive and physical motor skills; to understand the full scope of the new processes and grasps it successfully in a timely manner. Because a company may be unaware of these set –back until the system has been launched; it requires that a company initiate a more intimate training settings so that there is very little if any interruption in operation of the system. In my case this was extremely prudent to the business and its operation requirements. The smaller training segments aid the company avoid project delays that could of lowered the software implementation, effectively. By reducing their return on their training investment; the company was able to decrease the overhead involved with estimated launch cost and eliminate any resistance affiliated with the modifications to the old system. This manual process resulted in an increase in job satisfaction, due to limited systematic frustrations with training each employee on their level and any issues with prior system maintenance and or frequent system updates.
GO’s post states the following:Top of Form
One of the major challenges to supporting a product is when to end that support. Supporting old software has its limits and is not a profitable enterprise in the long run. Companies have to juggle when to end support and focus on new versions of their software. The product price of new software is always an issue, and so is the social cost of no longer supporting older software. One solution is to set firm dates for ending support and keeping the price of new versions low. (Ghoshal, Lahiri,& Dey, 2017) One company I worked for years ago was developing new software to replace the current system in use. The new software was a complete redesign of the current system and used outside vendor software as part of the design. The company had to bring in someone from the vendor software company to help in implementing the changes. In this particular situation, because the person in question had to be onsite for multiple days, they needed short term housing. Fortunately, the parent company had its office in an apartment complex and was able to find a place. Ghoshal, A., Lahiri, A., & Dey, D. (2017). Drawing a Line in the Sand: Commitment Problem in Ending Software Support. MIS Quarterly, 41(4), 1227-10-A4. Retrieved from https://search.ebscohost.com/login.aspx?direct=true&db=bth&AN=125996712&site=eds-live&scope=site