Appendix_G-_Project_Management.docx

Appendix G: Project Management

Project Management Project and Implementation Approach Methodology The State expects the successful responder to implement strong project management methodology practices and implementation methodology practices that will enable the responder to deliver the OMS within established project management parameters (cost, budget, scope, schedule), and quality expectations that also meets the State’s intended benefits/outcomes associated with OMS.

Stakeholder Collaboration Each process affects individuals and entities inside and outside the State in unique ways. It is important to plan an engagement and collaboration strategy that will promote effective, efficient development and implementation. The table below identifies some key Program stakeholder entities and a brief description of their role:

Project Planning Project Planning includes all activities required to create and develop project planning documents with input and agreement from all stakeholders. The primary planning document is the Project Management Plan.

A detailed Project Management Plan will be developed by the successful Responder in conjunction the State at a level of detail sufficient to serve as a baseline for measuring performance in terms of schedule, quality, and cost.

A sample outline of the expected Project Planning Deliverables is provided below:

I. Project Management

a. Project Organization

b. Roles and Responsibilities

c. Stakeholder Identification and Engagement

d. Project Deliverables & Receivables

e. Customer Furnished Equipment

f. Hardware/Software Acquisition Inventory

g. Supplier/Subcontractor Management

h. Project Communication (Ongoing/Regular and Event Based)

i. Security and Proprietary/Protected Data Considerations

j. Risks and Issues Management

k. Knowledge Management

l. Business Continuity Plan

m. Cutover, Acceptance Criteria, and Stage Gates

n. Monitoring and Incident Management Plan

o. Qualifications II. Technical Approach

a. Implementation Methodology

b. Technical Plan and Documentation Summary

i. Quality Management Plan (including Quality Planning, Control and Assurance activities and artifacts)

ii. Configuration Management Plan

iii. System Administration Manual

iv. Software Test Plan

v. User Manuals

c. Systems Development Approach

i. Agile/SDLC Model

ii. COTS Configuration Disciplines

iii. Custom Development Disciplines (by exception)

iv. Technical Computing Environments (Dev., Test, Stage, Prod)

d. Technical Management Activities

i. Design and Solution Configuration Artifacts

ii. Requirements Traceability Matrix

iii. Interface Design and Management

iv. Data Migration Management

v. Formal Technical Reviews and Quality Control Gates I. Project Planning Review (PPR) II. Requirements & Design Review (RDR) III. Configuration & Build Review (CBR) IV. Test Readiness Review (TRR) V. User Acceptance Test (UAT)

e. Proof of Concept (POC)

f. Training, Communication & Knowledge Transfer

i. Stakeholders & Communication Plan

ii. Training Plan

iii. User Training

iv. Administrative Support Training

v. Technical Support Training III. Project Tracking and Oversight

a. Weekly Status Meetings and Communications

b. Scheduled Reports and Updates

c. Project Reports

d. Action Item Tracking

e. Decision Log Tracking

f. Risks, Issues, Dependencies and Assumptions (RIDA) Management / Tracking Roles and Responsibilities The following table identifies the general roles and responsibilities of the parties with respect to Project Planning, where RACI (Responsible Accountable Consulted Informed) designation(s) are assigned to indicate the proposed roles and responsibilities in performing and/or completing the activity or task:

18. Create and develop risk management plans, to include all stages of the implementation and any foreseeable risks to cost, schedule, contract, quality of solution, etc., as well as propose preventative and/or mitigating measures to ensure continuity, to include at least but not limited to:

· Environmental disaster

· Security breach

· Equipment failure

· Data loss

· Etc.

21. Create and develop Quality Control management plan, to include all stages of the implementation and post-implementation, to include at least but not limited to:

· Project management standards

· Risk management standards

· Technical standards

· Functional standards

· Schedules

· Stage gates

· Deliverable management

· Checklists

· Training

· Reliability

· Solution integrity/robustness

· Reporting

· Etc.

image2.png