Phase Summary of Phase Key Deliverables Initiate During initiate, the project manager of the delivery team will kick-off the project, validate the scope, facilitate the logistic, and initiate the project plan Communication Plan Escalation Plan Timeline Schedule Project collaboration eRoom Analyze The delivery team will conduct the analysis of DOT’s requirements and define the architecture and design of the solution. The requirements include business requirements, functional requirements, and infrastructure requirements. Enterprise Foundation Definition Taxonomy) Functional Requirements Definition (use-case specific). Technical Architecture Definition (Infrastructure) Solution Design Document (SDD) Build In Build, the delivery team will actually build the proposed system. It includes the installation, development, and configuration, and testing of components and comprising the proposed solution. Out-of-the-box Documentum software installed Configured Documentum environment with taxonomy and library services Configured retention policies Migrated content from FileNet Imaging Services to Documentum Migration of Computer Output to Laser Disc (COLD) data Utility to ingest content from Fileshare
Closeout: $-0- Customer Acceptance, Transition to Operations 12/31/2014 5.4 Project Team 5.4.1 Project Team Organizational Structure 5.4.2 IT Manager Oversight of Project Oakeley IT Team member Work with Vendor David Coriz IT Records Management Team Member Work with vendor Jeff Woodman IT Web SYS ADMIN Work with vendor Gabriel Vigil IT Records Management 5.5 STAFF PLANNING AND ACQUISITION 5.5.1 Role Responsibilities
of scope to the project and if scope does change, it is done knowing the impact to the project. The third process for quality management is the risk management plan, which measures, mitigates and includes contingency plans for each risk. The project team will also create lessons learned at the end of each phase of the project. These lessons learned will be incorporated into the next phase of the project and be part of the project library that will be available for future projects to use. All of these processes combined will create a product that has quality that is built in not tested in after the fact. This will provide an environment that maximizes opportunities to control quality. 6.7.1 No. Quality Standard Tracking Tool or Measure 1 Project phase is completed by the established finish date. Project Schedule Project Status 2 Project is completed within budget. Project Charter Project Status 3 Quarterly project reviews show contractors deliver requirements specified in the contract by due or pay penalties. Vendor Contract Customer Acceptance 4 Project issues are resolved and documented within 10 calendar days of identification or extensions are justified. Issues Tracking 5 Project will be completed based on the original project scope and approved scope changes. Project Charter Project Plan Control Change Request 6.7.2 AND ASSESSMENTS Review Type Quality Standard Tools Reviewer Reports Requirements Project is completed within budget. Contract deliverables Project Manager Produce by vendor Plans All must meet contract deliverables Scope of work by vendor Project Manager Produce by vendor Milestones Project phase is completed by the established finish date. Contract Deliverables Project Manager Milestone checklist from vendor Testing Execution of User Acceptance Testing (UAT). System Test Scripts procedure. for User Acceptance Testing (UAT). Project Manager Produced by Vendor