RLD PROJECT MANAGEMENT PLAN (PMP) – RLD RLD – RLD MHD – MHD RLD LPG – LPG RLD CMS – CMS RLD PRM – PRM RLD CIO/IT – RLD – RLD 23, 2018 5, 2018 1.1 JESUS CARRASCO, BUREAU CHIEF CLAY BAILEY, BUREAU AMANDA ROYBAL, BUREAU RICHARD LUCERO, BUREAU PROJECT
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.
Training 4.2.1 Technical Strategy for Configuration is listed in detail in the ANM Statement of Work document. 4.2.2 Product Deliverables are work products or artifacts that are driven by the product management methodology requirements and standard project management practices regardless of the product requirements of the project. 4.2.2.1 Permitting Application Design Description – Design of Permitting Application based on 10 Permit Types Deliverable Acceptance Criteria - defined understanding of the system design for permitting application. Application Design Document with Information from Workshops for 10 Permit Types and Go-Live Plan for one Permit Type. Standards for Content and Format - Understandable to key stakeholders Quality Review - Key Stakeholders accept it. 4.2.2.2 Permitting Application Description - One Permit Type Active in Production Environment of Permitting Application Deliverable Acceptance Criteria - Application Delivered and Active in Production Environment for One Permit Type. Data Migration (or Integration) for the one permit type from Accela to Salesforce. Integrations for Document Management, Credit Cards and Geo Location Completed. Standards for Content and Format – Design Document Quality Review – User Acceptance Criteria 4.2.3 1 Permitting Application Design Martin Romero Jesus Carrasco Michelle Langehennig Fabio Mir 2 Permitting Application Martin Romero PRODUCT
Executive Sponsor Ensure project funding. Approve any changes to project plan or scope. Communicate with Project Manager the status of project. Mike Unthank Cabinet Secretary Business Owners Part of the business requirements gathering and verifying that the progress is headed in an acceptable direction. Martin Romero Jesus Carrasco Clay Bailey Amanda Roybal Richard Lucero Division Directors User Acceptance Team Formal acceptance of project deliverables. TBD Cross-Functional Operations Team Team dedicated to ensuring testing and project is moving forward efficiently. be managers of internal users to encourage their staff to complete their user acceptance testing TBD Cross-Functional Application Support Team Internal IT Applications Developers Chuck Slocter Amanda Urioste Mir Applications Development IT Project Management Vendor Team Team of Vendors implementing Salesforce Salesforce ANM Cross-Functional, representing application development, project management and training 5.5 STAFF PLANNING AND ACQUISITION 5.5.1 Resource Cost Estimate Estimated Hours Availability Set Work Product/Deliverable
budget reporting to DoIT will be managed by the IT Project Manager and verified by the Business Owners and Project Manager. 6.5 Communication planning involves determining the information and communication needs of the stakeholders, executive sponsors, project team and others as needed. The communication plan needs to address who needs what information, when they will need it, how it will be given to them, and by whom. The complexity of the project may require a separate communication plan; however a high level summary of that plan will need to be included here and a reference made to the appropriate Appendix. 6.5.1 Communication Type Objective of Communication Medium Frequency Audience Deliverable Initial Logistical Kickoff Meeting Introduce the project team and the project. Review project objectives and management approach. - Conference Call Once - Project Team Vendor Project Manager - Meeting Minutes - PMP - Issue tracking system & other documentation templates as needed Business Analysis & Project Kickoff In-depth review of business processes & needs across all stakeholders. Formal project kickoff across full project team. - Face to Face Once - Project Sponsor - Project Team - Stakeholders Vendor Project Manager - Meeting Minutes - Baseline project schedule - Updated PMP Project Team Meetings Review status of the project with the team. - Face to Face - Conference Call Bi-Weekly - Project Team Project Managers - Meeting Minutes - Updated Project Schedule & issue/risk log IT Project Reports Report the status of the project including activities, progress, and issues. - Email Bi-Weekly Monthly (ESC Report) - Business Owner - IT Leadership IT Project Manager - Project Status Report ESC Project Status Reports Report the status of the project including activities, progress, costs and issues. Conference call and email Monthly - Project Sponsor - Project Team Business Project Manager - Project Status Report - Project Schedule