Vickie Evans Project Manager, Lead SME – MVD TRD, Motor Vehicle Division Bureau Chief Loretta Silva Project Manager – ITD CSW Enterprises, LLC Contract PM Sailam Vasudevan Technical and Business Knowledge TRD, Information Technology Division IT Business Analyst Doug Torhan AAMVA Technical Knowledge DoIT, Information Systems Division Contract Developer Donna Intermont Business Knowledge Input – CDLIS TRD, Motor Vehicle Division Subject Matter Expert Darren Cordova Business Knowledge - CDLIS TRD, Motor Vehicle Division Subject Matter Expert Nichole Armijo Business Knowledge Input – Medical Certificate TRD, Motor Vehicle Division Subject Matter Expert Raul Alvarez Business Knowledge Input TRD, Motor Vehicle Division Subject Matter Expert Connie Torres Business Knowledge Input TRD, Motor Vehicle Division Subject Matter Expert Mac Lewis Policies and Procedures TRD, Motor Vehicle Division Bureau Chief Julia Belles Legal Interpretation TRD, Services Bureau Attorney TRD IT Technology and System Support Technical Support of Systems TRD, Information Technology Division MVD Dev, Database Admin, Support, Operations To Be Determined MVD Training TRD, Motor Vehicle Division Training Manager 2.2 Project Governance Structure 2.2.1 –
4.2.2.5 User Acceptance Testing Perform UAT for C-Mod changes Run test scripts, document results, and accept test results for C-Mod changes, ensuring accuracy and completeness. Test scripts and results for: Name Expansion Ten-Year History Check/Driver License Number Survey Patriot Act Medical Certificate Per Se Passenger 16+
4.2.2.6 AAMVA Casual and Structured Testing Perform Casual and Structured Testing to obtain AAMVA certification of changes. Work closely with to test all aspects of each C-Mod component, ensuring accuracy and completeness. certification for: Name Expansion Ten-Year History Check/Driver License Number Survey Patriot Act Medical Certificate Admin Per Se Passenger 16+ 4.2.2.7 User Training Train users on C-Mod changes. Conduct user training of MVD2.0 and mainframe changes using a approach prior to implementation in production. Deliver C-Mod training to MVD personnel. Trainer
5.3 Costs estimates are the costs applied to an activity in a project by assigning resources with associated rates or fees. Resources can include equipment, material, technology, processing cycles, or people. The total cost is critical and should be consistent with the proposal; include breakdowns as needed. Match these cost estimates with the actual billed amounts. Use an appropriate format for the project size and customer requirements (e.g., by WBS, milestone, or deliverable). Identifier Work Package or Budget Category Cost 4.2.2.1 Project Management $157,932 4.2.2.2 IV&V $72,520 4.2.2.3 Requirements Specifications $96,004 4.2.2.4 Design, Coding and Unit Testing $890,060 4.2.2.5 User Acceptance Testing $101,807 4.2.2.6 AAMVA Casual and Structured Testing $54,687 4.2.2.7 User Training $88,409 4.2.2.8 Implementation $12,009 TOTALS $1,473,430 5.4 5.4.1 The C-Mod project team is comprised of MVD business subject matter experts, ITD technical experts, and contract personnel (PM, IV&V, and developers). The core members of the project team are co-located in the ITD area of the Joseph Montoya building. Co-location facilitates ongoing day-to-day interaction and collaboration. The Technical Project Manager is the lead project manager.
IT Team Members and contract developers Participate in project meetings and activities Design and implement database changes as required Design and develop application changes as required Participate in UAT Participate in User Training Participate in Implementation Provide IT subject matter expertise Work with Project Manager to determine technical requirements Work with Project Manager to define technical system interface requirements Provide IT perspective and guidance for technology issues The table below summarizes the roles and responsibilities of each of the team members. Cabinet Secretary Program Financial Responsibility Demesia Padilla Taxation and Revenue Department (TRD) Deputy Cabinet Secretary Program Financial Responsibility John Monforte Taxation and Revenue Department (TRD) MVD Director Program Administration Responsibility Keith Perry 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 Greg Saunders TRD, Information Technology Division
IT Manager MVD Applications Development Lee Baca TRD, Information Technology Division Technical Project Manager Lead Project Manager Loretta Silva Contract Project Management Business Project Manager/Lead SME MVD Project Manager Vickie Evans TRD, Motor Vehicle Division Driver SME MVD Requirements Specifications Connie Torres TRD, Motor Vehicle Division Bureau Chief MVD Policy and Procedure Mac Lewis TRD, Motor Vehicle Division CDL SME MVD Commercial Driver License Bureau Darren Cordova TRD, Motor Vehicle Division Medical Certificate SME MVD Commercial Driver License Bureau Nichole Armijo TRD, Motor Vehicle Division Business Knowledge Input MVD Special Projects Manager Raul Alvarez, Jr. TRD, Motor Vehicle Division Legal Interpretation TRD Services Bureau Belles TRD, Office of the Secretary TRD IT Technology and System Support Technology Support of Systems Jacque Geoffrion Chris Hollis Larry Vigil TRD, Information Technology Division User Training MVD Training TBD TRD, Motor Vehicle Division 5.5 STAFF 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 5.5.1
6.5.1 Description Target Audience Delivery Method Frequency Responsible Party Standard MVD C-Mod Project Status Meeting To discuss project status with the TRD CIO TRD CIO Face-to-Face Weekly Technical Project Manager Recurring meetings are scheduled through Outlook Uses standard format MVD C-Mod Team Lead Status Meeting Regularly scheduled meetings: To discuss project activities, progress, issues and results of measurement and analysis activities. Event driven: When new requirements are existing requirements are changed, etc. Meeting attendees (PMs, BA,Team Leads) Meeting minutes are stored in the Project Repository Face-to-Face Weekly (Specify days and times) Business Project Manager (contributes to agenda) Technical Project Manager (owns meeting notice; plans agenda topics) Business Analyst (contributes to agenda) Recurring meetings are scheduled through Outlook Uses standard format An agenda is distributed in advance. MVD DRIVE Steering Committee This formal meeting addresses the accomplishments and results of all MVD projects. Meeting Attendees (PMs, TRD CIO, MVD Director, MVD Deputy) Face-to-Face Bi-weekly Technical Project Manager Recurring meetings are scheduled through Outlook Uses standard format DoIT MVD Reengineering Project Status To describe the status of the project to DoIT DoIT Word Document Email Monthly Technical Project Manager Follows DoIT Standard
MVD C-Mod Change Control Board (CCB) Meeting Review, evaluate, approve or reject, and prioritize change requests. Group approved change requests into releases. Attendees (PMs, BA, Team Leads as needed) Meeting minutes are stored in the Project Repository Group Meeting or conference call As needed (Specify days and times) Business Project Manager Meetings are scheduled through Outlook as needed. An agenda is distributed in advance. Issue Tracking and Escalation To provide a framework for documenting and tracking issues to closure and escalating long-standing or critical issues for senior leadership attention. Captured and stored in the Project Repository Project Repository E-mail, conference call or in person Whenever an arises or needs management involvement for resolution. Project Managers External Issue Resolution and Escalation Procedure
Testing Test Execution Percentage by Type A metric to indicate the percentage of tests executed by use case and subsystem. The status of testing efforts and a software quality indicator. Testing Percentage of Test Cases Passed An indicator to show the pass percentage of test scenarios and test cases Testing Number of Defects Found by Inspection (DFI) An indicator to show how many defects the customer has found through inspection of the software 6.7 QUALITY AND CONTROL Quality Management includes the processes required to ensure that the project will satisfy the needs for which it was undertaken. It includes all activities of the overall management function that determine the quality policy, objectives, quality assurance, quality control, and quality improvement, within the quality system. 6.7.1 Quality standards are defined to support the acceptance criteria for each deliverable. No. Quality Standard Tracking Tool or Measure 1 Deliverables conform to style and grammar standards? Review of deliverables 2 Are project status reports accurate and completed on time? Agency-approved Contractor Status Report Template, Transmittals, Status Log 3 Are project issues being handled within appropriate timeframes and being escalated as appropriate (avoiding stale issues)? Issues Log, Status Meeting Minutes 4 Are risks reviewed regularly with mitigation plans developed for high impact/probable risks? Risk Log, Status Meeting Minutes 5 Is the project schedule current on the progress of project activities? Project Schedule, Status Meeting Minutes
including the planning of CM, configuration identification, configuration control, CM reporting, and baseline verification. Configuration Management will be applied across the life of the project to provide the appropriate level of control for all project configuration items. Each of these groups, listed below, consist of formally controlled configuration items (CIs). Changes to these formally controlled items are managed via change control: Statement of Work Requirements Documentation User Acceptance Testing Approach and Documentation AAMVA Casual and Structured Testing Approach and Documentation User Training Approach and Documentation The project will use Microsoft Visual Source Safe (VSS) for source code configuration management. All configuration are controlled within the repository using labels to manage the baselines. The versioning of Configuration Items (CIs) is handled using the native versioning within VSS and the integrity of the data is maintained through the implementation of access controls to prevent unauthorized changes. File locking is used to prevent multiple from updating the same file in parallel. Procedures have been implemented to ensure that only exclusively locked files are read-write in a user’s working area, unlocked files are stored as read-only. The native operating system standards prevent users from creating and/or adding files with duplicate file names to the same location. 6.8.1 For each deliverable, the document’s title, completion date, and version will be included on the cover page. Documents will also maintain a Revision History to record major changes and updates to each deliverable. The following versioning for document deliverables will be followed: Versioning Major Version Definition 1.X Initial Draft 2.X Review Ready Draft 3.0 Accepted Deliverable revisions also will be reflected with changes to the numbers to the right of the decimal.