{"id":57,"date":"2015-06-29T18:24:05","date_gmt":"2015-06-29T23:24:05","guid":{"rendered":"https:\/\/iscgi.com\/?page_id=57"},"modified":"2015-08-15T05:38:22","modified_gmt":"2015-08-15T10:38:22","slug":"software-integration-problems","status":"publish","type":"page","link":"https:\/\/iscgi.com\/why-are-failures-so-common\/risks-not-identified\/software-integration-problems\/","title":{"rendered":"Software & Integration Problems"},"content":{"rendered":"

Problems with the software & integrations are not uncovered until after go-live<\/h2>\n

Despite what appears to be an easy way to avoid this risk (test the system prior to live launch), many AMS, LMS, and Websites go live before they are ready. Problems found after go-live can threaten your cash flow, customer service, productivity, reputation, and staff morale. If you flip the switch too soon, deficiencies found in the system or staff’s knowledge of how to accomplish their business processes cause everyone to operate in crisis mode, thereby putting your business at risk. Simply instructing staff to test the system prior to go-live, or relying on the vendor to do it for you, is a simplistic answer that is unlikely to keep you out of trouble. You have to look no further than the healthcare.gov website to see the disastrous impact of going live on a new untested system prematurely.<\/p>\n

How to ensure you are ready to go-live on your new AMS, LMS, or Website<\/h2>\n

Although your vendor should test their configurations prior to delivery, it is your<\/u> responsibility to conduct thorough acceptance testing prior to go-live. The Framework methodically walks you through creating a comprehensive test plan<\/strong> that covers nine<\/strong> different types of tests, from unit testing the functions in a business process, to workflow and integration testing, usability testing, performance\/load testing, data conversion reconciliation, security and penetration testing, and more. The Framework also guides staff on how to create detailed test scripts and how to document the expected results before testing begins. Templates and step-by-step instructions are provided for conducting acceptance tests and recording the results. Charts tracking the progress of the testing effort, showing the number of test scripts that passed and failed, are provided so that you can include them in your regular project status reports.<\/p>\n

\"Risks3\"Although comprehensive acceptance testing is a vital part of the solution, it is not the only<\/em> part. A thorough Readiness Assessment<\/strong> is imperative prior to live launch of a new AMS, LMS, or Website. The Framework includes a Readiness Assessment template that evaluates 60+ readiness factors within seven major categories, including product readiness, staff readiness, data\/content readiness, infrastructure, support team, and more. By using the assessment templates in the Framework along with guidance from ISCG, most clients are able to conduct a series of readiness assessments on their own. Readiness factors are evaluated using a stoplight metaphor, allowing senior management to understand the results at a glance, and to analyze the organizational impact and risks<\/strong> involved in authorizing a final go\u2011live decision. The results of the Readiness Assessment facilitate action plans that focus on those areas identified as not ready so that the proper adjustments to your project can be made prior to go-live.<\/p>\n

The Business Impact of WHEN<\/u> problems are found<\/h2>\n

in your new AMS, LMS, or Website system<\/h2>\n

\"Risks3a1\"<\/a>
\n<\/a>
\nThe Framework\u2019s Readiness Assessment<\/strong> helps you evaluate the factors that executive leadership needs to know before making the decision to go live. If the key factors show a green light, you can go live with confidence<\/strong> that your staff and new system are truly ready. If the key factors show yellow or red, you will be armed with documented knowledge as to what risks may occur upon go-live. The Framework\u2019s Readiness Assessment is a critical component in your risk mitigation strategy.<\/p>\n

\"Next\"<\/a>\"Previous\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Problems with the software & integrations are not uncovered until after go-live Despite what appears to be an easy way to avoid this risk (test the system prior to live launch), many AMS, LMS, and Websites go live before they are ready. Problems found after go-live can threaten your cash flow, customer service, productivity, reputation, […]<\/p>\n","protected":false},"author":5,"featured_media":0,"parent":20,"menu_order":20,"comment_status":"open","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"acf":[],"_links":{"self":[{"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/pages\/57"}],"collection":[{"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/comments?post=57"}],"version-history":[{"count":0,"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/pages\/57\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/pages\/20"}],"wp:attachment":[{"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/media?parent=57"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}