Attachment F- Project Management Plan Template.docx
DOCX document 268 KB Posted
- Attached to
- ECONOMIC SVCS SYSTEM APP MODERNIZATION State and local contract opportunity
- Solicitation number
- 5400024945
- Issued by
- Richland County, South Carolina
About this file
This is a Project Management Plan (PMP) template document prepared by the South Carolina Department of Social Services (SC DSS) for the Economic Services System Application Modernization (ESSAM) project, a multi-year software development and implementation initiative. The plan establishes comprehensive project governance, organizational structure, lifecycle phases, and management methodologies for coordinating state and contractor efforts. The project phases include Planning, Initiation, Project Planning, Requirements and Design, System Development, Acceptance Testing, Implementation, Federal Review, and Closeout. The document defines roles and responsibilities across the State Project Team (including Project Director, Project Manager, Financial Analyst, and various functional and technical leads), the Software Development Contractor (SDC) organization, independent verification and validation providers, and supporting agencies including DSS Division of Technology Services and Department of Admin Division of Technology Operations. Deliverables are managed through formal approval processes with specific acceptance criteria documented in Deliverable Expectation Documents (DEDs), and the state anticipates federal oversight by USDA FNS throughout the project lifecycle.
The plan employs PMBOK-guided project management incorporating five process groups (Initiating, Planning, Executing, Monitoring and Controlling, and Closing) and establishes baselines for requirements, scope, schedule, and cost. Human resource management addresses staffing through multiple acquisition methods including Full Time Equivalents, temporary positions, Request for Proposals, state staffing contracts (TAPFIN), and Memoranda of Understanding. The state projects resource needs ranging from 47 to 56 full-time equivalent positions during the active implementation phase, with staffing tapering to 13 FTEs in closeout phases. Project management systems and tools include SharePoint for document repository and stakeholder management, Microsoft Team Foundation Server for requirements and defect tracking, Microsoft Project for scheduling, and standard Microsoft Office applications. The plan emphasizes quality assurance through internal SDC processes and state oversight, configuration management, integrated change management through a Change Control Board, and risk mitigation strategies, with specific provisions for contract administration, vendor invoicing procedures with ten-business-day payment windows, and closeout activities including final lessons learned documentation and project closure signoff by executive leadership.
View the file
Other files for this state and local contract opportunity
Show all 22
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
South Carolina Department of Social Services
Project Comment by Delage, Bruno G: This Project Management Plan(PMP) is a template for SC DSS and will be used as a project accelerator. The highlighted text is meant to assist the users identify relevant sections to update.
Project Management Plan and Products
| Document number: |
| Project_Name.PLAN.0000 |
| Version: |
| 0.1 |
Preface This document describes the overall approach to the management of the Project_Name and the supporting management plans that will guide the project. It also defines the roles and responsibilities required to properly carry out this plan.
Contributors Name of Contributor(s)
Owner This document is owned by the Project Director Document Control Information
| TITLE |
| Project Management Plan and Products |
| DOCUMENT CONTROL NO. |
| XXX.PLAN.0000 |
| VERSION |
| 0.1 |
| REPOSITORY LOCATION |
| TBD (Controlled Documents) |
| SUBMITTER |
| Name of Submitter |
Version History
| Ver. |
| Approval Date |
| Author |
| Sections |
| Description of change |
Vendor Quality Management Review This document has been reviewed by the following people.
| Reviewer Name |
| Date |
| Version No. |
| Revision Remarks |
Table of Contents
| 1. | Introduction | 6 |
| 1.1 | Project Management Plan Purpose | 6 |
| 1.2 | Project Management Plan Goals and Objectives | 6 |
| 1.3 | Scope | 6 |
| 1.4 | Assumptions | 7 |
| 1.5 | Constraints | 7 |
| 1.6 | References | 7 |
| 2. | Project Management Model | 7 |
| 2.1 | Project Functional Organization and Governance | 7 |
| 2.1.1 | Project Executives | 9 |
| 2.1.1.1 | SC Department of Social Services (SC DSS) State Director | 9 |
| 2.1.1.2 | Division Director (Update based on Agency) | 9 |
| 2.1.1.3 | System Contract Manager (Optional State Role depending on the Project) | 9 |
| 2.1.2 | State Project Team | 10 |
| 2.1.2.1 | Project Director | 10 |
| 2.1.2.2 | Project Manager | 10 |
| 2.1.2.3 | Financial Analyst (Optional State Role depending on the Project) | 11 |
| 2.1.2.4 | Communications and Documentation Manager (Optional State Role depending on the Project) | 11 |
| 2.1.2.5 | Technical Support Specialist | 11 |
| 2.1.2.6 | System Team Leads | 12 |
| 2.1.2.7 | System Functional Lead | 12 |
| 2.1.2.8 | System Technical Lead | 13 |
| 2.1.2.9 | System Subject Matter Expert (SMEs) | 13 |
| 2.1.2.10 | System Technical Specialist | 13 |
| 2.1.2.11 | System Test Lead | 13 |
| 2.1.2.12 | System Test Specialist | 14 |
| 2.1.2.13 | System Business Analysts (BAs) | 14 |
| 2.1.3 | Software Development Contractor (SDC) | 14 |
| 2.1.3.1 | SDC Team Reporting Structure – TO BE UPDATED BY SELECTED VENDOR | 15 |
| 2.1.3.2 | SDC Project Director - TO BE UPDATED BY SELECTED VENDOR | 15 |
| 2.1.3.3 | SDC Project Manager - TO BE UPDATED BY SELECTED VENDOR | 15 |
| 2.1.3.4 | SDC Assistant Project Manager- TO BE UPDATED BY SELECTED VENDOR | 16 |
| 2.1.3.5 | SDC PMO Manager- TO BE UPDATED BY SELECTED VENDOR | 17 |
| 2.1.3.6 | SDC System Quality Assurance Specialists - TO BE UPDATED BY SELECTED VENDOR | 17 |
| 2.1.3.7 | SDC System Functional Design Manager- TO BE UPDATED BY SELECTED VENDOR | 17 |
| 2.1.3.8 | SDC System Functional Design Team- TO BE UPDATED BY SELECTED VENDOR | 18 |
| 2.1.3.9 | SDC System Testing Manager- TO BE UPDATED BY SELECTED VENDOR | 19 |
| 2.1.3.10 | SDC System Testers- TO BE UPDATED BY SELECTED VENDOR | 19 |
| 2.1.3.11 | SDC System Development Manager- TO BE UPDATED BY SELECTED VENDOR | 20 |
| 2.1.3.12 | SDC System Developers- TO BE UPDATED BY SELECTED VENDOR | 21 |
| 2.1.3.13 | SDC System Technical Architect - TO BE UPDATED BY SELECTED VENDOR | 21 |
| 2.1.3.14 | SDC Implementation Manager-- TO BE UPDATED BY SELECTED VENDOR | 22 |
| 2.1.3.15 | SDC Implementation Leads-- TO BE UPDATED BY SELECTED VENDOR | 23 |
| 2.1.4 | DSS Division of Technology Services (DTS) – Update responsibilities based on selected solution. | 23 |
| 2.1.5 | Department of Admin Division of Technology Operations (DTO) – Update responsibilities based on selected solution. | 24 |
| 2.1.6 | Independent Verification and Validation (IV&V) | 24 |
| 2.1.7 | Federal USDA FNS | 24 |
| 2.2 | Project Lifecycle | 24 |
| 2.2.1 | Planning | 24 |
| 2.2.2 | Initiation | 24 |
| 2.2.3 | Project Planning | 25 |
| 2.2.4 | Requirements and Design | 25 |
| 2.2.5 | System Development | 25 |
| 2.2.6 | Acceptance Testing | 25 |
| 2.2.7 | Implementation | 25 |
| 2.2.8 | Federal Review | 26 |
| 2.2.9 | Closeout | 26 |
| 3. | Project Management Methodology | 26 |
| 3.1 | Project Integration Management | 28 |
| 3.1.1 | Project Plan Development | 28 |
| 3.1.2 | Monitoring and Controlling Project Work | 28 |
| 3.1.2.1 | Baselines | 28 |
| 3.1.2.2 | Tracking Actual Performance | 29 |
| 3.1.2.3 | Action Item (AI) Tracking | 29 |
| 3.1.3 | Integrated Change Management | 29 |
| 3.2 | Scope Management | 29 |
| 3.2.1 | Project Scope Management | 30 |
| 3.2.1.1 | Project Scope Baseline Maintenance | 30 |
| 3.2.1.2 | Project Scope Verification and Deliverable Approval | 31 |
| 3.2.1.3 | Project Scope Management Tracking, Reporting, and Metrics | 31 |
| 3.2.2 | Product Scope (Requirements) Management | 31 |
| 3.3 | Performance Measurement | 31 |
| 3.4 | Procurement Management | 32 |
| 3.4.1 | Procurement Planning (Following to be confirmed with DSS Procurement and MMO) | 32 |
| 3.4.2 | Solicitation Planning | 33 |
| 3.4.3 | Solicitation | 33 |
| 3.4.4 | Source Selection | 34 |
| 3.4.5 | Contract Administration | 34 |
| 3.4.5.1 | Vendor Invoicing Procedures (TO BE UPDATED) | 35 |
| 3.4.6 | Prime Vendor Subcontractor Management (Update by Prime Vendor) | 35 |
| 3.4.7 | Contract Closeout | 36 |
| 3.5 | Human Resource Management | 37 |
| 3.5.1 | Staff Planning/Needs Assessment | 37 |
| 3.5.1.1 | Initial Needs Assessment | 37 |
| 3.5.1.2 | Ongoing Needs Assessment | 38 |
| 3.5.2 | Staff Acquisition | 38 |
| 3.5.2.1 | Full Time Equivalent (FTE) | 38 |
| 3.5.2.2 | Request for Proposal (RFP) | 39 |
| 3.5.2.3 | State Staffing Contract | 39 |
| 3.5.2.4 | DSS Fixed Price Bid | 40 |
| 3.5.2.5 | Memorandum of Understanding (MOU) | 40 |
| 3.5.2.6 | Field Resources (Loan) | 40 |
| 3.5.2.7 | SDC Employees | 40 |
| 3.5.2.8 | Prime Vendor Subcontracts | 41 |
| 3.5.3 | Skills and Training Assessment | 41 |
| 3.5.4 | Staff Retention | 42 |
| 3.5.5 | Staff Management and Administration | 42 |
| 3.5.6 | Staff Transition or Release | 43 |
| 3.5.6.1 | Release and Replacement of Non-Performing Resources | 43 |
| 3.5.6.2 | Backup Planning | 43 |
| 3.5.6.3 | Succession Planning (Key Roles) | 44 |
| 3.5.6.4 | Release Planning | 44 |
| 3.6 | Documentation Management | 45 |
| 3.6.1 | Document Lifecycle | 45 |
| 3.6.2 | Version Control | 45 |
| 3.6.3 | Creating, Revising, and Approving Controlled Documents | 46 |
| 3.6.4 | Publishing, Storing, and Retiring Documents | 46 |
| 3.6.5 | Reproducing and Distributing Documents | 46 |
| 3.6.6 | Storing and Managing Electronic Mail | 46 |
| 3.7 | Deliverable Approval Process | 47 |
| 3.7.1 | Submission of Document Deliverables | 47 |
| 3.7.2 | Review Input Requirements | 47 |
| 3.7.2.1 | Deliverable Expectation Documents | 47 |
| 3.7.2.2 | Formal CDRL Deliverables | 48 |
| 3.7.3 | Deliverable Review | 48 |
| 3.7.4 | Full Deliverable Approval | 48 |
| 3.7.4.1 | Deliverable not Approved | 48 |
| 3.7.4.2 | Deliverable Approved | 49 |
| 3.7.5 | Partial Deliverable Approval | 49 |
| 3.7.6 | Interim/Draft Reviews | 50 |
| 3.7.7 | Making Updates to Documents | 50 |
| 3.8 | Closeout | 51 |
| 3.9 | Exceptions to Project Processes | 52 |
| 4. | Project Team Training | 52 |
| 4.1 | Identify Training Needs | 52 |
| 4.2 | Training Documentation | 52 |
| 4.3 | Method of Delivery | 52 |
| 4.4 | Training Schedules and Tracking | 53 |
| 4.5 | Training | 53 |
| 4.5.1 | SharePoint | 53 |
| 4.5.2 | Processes | 53 |
| 4.5.3 | Tools | 53 |
| 5. | Subsidiary Plans and Procedures | 53 |
| 5.1 | Project Charter and Plans | 53 |
| 5.1.1 | .CHTR.0002 - Project Charter | 53 |
| 5.1.2 | .PLAN.0001 – Project Management Plan | 53 |
| 5.1.3 | .PLAN.0002 – Cost Management Plan | 54 |
| 5.1.4 | .PLAN.0003 – Communications Management Plan | 54 |
| 5.1.5 | .PLAN.0004 – Implementation Advanced Planning Document (IAPD) | 54 |
| 5.1.6 | .PLAN.0150 State Quality Assurance Management Plan – M&O | 54 |
| 5.1.7 | .PLAN.0011 - Requirements Management Plan (PACSS) | 54 |
| 5.1.8 | .PLAN.0100 – Risk Management Plan and Products | 54 |
| 5.1.9 | .PLAN.0101 – Statewide Implementation Plan and Products | 54 |
| 5.1.10 | .PLAN.0102 – PACSS Quality Assurance Management Plan and Products | 54 |
| 5.1.11 | .PLAN.0103 – PACSS Configuration Management Plan and Products | 54 |
| 5.1.12 | .PLAN.0104 – PACSS Software Development Plan and Products | 55 |
| 5.1.13 | .PLAN.0105 - PACSS Data Conversion Plan and Design Document | 55 |
| 5.1.14 | .PLAN.0106 – PACSS Training Plan and Products | 55 |
| 5.1.15 | .PLAN.0107 – PACSS Test Plan and Products | 55 |
| 5.1.16 | .PLAN.0108 – PACSS Federal Certification Plan and Products | 55 |
| 5.1.17 | .PLAN.0109 – FCCMS Software Development Plan and Products | 55 |
| 5.1.18 | .PLAN.0110 – FCCMS Configuration Management Plan and Products | 55 |
| 5.1.19 | .PLAN.0111 – FCCMS Quality Assurance Management Plan and Products | 55 |
| 5.1.20 | .PLAN.0112 – FCCMS Test Plan and Products | 55 |
| 5.1.21 | .PLAN.0118 – FCCMS Requirements Management Plan | 56 |
| 5.1.22 | .PLAN.0113 – FCCMS Data Conversion Plan and Design Document | 56 |
| 5.1.23 | .PLAN.0114 – FCCMS Training Plan and Products | 56 |
| 5.1.24 | .PLAN.0115 – PACSS Sponsor Roadmap Plan | 56 |
| 5.1.25 | .PLAN.0116 – PACSS Organizational Change Mgmt Communication Plan | 56 |
| 5.2 | Project Procedures | 56 |
| 5.2.1 | .PROC.0001 - SharePoint Policies and Procedures Manual | 56 |
| 5.2.2 | .PROC.0002 – Cost Management Procedures | 56 |
| 5.2.3 | .PROC.0003 - Change Management Process | 56 |
| 5.2.4 | .PROC.0004 – Schedule Development and Maintenance Process | 56 |
| 5.2.5 | .PROC.0006 - Risk Management Process | 57 |
| 5.2.6 | .PROC.0116 – State QA Oversight Procedures – M&O | 57 |
| 5.2.7 | .PROC.0030 – Issue Management Process | 57 |
| 5.2.8 | .PROC.0113 – Enhancement Request Process | 57 |
| 6. | Project Management Systems and Tools | 57 |
| 7. | Plan Maintenance | 58 |
| Appendix A | Project Contract Deliverable and Milestone List | 59 |
| Appendix B | State Project Team Organization Chart | 61 |
| Appendix C | Project Team Resource Planning | 63 |
| Appendix D | SDC Project Organization Chart | 65 |
Introduction This Project Management Plan (PMP) defines how the Project is to be planned, executed, monitored, controlled, and closed. It is a summary plan that identifies the project organization and lifecycle, project management methodology (PMM), describes internal team training, and summarizes supporting subsidiary management plans, processes, and procedures.
The project is defined and authorized by the Project Charter approved by the SC Department of Social Services (DSS) State Director.
Project Management Plan Purpose The purpose of this PMP is to describe the overall context for the project and to provide a framework and structure for the execution, monitoring, control, and closure of the Project.
Project Management Plan Goals and Objectives This plan is intended to provide management structure and capabilities that help the project team:
· Define a context for the project and describe a project lifecycle
· Describe how the project will be planned, executed, monitored, and controlled
· Integrate the plans and activities of the development contractors with those of the State Project Team
· Address business objectives and meet end user and federal requirements
· Manage project activities within approved budgets and schedules
· Maintain timely and accurate communication with project stakeholders Scope This PMP details the project management plans and procedures that comprise the project management system utilized by the State and Software Develepment Contrator (SDC) on the Project. These plans and procedures will guide the State and SDC in meeting the requirements of the Contract/Statement of Work (SOW). The PMP also describes how the Project plans and procedures integrate with those of the State.
The key elements in the project management system are:
· The plans describing the work to be performed and how the project will operate
· The procedures which standardize key tasks so they are performed in a systematic and visible manner
· The records which the Project Management Team (PMT) uses to control status and events
· The project management activities used to plan, control, and react to daily events
· The resources and tools used to implement the plans
The PMP defines how the State and SDC will perform the project management tasks of planning, organizing, staffing, directing, coordinating, controlling, measuring, reporting and evaluating. Furthermore, it establishes how the SDC will strive to achieve the four management objectives that are paramount to project success:
1. High-quality work: Deliver high quality end products, address business objectives and meet end user and Federal needs
2. On-time delivery: Complete deliverables on schedule
3. Effective communication: Maintain timely and accurate communication to project participants throughout the entire project
4. Aggressive and proactive management: Identify potential problems and risks before they develop, and initiate appropriate corrective actions and mitigation strategies Assumptions
· Adequate personnel resources and effort will be applied to achieve critical success factors identified in the charter
· Organizational or staffing changes will not have a major effect on the Project requirements, scope, and goals
· The Project will be funded and budgeted as planned throughout the Project life cycle
· The SDC can perform all the work as defined in the Request for Proposal (RFP) and this work can be accomplished at an acceptable cost
· The SDC proposes technology that is viable and acceptable to all stakeholders
· The SDC employs sound development methodologies and sound configuration management resulting in a stable and effective infrastructure with separate development, test, training, and production environments
· SC DSS and county business owners will be available to make timely decisions regarding system functionality and requirements
· SC DSS Department of Technology Services (DTS) staff will be responsive to the project requests regarding data conversion, implementation, etc.
Constraints
· The project must comply with Federal and State Standards (UPDATE AS APPROPRIATE)
· Appropriately skilled human resources are limited as are the funds to procure additional resources
· The time and ability to obtain project resources through standard procurement and personnel practices may constrain the ability to add or replace skilled staff
· The dependencies on Regulatory and Legislative approval to proceed as planned References For current versions of all controlled documents refer to the Controlled Documents folder in SharePoint(Or another product that houses approved documentation).
Project Management Model Project Functional Organization and Governance While participation by each area in the project is critical, ultimate responsibility for the success of the project lies with the Department of Social Services. In order to meet this responsibility DSS has dedicated a full time resource, the Project Director(Or project equivalent), and created the State Project Team to manage and oversee the Project.
Under the direction of the Agency Director, the day-to-day activities of the State Project Team will be managed by the Project Director, the Project Manager, and the State Project Team Leads. These team members are the decision makers for the Project and will set project priorities, assign project resources, approve Risk response strategies, and make other project decisions as needed. Final decision-making authority of the State Project Team remains with the Project Director(or equivalent) as specified in the Project Charter.
Project decisions that cannot be made by the Project Director will be escalated to the Agency Director and/or Appropriate Federal Agency as appropriate.
The day-to-day management of the software development effort will be managed by the SDC. The SDC will also provide information to the State Project Team to assist in the overall management of the project. Information on application development reported to the State Project Team includes, but is not limited to, WBS elements, scheduled tasks and status, issues, risks, action items, change order status, requirements stability metrics, and testing metrics. The collective team, including the State Project Team, the SDC, and any subcontractors, will be referred to as the Project Team.
To provide input into and support the management activities of the State Project Team, a number of State Project Team members have been tasked with overseeing the day-to-day activities of the SDC. Each role is defined as Oversight for specific areas of responsibility and is described in the following project roles and responsibilities.
Project Executives SC Department of Social Services (SC DSS) State Director The Executive Sponsor for the Project is the SC DSS State Director and Program Area Director. The direction, management, oversight, and decision-making authority for the Project is under the sole authority of the Director of the SC Department of Social Services who shall make all final decisions regarding the project.
The SC DSS State Director will provide overall governance for the Project, and shall provide the policy and strategic guidance to the Project. This position is the highest approval authority for the State concerning Project scope, schedule, and deliverables. This position is ultimately responsible for the success of the Project.
Division Director (Update based on Agency) The Division Director has responsibility for the XXX program in South Carolina and, therefore, has a critical role in the successful completion of the Project. The Director is the owner of the Project and products, and will maintain a significant awareness of the overall progress and direction of the Project to ensure that the proposed system components are implemented in a manner that best serves the affected (Program Name) program in South Carolina.
The Division Director reports to the SC DSS State Director and serves as a liaison between stakeholders and the Project Team and identifies resources and processes outside of the project team that need to be addressed for successful implementation of the project. The Division Director directs the efforts of the Project Director and serves as an escalation point for resolution of conflicts between the SDC and State Project Team and for final resolution of program concerns that affect the development and implementation of proposed system.
Responsibilities:
· Promote and support the Project
· Provide policy and strategic guidance
· Resolve escalated risks and issues
· Approve escalated change requests System Contract Manager (Optional State Role depending on the Project) The System Contract Manager provides the necessary state contract and administrative oversight (i.e. approves procurements, manages contract changes, approves timesheets/state employee leave) for the Project. This position will actively engage with the Division Director, the Project Director, and the Project Manager to be aware of the status of the Project including project risks and issues and to remove obstacles inhibiting progress. This position will work with the project’s fiscal analyst in the preparation of the annual updates to the Implementation Advanced Planning Document (IAPD) to OCSE and will coordinate procurement activities for the project. This position will also ensure approved contract deliverables are submitted in the DSS financial process for payment.
State Project Team The State Project Team is comprised of staff from the SC Department of Social Services and contracted technical and project management experts (See Appendix B State Project Team Organization Chart).
Project Director The Project Director provides strategic direction for the project and provides advice and recommendations to the SC DSS State Director and the Division Director regarding fiscal and legislative issues affecting the project at the federal and state level.
The Project Director reports to the Division Director, serves as a liaison between stakeholders and the Project Team and identifies resources and processes outside of the project team that need to be addressed for successful implementation of the project. The Project Director directs the efforts of the Project Manager and serves as an escalation point for resolution of conflicts between the SDC and State Project Team.
The responsibilities of the Project Director include:
· Ensure timely completion of the integrated Project
· Provide leadership in communicating the Project vision, goals, and priorities to all stakeholders, including federal and state oversight organizations and the beneficiaries of the Project
· Bring strategic issues and recommendations to the Division Director and SC DSS State Director and provide strategic direction to the Project Manager
· Communicate the status of the project to state legislative leaders
· Oversee the development of the Project budget and presenting it to the Division Director, SC DSS State Director, and other interested stakeholders
· Facilitate timely resolution of major Project issues
· Work with the Project Team to ensure the system implementation is coordinated with other teams
· Ensure timely delivery of the completed system for ongoing management
· Prepare monthly and other periodic progress reports Project Manager The Project Manager reports to the Project Director.
The Project Manager will:
· Utilize formal project management methodologies and processes from PMBOK and from automated system development standards of IEEE, tailored as necessary and appropriate for the Project. Ensure schedules, metrics, and deliverables are presented in detail to ensure successful project implementation
· Track the Project against its baseline schedule, identifying variances effecting the completion of project tasks and activities, particularly those variances that affect the critical path
· Make staffing assignments within the State project team to best utilize project resources
· Approve or recommend for approval project deliverables, including deliverables specified in the Project contract and other products
· Assess task estimates, identify task interdependencies, resource assignments, project milestones, project risks, and delivery dates
· Prepare project status report for presentation at the project status meeting and to executives
· Ensure that necessary project metrics are being developed, monitored, and reported in order to objectively ascertain that the right project is being developed and delivered in accordance with the contracted implementation schedule and other contract requirements
· Foster a positive partnership with the SDC while holding the contractor accountable for project schedule, cost, and quality
· Develop and maintain project plans and processes for executing, monitoring, and controlling the project
· Provide project management process support and mentoring
· Evaluate and report on development contractor project management deliverables
· Report status and performance at the Project level
· Execute Risk and Issues Management functions
· Execute Action Items functions
· Execute Schedule Management functions
· Monitor Change Management functions Financial Analyst (Optional State Role depending on the Project)
· Execute Change Management functions
· Execute Cost Management functions
· Coordinate travel and expenses Communications and Documentation Manager (Optional State Role depending on the Project) Responsibilities:
· Maintain the PMO SharePoint site
· Coordinate stakeholder communications
· Execute Documentation Management functions Technical Support Specialist The Technical Support Specialist provides technical support to the Project Team.
Responsibilities of the Technical Support Specialist:
· Analyze, maintain, troubleshoot, and resolve hardware and software issues
· Plan, coordinate, manage, and complete maintenance for all project training equipment
· Maintain equipment inventory lists and team seating charts System Team Leads The State Team Leads, under the direction of the Project Director, are responsible for the day-to-day management of the System functional areas. Each of these roles works with their development contractor counterpart(s) to manage the functional area.
General responsibilities are:
· Coordinate with Project Director to execute Staffing Management functions
· Coordinate functional area reviews, approvals, and communication
· Evaluate and report on all functional area deliverables
· Determine functional area priorities
· Serve as point of contact for SDC functional managers and subject matter and technical experts, including scheduling of requirements validation and testing activities
· Resolve functional area action items, issues and risks
· Escalate action items, issues and risks to the Project Manager
· Participate in the Change Control Board (CCB)
· Review and approve functional area deliverable acceptance criteria documented in Deliverable Expectations Documents (DEDs)
· Participate in Project Management Office activities including action items, risk and issue management, and schedule development and maintenance State Team Leads for System include the Functional Lead and Technical Lead. Responsibilities specific to each of these roles are addressed in the following sections.
System Functional Lead The System Functional Lead performs the lead role in developing a thorough knowledge of the functional requirements and functional architecture of the system.
Responsibilities:
· In collaboration with the SDC, plan and resource the tasks in the project schedule related to State project team responsibilities for requirements validation, general and detailed design and system testing
· Oversee the work performed by the SDC during the requirements validation, development, design and system testing phases of the system development life cycle (SDLC) including establishing a positive day-to-day interaction with the appropriate members of the SDC staff to address concerns identified during this oversight
· Review SDC deliverables applicable to the areas of responsibilities in accordance with project plans and processes and in accordance with the contract between the Department of Social Services (Department) and the SDC
· Coordinate and Manage the activities of the Business Analysts (BAs) and the Subject Matter Experts (SMEs)
· Oversee the Requirement Management Process in collaboration with the SDC to ensure changes to system requirements are controlled and to ensure system requirements are traced through a Requirements Traceability Matrix (RTM) throughout the SDLC
· Develop a thorough knowledge of the technical requirements of the System in order to understand how these requirements could affect the functional design System Technical Lead Responsibilities:
· Execute project configuration management oversight
· Serve as liaison between the Project and DSS DTS by coordinating and managing the activities defined in the SLA
· Monitor security policy compliance
· Monitor hardware and Local Area Network (LAN) activities System Subject Matter Expert (SMEs) Under the direction of the System Functional Lead, the subject matter experts apply their knowledge of Program Area, and technology to help develop the project requirements and verify their fulfillment.
Responsibilities:
· Provide programmatic assistance and requirements clarification to any state or development contractor staff
· Review final project deliverables
· Act as lead for tasks and activities that are State responsibilities These personnel work with their development contractor counterparts to:
· Coordinate activities with their counterparts in the SDC team (this is not intended to be a one-to-one arrangement in all cases)
· Be involved in the requirements validation activities for their respective areas
· Receive regular updates from their SDC counterparts on work completed, work in progress, and work yet to be done
· Be a source of information to the development contractors when appropriate System Technical Specialist The Technical Specialists provide expertise in a variety of areas, including technical knowledge and Program Area expertise.
Responsibilities of the Technical Specialists:
· Review plans, processes, reports, and deliverables for consistency with State expectations and raise concerns to the appropriate Team Lead (this may also include work in progress)
· Monitor SDC activities for compliance System Test Lead The Test Lead will work with the SDC and the end users to coordinate decisions related to testing activities.
Responsibilities:
· Validate and approve testing deliverables, including test scripts
· Execute the Project test plan which includes the testing activities for which the State Project Team is responsible
· Facilitate testing communications between the SDC, DSS County Personnel and DSS project and program team System Test Specialist Responsibilities:
· Work with State’s SMEs and BAs to develop test scenarios and test scripts
· Prepare test data needed for executing test scripts
· Execute test scripts
· Record and verify test results
· Analyze and report test results
· Report defects to Test Specialist Lead
· Perform regression tests
· Reproduce defects/demonstrate defects to development as needed
· Participate in Incident Review meetings as needed
· Provide data analysis and root cause analysis as needed System Business Analysts (BAs) Under the direction of the System Functional Lead, the BAs apply their knowledge of the program area, and technology to help develop the project requirements and verify their fulfillment.
Responsibilities:
· Contribute to requirements definition, testing, data conversion, training, and implementation activities
· Provide programmatic assistance and requirements clarification to any state or development contractor staff
· Review final project deliverables
· Act as lead for tasks and activities that are State responsibilities These personnel work with their development contractor counterparts to:
· Coordinate activities with their counterparts in the SDC team (this is not intended to be a one-to-one arrangement in all cases)
· Be involved in the requirements validation activities for their respective areas
· Receive regular updates from their SDC counterparts on work completed, work in progress, and work yet to be done
· Be a source of information to the development contractors when appropriate Software Development Contractor (SDC) The Project will utilize the SDC for the ongoing maintenance and operations of the system. The SDC is responsible for managing their work as outlined in the Record of Negotiation (RoN) Contract Amendment Responsibilities:
· Complete their contractual duties
· Develop contracted plans and deliverables
· Manage and perform the work in their development and maintenance and operations contract in accordance with approved plans
· Manage the work and deliverables of all their subcontractors
· Report information needed by the State Project Team to manage the project and maintenance and operation activities and oversee contractor activities
· Escalate risks and issues to the State Project Team as needed for resolution
· Follow the State Project Team change management and enhancement request processes and procedures
· Provide schedule updates and earned value metrics to the State Project Team
· Follow specific State Project Team plans and processes as noted in the Project Management Methodology (PMM) section of this document
· Cooperate with the SQA in the performance of their duties SDC Team Reporting Structure – TO BE UPDATED BY SELECTED VENDOR The SDC Project Director has final responsibility for SDC project responsibilities. There are eight significant areas reporting through their respective management organization – Project Management, Quality Assurance, Functional Design, Technical Design, Development, Testing, Networking, and Implementation. Additionally, the Functional Manager, Technical Manager, Rollout Implementation Manager, Training Manager and Conversion Manager have key roles in the organization. The SDC Project Manager and SDC Project Management Office provide supporting management functions to the SDC Project Director. The roles and responsibilities of each of these individuals are described below.
SDC Project Director - TO BE UPDATED BY SELECTED VENDOR The SDC Project Director is responsible for the successful design, development and implementation of the Project. S/he participates in project planning, assists with major issues, problems and conflicts, removes obstacles, plans the project scope, approves scope changes, and has final approval of all changes that impact timeline, budget, or scope and signs off on approvals to proceed to each succeeding project phase. The SDC Project Director is a champion for the Project and committed to its success.
Responsibilities:
· Participate in project planning (High Level)
· Work with the State to resolve contract-related issues throughout the life of the project
· Ensure adequate staffing
· Assist with major issues, problems and policy conflicts, removes obstacles, plans the project scope
· Approve all scope changes that impact timeline, budget, or scope and signs off on approvals to proceed to each succeeding project phase.
· Champion the Project and be committed to its success
· Responsible for overall SDC management during Warranty and M&O period SDC Project Manager - TO BE UPDATED BY SELECTED VENDOR (#1 in the SDC Team Organization Chart in Appendix D) The SDC System Project Manager oversees the day-to-day execution and delivery of the solution. Reporting through the SDC Program Director, the SDC System Project Manager assumes authority for overall System management, quality assurance and contract compliance on behalf of the SDC System Team. Provides or delegates authority for all required System-related negotiation and coordination with the State project management staff, as well as participates in regularly scheduled project status meetings.
Responsibilities:
· Be the focal point for all SDC System related issues
· Work directly with the State Project Manager to assume authority for overall project management, quality assurance and contract compliance on behalf of the SDC Team
· Provides or delegates authority for all required negotiation and coordination with the State project management staff
· Participates in regularly scheduled project status meetings.
· Plan, organize, direct, and monitor the tasks and activities of the System implementation
· Responsible for implementation in accordance with SDC methodologies
· Responsible for management and resolution of Risks and Issues
· Conduct monthly project reviews with SDC Senior Management
· Has approval authority over all project deliverables
· Monitor the progress of the project
· Communicate project progress and issues to the SDC Project Director
· Maintain the Project schedule and provides input to the SDC Schedule Manager
· Ensure deliverable quality
· Provide System-related input for weekly and monthly project status reports
· Provides direction to the SDC team
· Ensure adequate staffing
· Perform application certification after installation in the State environments SDC Assistant Project Manager- TO BE UPDATED BY SELECTED VENDOR (Reference # in the SDC Team Organization Chart in Appendix D) Works directly with the SDC Project Manager to ensure overall project management, quality assurance and contract compliance on behalf of the SDC Team. Acts in the absence of the SDC Project Manager.
Responsibilities:
· Participate in PMO and PMO Team meetings
· Focus on the day-to-day management of M&O, especially in the areas of Enhancement Requests
· Work with the SDC PMO Team and the SDC functional managers to facilitate Enhancement Request project tasks and produce high quality deliverables
· Act as a liaison between the SDC and the State
· Maintain open lines of communication with managers through regular meetings and communications
· Work with the State and Quality Assurance to meet approved project quality standards SDC PMO Manager- TO BE UPDATED BY SELECTED VENDOR (Reference # in the SDC Team Organization Chart in Appendix D)
The SDC PMO Manager executes, monitors, and controls PM activities on a day-to-day basis during M&O. Reviews project documentation to ensure documents are completed in alignment with standards. Project Governance is also one of the key responsibilities of the SDC PMO Manager.
Responsibilities:
· Updates and maintains the project schedule
· Prepare weekly project status reports
· Updates the project schedule based upon turnaround reports
· Raises issues and risks to the State PMO SDC System Quality Assurance Specialists - TO BE UPDATED BY SELECTED VENDOR (Reference # in the SDC Team Organization Chart in Appendix D) The SDC Quality Assurance (QA) Specialists are responsible for the review of project documentation before submission to the State.
Responsibilities:
· Performs monthly document cleanup
· Generate reports for Maintenance and Operations
· Assist in schedule updates SDC System Functional Design Manager- TO BE UPDATED BY SELECTED VENDOR (Reference # in the SDC Team Organization Chart in Appendix D) Having a thorough knowledge of the Program area and application. Will work closely with the SDC Delivery Team, SDC project management as well as the State Project Team to ensure that the commercial off the shelve (COTS) application meets the functional and technical requirements as agreed upon in the contract.
Areas of expertise include product planning, functional design, product development, requirements engineering, court processes and environment, product customization, technical design, and technical architecture.
Conducts internal reviews among project staff and jointly with the State to identify business requirements associated with Enhancement Requests, which serve as the blueprint for the functional and technical system designs. Translates results from enhancement request impact analyses into the creation and updates to design documents.
Responsibilities:
· Participate in triage meetings
· Acknowledge and address all questions, points, and issues raised regarding defects and functional design
· Pursue solutions to outstanding defect issues
· Oversee design documentation updates
· Manage the SDC product / portfolio and development life cycles for system\solution
· Support SDC PMO activities:
· Develop functional design tasks for the project schedule
· Provide weekly team status updates
· Monitor and update functional design team tasks on the project schedule
· Submit, review and update Action Items, Issues and Risks
· Participate in business requirements development, validation and verification and contributes to the process of translating those into executable functional requirements
· Manage traceability of requirements as defined in the Requirements Management Plan
· Maintain the Requirements Traceability Matrix in TFS
· Communicate product requirements to development team, reviews development plans against requirements, and manages changes within the constraints of budget, schedule, and business need in collaboration with project managers, acting as the final decision point for the SDC, if required.
· Acknowledge and address all questions, points, and issues raised regarding Enhancement Requests and Production Operation defects
· Oversee the linking of requirements as defined in Requirements Management Plan
· Monitor and update requirements links for changes and consequent effects on other requirements
· Oversee preparation of design documents
· Implement approved changes to requirements baseline
SDC System Functional Design Team- TO BE UPDATED BY SELECTED VENDOR (Reference # in the SDC Team Organization Chart in Appendix D) Responsibilities:
· Understand the Federal, State and RFP requirements of the System project
· Prepare documents for Enhancement Requests, Production Operation defects and documentation defects
· Participate in and document Imapct Analyses based on Enhancement Requests
· Develop and/or update design documentation
· Continuously involve and work with the state counterpart
· Work closely with the technical development team on Enhancement Requests and Production Operation defects
· Support development and testing efforts through clarification of design to Development and Test teams, confirmation of validity of test cases and scripts and defect triage as appropriate SDC System Testing Manager- TO BE UPDATED BY SELECTED VENDOR (Reference # in the SDC Team Organization Chart in Appendix D) The SDC Testing Manager is responsible for testing all Enhancement Requests and defects before delivering to the State for their final testing and promotion to production. Will follow the test plan that employs sound testing principals and processes for testing the application to ensure it meets both functional and technical requirements as determined by the State.
Responsibilities:
· Set/refine overall testing strategy and procedures
· Support SDC PMO activities:
· Develop testing team tasks for the project schedule
· Provide weekly team status updates
· Monitor and update testing team tasks on the project schedule
· Submit, review and update Action Items, Issues and Risks
· Review migration of software builds into test environments
· Ensure completion of test preparation and execution activities
· Conduct and participate in planning on-going status meetings
· Establish/review procedures for Database Business Analysts (DBAs) to backup, load, and maintain test data into the test environments
· Ensure proper completion of test scripts
· Oversee test planning, preparation, execution, and documentation of deliverables and work products by test team members
· Review / escalate defects
· Publish and analyze testing metrics to identify potential bottlenecks in test execution, defect creation, or defect resolution processes
· Liaise between testing teams in different functional areas
· Resolve cross-functional issues between testing teams
· Augment testing resources where and when needed
· Communicate test issues and ensure they are addressed SDC System Testers- TO BE UPDATED BY SELECTED VENDOR (Reference # in the SDC Team Organization Chart in Appendix D) Responsibilities:
· Provide input to test planning activities (test scripts, test conditions, test cycles, data-related activities, and test scheduling) and test procedures
· Document traceability as defined in .PLAN.0011 – Requirements Management Plan and in System Test Plan
· Coordinate with DBAs to establish and follow procedures to load test data into the test environments
· Execute Enhancement Request tests
· Test System defects found in SIT and/or REG
· Utilize appropriate test tools to capture, document, and record test activities
· Create, review, and regression test defects documented in the defect tracking tool
· Interact with external entities (i.e. data exchange, execution, and interface related issues) SDC System Development Manager- TO BE UPDATED BY SELECTED VENDOR (Reference # in the SDC Team Organization Chart in Appendix D)
The SDC Development Manager is responsible the software development for SystemEnhancement Requests and for directing the work of the Development Team working on M&O. He works closely with the design, development, test, and State interface teams to ensure that all performance and quality requirements are aligned with the business objectives.
Responsibilities:
· Participate in the PMO and PMO Team meetings
· Support SDC PMO activities:
· Develop development team tasks for the project schedule
· Provide weekly team status updates
· Monitor and update development team tasks on the project schedule
· Submit, review and update Action Items, Issues and Risks
· Lead the development team(s) in building and testing of Enhancement Requests
· Support testing efforts by providing problem investigation, code and data fixes
· Focus specifically on:
· Enhancement Request component coding, unit testing and defect correction
· Unit integration testing
· Support of testing activities
· Software development per approved Enhanement Requests
· Configuration Management
· Interfaces
Responsibilities:
· Manage the SDC product / portfolio and development life cycles for court-case system products
· Participate in business requirements development, validation and verification and contributes to the process of translating those into executable functional requirements
· Communicate product requirements to development team, reviews development plans against requirements, and manages changes within the constraints of budget, schedule, and business need in collaboration with project managers, acting as the final decision point for the SDC, if required.
SDC System Developers- TO BE UPDATED BY SELECTED VENDOR (Reference # in the SDC Team Organization Chart in Appendix D) Responsibilities:
· Work closely with the BA Team to understand the defect, and work together with the BA Team in the completion of the defect fixes
· Actively participate with the database and technical design team to develop the logical and the physical data model for approved Enahancement Requests
· Develop SP calls following the SQL coding standard for the Software components defined in the SDD
· Develop or update business components in C# code for the business rules identified in the solution design
· Follow the design and coding standards
· Write Unit test cases in parallel with application code
· Execute Unit test cases and confirm successful completion
· Verify that Unit test cases properly test application components against valid test criteria
· As necessary, review code and Unit test cases from developers within Development teams. Primary reviews are performed by developers and their peers
· Review Unit test reports to validate test cases pass successfully
· Continuously work together with the testing team during system, integration and user acceptance testing
· Continuously work together with the technical design team to incorporate the proposed/approved technical architecture SDC System Technical Architect - TO BE UPDATED BY SELECTED VENDOR (Reference # in the SDC Team Organization Chart in Appendix D) The SDC Technical Architect directs and coordinates the overall architecture of the System solution. Directs activities of an architecture and technical design teams.
Responsibilities:
· Directs and coordinates the overall architecture of the solution, focusing specifically on:
· Systems Architecture
· Network Architecture
· Application Architecture
· Database Design (logical and physical)
· Infrastructure implementation
· Environment maintenance and operations
· Works closely with the System functional and technical design teams to ensure that the State-specific modifications to the application conforms to the State’s business requirements as well as the architecture standards set forth by the vendor.
· Leads the development of materials, tools, and approaches for architecture activities
· Development and approval of the following technical Project Deliverables
· Software Development Plan and Products
· Detailed System Design Document
· System Requirements and Technical Architecture Plan SDC Implementation Manager-- TO BE UPDATED BY SELECTED VENDOR (Reference # in the SDC Team Organization Chart in Appendix D) Under the direction of the SDC Project Manager, and in coordination and collaboration with Team Leads, the SDC Implementation Manager will oversee the day-to-day activities of the SDC Implementation staff. As part of these duties, the SDC Implementation Manager will conduct and monitor SDC implementation deliverables and activities associated to Go-Live deployment, user training, and user support of the systems.
Responsibilities:
· Review and adhere to established project processes and procedures
· Support SDC PMO activities;
· Develop implementation team tasks for the project schedule
· Provide weekly team status updates
· Monitor and update primary tasks on the Project Schedule
· Submit, review and update Action Items, Issues, and Risks
· Collaborate, coordinate and execute the review, revision and delivery of the Statewide Implementation Plan, Training Plan and other implementation products
· Develop and facilitate the execution of the Pilot and Regional Go-Live Schedules
· Track Go-Live readiness milestones are being met, or mitigated, and engage escalation procedures as necessary
· Advocate and ensure user sites and community are prepared, trained and supported for the system implementation
· Facilitate staffing assignments, within respective areas of responsibility, to best utilize project resources; ensure staff are equipped and trained to perform the various responsibilities of implementation
· Assess Change Controls and provide schedule, cost, and effort estimates impacting respective areas of responsibility
· Coordinate and deliver Pilot, Regional and Statewide Implementation Reports
· Foster a positive partnership amongst the Project Teams and Stakeholders SDC Implementation Leads-- TO BE UPDATED BY SELECTED VENDOR (Reference # in the SDC Team Organization Chart in Appendix D) The SDC Implementation Leads are responsible for supporting the SDC Implementation Manager as well as performing and overseeing activities assigned the implementation teams.
Responsibilities:
· Review and adhere to established project processes and procedures
· Contribute and review implementation, training and support artifacts and deliverables
· Act as lead for tasks and activities that are SDC implementation responsibilities
· Coordinate, collaborate and verify with State counterparts on activities and products related to areas of responsibility as they apply to Go-Live preparation and deployment, user training, and user support of the systems
· Coordinate team planning and direction on assigned implementation tasks
· Provide weekly task and activity updates to the Project Implementation Manager
· Acquire familiarity and understanding of the application and organization change impacts to the user community
· Apprise the Project Implementation Manager of potential risks and issues
· Support data conversion verification for deployment readiness
DSS Division of Technology Services (DTS) – Update responsibilities based on selected solution.
DTS is responsible for providing infrastructure services and support to the Project as defined in the Service Level Agreement (SLA) Responsibilities:
· Network engineering and support
· Desktop support
· Procurement services for hardware and software
· Telephone system and support
· Project facility security
· Provide dedicated staff to the Project as identified in the SLA
· Provide State and DSS technical standards Department of Admin Division of Technology Operations (DTO) – Update responsibilities based on selected solution.
DTO is responsible for providing server infrastructure services and support to the Project as defined in the Service Level Agreement (SLA) Responsibilities:
· Server Hosting
· Database backups
· Hardware and Software Maintenance
· Network Services
· Disaster Recovery Services
Independent Verification and Validation (IV&V) – UPDATE BASED ON PROJECT REQUIREMENTS The IV&V Provider performs a federally optional independent oversight and reporting function.
Responsibilities:
· Observe and review project activities and plans to produce written findings and associated recommendations
· Distribute the associated work products to FNS and DSS IV&V has access to project information through observation, document…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .