MVD and FDB Business Owners Team Members Provide subject matter expertise for MVD and FDB business requirements Participate in workgroups and status meetings to determine best course of action, options, and alternatives Review ITC PCC documentation for certification Participate in developing Driver Reengineering selection criteria Make recommendations to Driver Reengineering Project Director concerning the project deliverables Assist with project coordination and issues escalation is necessary Review Vendor deliverables and participate in test walk-through Approve and sign off on project documentation Work closely with Project Director to create an approved, published Driver Reengineering framework IT Team Members Participate in Hosting Strategy Development Support installation of hardware and technology infrastructure Develop applications as required Perform installation of hardware and software Configure hardware and software IT Specialists System Administrators, System Experts and Developers Provide IT subject matter expertise Work with Project Director to determine hardware, software, network and technical requirements. Work with Project Director to define technical system interface requirements. Provide IT perspective and guidance for technology issues Vendor(s) Ensure compliance with the Contract and the approved work plan. Develop and submit all deliverables as required by the Contract. Meet the project schedule and milestones as defined in the Work Plan and the Contract. List the team members, their role, responsibility and functional manager. Make sure to include a comprehensive listing including those from the organization managing the project, business members involved to ensure business objectives are met and the vendor members that may have a specific role. Cabinet Secretary Program Financial Responsibility Rick Homans Taxation and Revenue Department (TRD) Deputy Cabinet Secretary Program Financial Responsibility Marilyn Hill Taxation and Revenue Department (TRD) MVD Director Program Administration Responsibility Michael Sandoval TRD, Vehicle Division MVD Deputy Director Program Administration Responsibility Alicia Ortiz TRD, Motor Vehicle Division
MVD Deputy Director Program Administration Responsibility Paul Montoya TRD, Motor Vehicle Division Chief Information Officer IT Infrastructure Joel Matek TRD, Information Technology Division IT Manager MVD Applications Development Lee Baca TRD, Information Technology Division Bureau MVD Policy and Procedure Mac Lewis TRD, Motor Vehicle Division Bureau MVD Field Office Operations Toby Williams TRD, Motor Vehicle Division Bureau Chief MVD Office Operations Ortiz TRD, Motor Vehicle Division Training Manager MVD Training To Be Determined TRD, Vehicle Division Application Developer, Database Administration, System Administration Technical Support of Systems TRD IT Technology And System Support Technology and System Support 5.5 PLANNING AND ACQUISITION Complete the chart below identifying the project team members and details concerning their project commitment. Project staff should include State, Contract, Customer (Business Owner), or Vendor team members. Planning and Resource Acquisition is estimated only, and will not be determined until after RFP award. 5.5.1 Project staff requirements are estimated only, and will not be determined until after RFP award.
3 Project does not exceed budget. Project budget 4 System is secure, operable and stable UAT results 5 Staff is adequately trained User lessons learned 6 Collecting fees and revenue distributions are accurate and produced in a timely manner Independent Audit by Tax Fraud Division 7 Field offices operate more efficiently leading to improved customer satisfaction MVD Bureau chiefs comparing wait-times before MVD Driver Reengineering, and after MVD Driver Reengineering 8 Driver legacy data is converted accurately and efficiently UAT results 9 Driver and Distribution COTS solution integrates easily and accurately with POS or replaces POS functionality without losing existing POS capabilities and efficiencies UAT results 10 Mainframe costs are reduced as legacy Driver and Distribution functionality is successfully implemented in MVD Driver Reengineering solution Project Director comparing mainframe costs before MVD Driver Reengineering, and after MVD Driver Reengineering 6.7.2 AND ASSESSMENTS Review Type Quality Standard Tools Reviewer Reports Requirements Plans Milestones
A tool used to indicate the planned dates, dependencies, and assigned resources for performing activities and for meeting milestones. Software products such as ABT’s Workbench and Microsoft Project are tools used to develop project schedules. Project Scope The work that must be done to deliver a product with the specified features and functions. Project Sponsor The individual that provides the primary sponsorship for an approved project. This individual will play a key role in securing funding, negotiating for resources, facilitating resolution of critical organizational issues, and approving key project deliverables. Quality The degree to which a system, component, or process meets specified requirements. The degree to which a system, component, or process meets customer or user needs or expectations. [IEEE-STD-610] Quality Management The process of monitoring specific project results to determine id they comply with relevant standards and identifying ways to eliminate causes of product non-compliance. Risk Possibility of suffering loss. Risk Management An approach to problem analysis, which weighs risk in a situation by using risk probabilities to give a more accurate understanding of, the risks involved. Risk Management includes risk identification, analysis, prioritization, and control. Risk mitigation seeks to reduce the probability and/ or impact of a risk to below an acceptable threshold. Risk Management Plan The collection of that describes the Risk Management activities to be performed on a project. Scope Change Any change to the project A scope change almost always requires an adjustment to the project cost or schedule. Software Life Cycle The period of time that begins when a software product is conceived and ends when the software is no longer available for use. The Software Life Cycle typically includes a concept phase, requirements phase, design phase, implementation phase, test phase, installation, and checkout phase, operation and maintenance phase, and, sometimes, retirement phase. Stakeholder Individuals and organizations that are actively involved in the project, or whose interests may be positively or negatively affected as a result of project execution or project completion. They may also exert influence over the project and its results.