project due to the project having followed industry standards. It will be non-proprietary software that RLD owns and fully controls, unlike the current Accela implementation which is proprietary black box technology and requires Accela engineers to make programming changes. If neither of these were feasible we would need to turn to one of the other alternatives listed. Vendor abandonment (payment L/M Payment gateway providers are page provider): If Wells numerous and our financial service Fargo/CyberSource, our payment provider would likely have a new page provider, were to remove or recommended payment page host. significantly alter their hosted RLD IT would likely be able to make payment page service then the small required changes to the additional development work may application to accommodate a be required to adapt to new different payment page host given provider or to the page changes. that most of the initial integration has been completed. PCI compliance standard changes: M/M RLD IT will need to keep a close Security standards are, by their watch on how PCI compliance very nature, subject to ongoing requirements and items change over change. If the PCI compliance time. This time estimate is built into requirements were to change in a our maintenance hours estimations. significant way then additional Usually, these standards give work and\or funding would be sufficient lead time to make changes needed to adapt to the change. in time to remain compliant. 1.6.2 RISK MITIGATION PLAN & IMPACT Inadequate or incomplete L/H Project management would occur both requirements gathering: If project inside the contracted organization and requirements are not fully from RLD IT with cross-checking understood or updated early in the occurring between each organization process the final product may not throughout the requirements gathering address the true needs of the and design phases. This has worked project or additional time or well in past endeavors.
project due to the project having followed industry standards. It will be non-proprietary software that RLD owns and fully controls, unlike the current Accela implementation which is proprietary black box technology and requires Accela engineers to make programming changes. If neither of these were feasible we would need to turn to one of the other alternatives listed. Vendor abandonment (payment page provider): If Wells Fargo/CyberSource, our payment page provider, were to remove or significantly alter their hosted payment page service then additional development work may be required to adapt to new provider or to the page changes. L/M Payment gateway providers are numerous and our financial service provider would likely have a new recommended payment page host. RLD IT would likely be able to make the small required changes to the application to accommodate a different payment page host given that most of the initial integration has been completed. PCI compliance standard changes: Security standards are, by their very nature, subject to ongoing change. If the PCI compliance requirements were to change in a significant way then additional work and\or funding would be needed to adapt to the change. M/M RLD IT will need to keep a close watch on how PCI compliance requirements and items change over time. This time estimate is built into our maintenance hours estimations. Usually, these standards give sufficient lead time to make changes in time to remain compliant. 1.6.2 RISK & IMPACT MITIGATION PLAN Inadequate or incomplete requirements gathering: If project requirements are not fully understood or updated early in the process the final product may not address the true needs of the project or additional time or L/H Project management would occur both inside the contracted organization and from RLD IT with cross-checking occurring between each organization throughout the requirements gathering and design phases. This has worked well in past endeavors.
RLD-Accela%20Replacement%20Project%20Managment%20Plan.docx