The file's text, extracted by GovTribe without its formatting.
ATTACHMENT 011 - UPDATED
SCDHHS Project Management Office
CONSOLIDATED DELIVERABLES MANAGEMENT LIST
1.0 INTRODUCTION
The South Carolina Department of Health and Human Services (SCDHHS) defines a deliverable as a quantifiable good or service that will be provided or adhered to throughout the Project Lifecycle. Deliverables can be tangible or intangible, and are most often specified functions or characteristics of the project. The following tangible deliverables are included as part of the Consolidated Deliverables Management List (CDML) applicable to (SCDHHS) contractors managed in accordance with the Contractor (Vendor) Management Plan. The deliverables listed herein are the expected minimum list for SCDHHS third-party contracts. Depending on the scope of work (SOW), SCDHHS may include additional deliverables to this list or exclude by exception only. Therefore, this is not an all-inclusive list.
Unless otherwise indicated in the specific deliverable list below, deliverables will be submitted electronically by close of business (COB) at SCDHHS (5:00 p.m. Eastern Time). The ‘data rights of ownership’ for each deliverable is the State of South Carolina. Unless otherwise specified within the individual deliverable, any updates to a deliverable after the initial submission and SCDHHS’ approval will be communicated minimally on an annual basis.
Project-based deliverables are documented, monitored, measured and reported via the SCDHHS defined method (e.g., Schedule Management Plan, Communications Management Plan, etc.) throughout the contracted life of the projects lifecycle.
2.0 CONSOLIDATED DELIVERABLES MANAGEMENT LIST
2.1 BASIC TEMPLATE FIELDS
| Item Number |
| This field contains the prefix of ‘D-‘ and then the 3-digit number (e.g., D-001) correlating to the deliverable name |
| Deliverable Name |
| This field contains the SCDHHS approved deliverable name |
| SCDHHS Owner(s) |
| SCDHHS Approver(s) |
| Vendor Owner(s) |
| Vendor Approver(s) |
| Type of Data | | | |
| |_| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
This field is a checkbox categorizing the deliverable’s ‘Type of Data’
| Submission Due Indicator | |
| |_| | Initial |
|_| Recurring |_| Not Applicable (N/A)
Type of Deliverable Due: |_| Submission |_| Adherence
| Status | | |
| Initial | | |
| |_| | Preliminary | |_| | Baseline |
| |_| | Final | | |
| |_| | Not Applicable (N/A) | | |
This field is contains the applicable status checkbox(es) for an initial deliverable.
| Recurring | | |
| |_| | Annual Update | |_| | Other: ________________ |
| |_| | Not Applicable (N/A) | | |
When a recurring submission, the Status can be either ‘Annual Update’, ‘N/A’, or ‘Other: as specified’
| Deliverable Specification |
| This field is the Submission Due description in conjunction with the Submission Due Indicator checkbox(es) indicating the SCDHHS approved submission due date for the deliverable (e.g., Project Kickoff plus (+) five (5) business days; Within ten (10) calendar days from approved project kick-off date, weekly, etc.). |
| Note |
| This field provides the detailed explanation when SCDHHS indicates the deliverable status is ‘N/A’ or for special instructions |
| Description |
| This field provides the detailed description of the SCDHHS required deliverable |
2.2 SCDHHS Standard Deliverables List
| Item Number |
| D-001 |
| Deliverable Name |
| Project Status Report |
| SCDHHS Owner(s) |
| SCDHHS Approver(s) |
| Vendor Owner(s) |
| Vendor Approver(s) |
| Type of Data | | | |
| |X| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |X| | Recurring | |
| |_| | Not Applicable (N/A) | |
| Type of Deliverable Due: |X| Submission |_| Adherence | |
| Status | | |
| Initial | | |
| |X| | Preliminary | |_| | Baseline |
| |_| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |_| | Annual Update | |X| | Other: Weekly |
| |_| | Not Applicable (N/A) | | |
| Deliverable Specification |
| The Contractor (Vendor)’s initial Project Status Report submission is due ten (10) calendar days from the contract start date. |
The recurring project status reports are weekly due by Close of Business (COB) each Thursday Friday.
| Note |
| Recurring project status reports are required using the SCDHHS PMO Microsoft® Project Web App (PWA) online status report template. |
| Description |
| Project related status reports will be produced during the life of the project. |
The project status report is to outline progress toward the information related to the overall status of project delivery. The status reports will be produced weekly to provide stakeholders project information on the status and progress of the project’s delivery. The information provided will contain enough detail to allow stakeholders to make informed decisions and maintain oversight of the project.
At a minimum the reports will contain:
· Overall project status
· Deliverables, milestones, key activities accomplished
· Status of issues and/or risks
· Upcoming key tasks
· Upcoming deliverables and milestones
· Cost Performance Index (CPI)
· Schedule Performance Index (SPI)
· Key decisions made or needed Please refer to the SCDHHS PMO Communications Management Plan and Schedule Management Plan for additional information.
| Item Number |
| D-002 |
| Deliverable Name |
| Project Schedule |
| SCDHHS Owner(s) |
| SCDHHS Approver(s) |
| Vendor Owner(s) |
| Vendor Approver(s) |
| Type of Data | | | |
| |X| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |X| | Recurring | |
| |_| | Not Applicable (N/A) | |
| Type of Deliverable Due: |X| Submission |_| Adherence | |
| Status | | |
| Initial | | |
| |X| | Preliminary | |_| | Baseline |
| |_| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |_| | Annual Update | |X| | Other: Weekly |
| |_| | Not Applicable (N/A) | | |
| Deliverable Specification |
| The Contractor (Vendor)’s initial project schedule submission is due thirty (30) fifteen (15) calendar days from the project kickoff date. The project schedule will not be baselined by the Contractor (Vendor) until SCDHHS approves the project schedule. |
Recurring project schedule updates are weekly due by COB each Thursday Friday.
| Note |
| Recurring project schedule updates are required using the SCDHHS PMO Project Web App (PWA) |
| Description |
| Project schedules will be developed and maintained during the life of the project. The project schedule is to a formal, approved document used to guide both project execution and project control and serves as a roadmap for managing project activities. |
The contractor (vendor) is expected to utilize the SCDHHS PMO project schedule basic template requirements. Use of an Integrated Master Schedule (IMS) may be required to organize and link multiple project schedules.
The primary functions of the project schedule are to document planning assumptions and decisions, facilitate communication among stakeholders, and document approved scope, cost, and schedule baselines
Please refer to the SCDHHS PMO Schedule Management Plan for additional information.
| Item Number |
| D-003 |
| Deliverable Name |
| Decisions, Assumptions, Constraints Lists, and Action Items |
| Type of Data | | | |
| |X| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |X| | Recurring | |
| |_| | Not Applicable (N/A) | |
| Type of Deliverable Due: |X| Submission |_| Adherence | |
| Status | | |
| Initial | | |
| |X| | Preliminary | |_| | Baseline |
| |_| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |_| | Annual Update | |X| | Other: Weekly |
| |_| | Not Applicable (N/A) | | |
| Deliverable Specification |
| The Contractor (Vendor)’s submission of the initial lists for decisions, assumptions, constraints, and actions items are due ten (10) calendar days from the contract start date. They are updated and maintained through project delivery. |
The recurring list updates are due weekly by COB each Thursday Friday.
| Note |
| Recurring decision, assumption, and/or constraint updates are required using the SCDHHS PMO Microsoft Project Web App (PWA) |
| Description |
| Decisions, assumptions, and constraints identified during the life of the project need to be documented and maintained. |
| Item Number |
| D-004 |
| Deliverable Name |
| SCDHHS PMO Project Management Plan (PMP) – |
Risk Management Plan
| Type of Data | | | |
| |X| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |_| | Recurring | |
| |_| | Not Applicable (N/A) | |
| Type of Deliverable Due: |_| Submission |X| Adherence | |
| Status | | |
| Initial | | |
| |_| | Preliminary | |_| | Baseline |
| |X| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |_| | Annual Update | |_| | Other: ________________ |
| |_| | Not Applicable (N/A) | | |
| Deliverable Specification |
| PROJECT KICKOFF + ten (10) calendar days, the Contractor (Vendor) will adhere to the SCDHHS PMO Risk Management Plan requirements as well as the related risk processes and procedures. |
| Note |
| The SCDHHS PMO is the owner of the Risk Management Plan at an Enterprise level. The contractor (vendor) will be notified and provided an updated copy if changes are made to this PMP. |
| Description |
| A risk is an event or condition that, if it occurs, could have a negative effect or create a positive opportunity on the program’s or a project’s objectives. A negative risk is an undesirable or unexpected event that if occurred it would cause an unfavorable impact on the program’s or project’s scope, cost, schedule, technical, and/or quality aspect. A positive opportunity is an event or condition that if occurred could potentially produce a favorable outcome for the program or project. |
The Risk Management Plan defines how risks associated with SCDHHS programs or projects are identified, analyzed, and managed. It outlines how risk management activities are recorded, performed, and monitored throughout the lifecycle of the various projects in the portfolio and provides templates and practices for prioritizing risks by SCDHHS leadership.
The Risk Management Plan also provides standard terminology, clear roles and responsibilities; a detailed description of the risk management process; and the standard templates and tools used in the risk management process. It is designed to guide the PMO, program teams, project teams and other SCDHHS stakeholders for consistent risk management activities.
The primary objective of the risk management process is to ensure that risks are evaluated quantitatively and qualitatively; mechanisms to mitigate or eliminate risks are selected; and the success of the risk mitigation techniques are continuously monitored, measured, and reported.
The Risk Management Plan is a core document for PMO governance activities.
| Item Number |
| D-005 |
| Deliverable Name |
| SCDHHS PMO Project Management Plan (PMP) – |
Issue Management Plan
| Type of Data | | | |
| |X| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |_| | Recurring | |
| |_| | Not Applicable (N/A) | |
| Type of Deliverable Due: |_| Submission |X| Adherence | |
| Status | | |
| Initial | | |
| |_| | Preliminary | |_| | Baseline |
| |X| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |_| | Annual Update | |_| | Other: ________________ |
| |_| | Not Applicable (N/A) | | |
| Deliverable Specification |
| PROJECT KICKOFF + ten (10) calendar days, the Contractor (Vendor) will adhere to the SCDHHS PMO Issue Management Plan requirements as well as the related issue management processes and procedures. |
| Note |
| The SCDHHS PMO is the owner of the Issue Management Plan at an Enterprise level. The contractor (vendor) will be notified and provided an updated copy if changes are made to this PMP. |
| Description |
| An issue is an item or event that has already occurred, therefore it must be acknowledged, managed and resolved immediately. Once identified and implemented, resolutions to any issue have the potential to impact the programs or project’s scope, cost, schedule, technical, and/or quality aspect and therefore may invoke the change management process. |
The Issue Management Plan defines how issues associated with SCDHHS programs or projects are identified, analyzed, and managed. It outlines how issue management activities are performed, recorded, and monitored throughout the lifecycle of the various projects and provides templates and practices for documenting and prioritizing issues by SCDHHS leadership.
The overall goal of issue management is to protect the project from the negative impact of issues or unsatisfactory completion.
The objectives of issue management are as follows:
Ensure issues are documented in a standard and consistent manner Monitor a project to identify new or changing issues Analyze the issue to minimize the cost and other impacts Escalate issues where appropriate to acquire timely resolution Focus management’s attention on higher priority issues Make issue-related decisions at the proper level of authority (i.e. resolution activities, issue transference, closure, etc.)
Communicate clearly about issues with the team and project stakeholders Monitor, measure and report issues in a consistent manner to ensure appropriate management occurs through resolution Maintain a clear and accurate record of issues and related actions over the life of the project The Issue Management Plan is a core document for PMO governance activities.
Item Number
| D-006 |
| Deliverable Name |
| SCDHHS PMO Project Management Plan (PMP) – |
Change Management Plan
| Type of Data | | | |
| |X| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |_| | Recurring | |
| |_| | Not Applicable (N/A) | |
| Type of Deliverable Due: |_| Submission |X| Adherence | |
| Status | | |
| Initial | | |
| |_| | Preliminary | |_| | Baseline |
| |X| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |_| | Annual Update | |_| | Other: ________________ |
| |_| | Not Applicable (N/A) | | |
| Deliverable Specification |
| PROJECT KICKOFF + ten (10) calendar days, the Contractor (Vendor) will adhere to the SCDHHS PMO Change Management Plan requirements as well as the related change management processes and procedures. |
| Note |
| The SCDHHS PMO is the owner of the Change Management Plan at an Enterprise level. The contractor (vendor) will be notified and provided an updated copy if changes are made to this PMP. |
| Description |
| A change is a modification that affects: a project’s baselined scope, schedule, or cost/budget; non-maintenance Information Technology (IT) maintenance related to technical or network infrastructure/systems, databases, etc.; and/or SCDHHS Deputy Area policy-based initiatives which require the discipline of formal change management. |
Change Management is the formal process for identifying and requesting, analyzing, reviewing, escalating, communicating, implementing, monitoring, measuring and reporting of SCDHHS changes in a defined, consistent and repeatable manner.
The change management process provides the mechanism for allowing SCDHHS leadership and other stakeholders to effectively prioritize changes, evaluate progress, manage costs and communicate status of identified changes.
The Change Management Plan outlines how change management activities will be performed, recorded and monitored including documenting and prioritizing approved changes.
The scope of change management includes the following:
Changes provide value to the program or project and are applicable to: Project Schedule, Budget/Cost, and/or Scope;
Non-project changes which includes IT Technical changes considered non-maintenance; and/or SCDHHS Deputy Areas’ policy-based initiatives Changes will follow a defined, repeatable process to ensure routine changes are completed with minimal restrictions while complex, high impact changes receive the necessary oversight.
The Change Management Plan is a core document for PMO governance activities.
| Item Number |
| D-007 |
| Deliverable Name |
| SCDHHS PMO Project Management Plan (PMP) – |
Communications Management Plan
| SCDHHS Owner(s) |
| SCDHHS Approver(s) |
| Vendor Owner(s) |
| Vendor Approver(s) |
| Type of Data | | | |
| |X| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |_| | Recurring | |
| |_| | Not Applicable (N/A) | |
| Type of Deliverable Due: |_| Submission |X| Adherence | |
| Status | | |
| Initial | | |
| |_| | Preliminary | |_| | Baseline |
| |X| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |_| | Annual Update | |_| | Other: ________________ |
| |_| | Not Applicable (N/A) | | |
| Deliverable Specification |
| PROJECT KICKOFF + ten (10) calendar days, the Contractor (Vendor) will adhere to the SCDHHS PMO Communications Management Plan requirements as well as the related communication management processes and procedures. |
| Note |
| The SCDHHS PMO is the owner of the Communications Management Plan at an Enterprise level. The contractor (vendor) will be notified and provided an updated copy if changes are made to this PMP. |
The purpose of the Communications Management Plan is to outline the communication management approach, methodology, and tools used to provide a unified communication framework for sharing accurate information with stakeholders (both internal and external) to ensure the positive impact SCDHHS program and projects in the portfolio. The approved communication management process ensures a defined, documented, repeatable and measurable process exists for successful quality management.
The Communications Management Plan defines how communications associated with SCDHHS programs or projects will be identified, created, approved, managed and distributed. It outlines how communications-related activities will be performed, recorded, and monitored throughout the lifecycle of the various projects and provides templates and practices for documenting and prioritizing communication artifacts by SCDHHS leadership.
The approach to communications management throughout any SCDHHS program and project in the portfolio is intended to be defined for each of two levels;
· Level 1 – Basic Internal SCDHHS-related Communications, and
· Level 2 – Advanced Internal SCDHHS-related Communications and External-facing Communications.
SCDHHS intends to work collaboratively with internal and external stakeholders during the life of the project in order to ensure a seamless approach to communications. Open, ongoing communication between stakeholders is critical to the success of all PMO projects
The Communications Management Plan is a core document for PMO governance activities.
| Item Number |
| D-008 |
| Deliverable Name |
| SCDHHS PMO Project Management Plan (PMP) – |
Scope Management Plan
| Type of Data | | | |
| |X| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |_| | Recurring | |
| |_| | Not Applicable (N/A) | |
| Type of Deliverable Due: |_| Submission |X| Adherence | |
| Status | | |
| Initial | | |
| |_| | Preliminary | |_| | Baseline |
| |X| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |_| | Annual Update | |_| | Other: ________________ |
| |_| | Not Applicable (N/A) | | |
| Deliverable Specification |
| PROJECT KICKOFF + ten (10) calendar days, the Contractor (Vendor) will adhere to the SCDHHS PMO Scope Management Plan requirements as well as the related scope management processes and procedures. |
| Note |
| The SCDHHS PMO is the owner of the Scope Management Plan at an Enterprise level. The contractor (vendor) will be notified and provided an updated copy if changes are made to this PMP. |
| Description |
| Scope Management includes defining a program or project’s scope statement and managing all the approved work, while excluding unnecessary work, through a formal process(es) which includes monitoring, controlling and reporting in a defined, consistent and repeatable manner for successful quality management. |
Scope Management typically follows a five-step process to include:
1) Collect Requirements,
2) Define Scope,
3) Create the work breakdown structure (WBS),
4) Verify Scope, and
5) Monitor and Control Scope.
The purpose of the Scope Management Plan is to outline the scope management approach, methodology, and tools used to define, develop, verify, monitor, control and report scope-related work and components that could impact SCDHHS program and/or projects in the portfolio.
Other program or project components which may directly affect scope management include at a minimum:
· Identifying new or missed requirements
· Changes to the baseline project schedule
· Variation in budget or costs The Scope Management Plan is a core document for PMO governance activities.
| Item Number |
| D-009 |
| Deliverable Name |
| SCDHHS PMO Project Management Plan (PMP) – |
Staff Management Plan
| Type of Data | | | |
| |X| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |_| | Recurring | |
| |_| | Not Applicable (N/A) | |
| Type of Deliverable Due: |_| Submission |X| Adherence | |
| Status | | |
| Initial | | |
| |_| | Preliminary | |_| | Baseline |
| |X| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |_| | Annual Update | |_| | Other: ________________ |
| |_| | Not Applicable (N/A) | | |
| Deliverable Specification |
| PROJECT KICKOFF + ten (10) calendar days, the Contractor (Vendor) will adhere to the SCDHHS PMO Staff Management Plan requirements as well as the related staff management processes and procedures. |
| Note |
| The SCDHHS PMO is the owner of the Staff Management Plan at an Enterprise level. The contractor (vendor) will be notified and provided an updated copy if changes are made to this PMP. |
| Description |
| The purpose of the Staff Management Plan is to outline the staff management approach, methodology and tools used to define, manage, verify, monitor, control and report staff-related components of the SCDHHS program and/or project(s) in the portfolio. The approved staff management process ensures a defined, documented, repeatable and measurable process exists for successful quality management. |
The Project’s Leadership or Designee plans for necessary staff for the duration of the project during the Inception, Concept and Planning Phase of the project. Staff planning and estimating occurs to identify the necessary state and contractor roles needed. In addition, staff planning and estimating identifies each specific role and the role’s timeframe assigned to the project. The staff planning and estimating model directly affects the project’s overall budget.
The plan also describes the planning, acquisition and management of both state staff and consulting or contractor staff and describes the responsibilities assigned to key staff roles.
The Staff Management Plan is a core document for PMO governance activities.
| Item Number |
| D-010 |
| Deliverable Name |
| SCDHHS PMO Project Management Plan (PMP) – |
Cost Management Plan
| Type of Data | | | |
| |X| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |_| | Recurring | |
| |_| | Not Applicable (N/A) | |
| Type of Deliverable Due: |_| Submission |X| Adherence | |
| xStatus | | |
| Initial | | |
| |_| | Preliminary | |_| | Baseline |
| |X| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |_| | Annual Update | |_| | Other: ________________ |
| |_| | Not Applicable (N/A) | | |
| Deliverable Specification |
| PROJECT KICKOFF + ten (10) calendar days, the Contractor (Vendor) will adhere to the SCDHHS PMO Cost Management Plan requirements as well as the related cost management processes and procedures. |
| Note |
| The SCDHHS PMO is the owner of the Cost Management Plan at an Enterprise Level. The contractor (vendor) will be notified and provided an updated copy if changes are made to this PMP. |
| Description |
| The purpose of the Cost Management Plan is to outline the cost management approach, methodology and tools used to identify and estimate costs, analyze expenditures and variances, track and reconcile estimates to invoices, monitor, control and report actual cost/budget expenditures. The approved cost management process ensures a defined, documented, repeatable and measurable process exists for successful quality management. |
Cost management includes estimating, tracking, and controlling expenditures related to all SCDHHS major projects, system-based changes, IT equipment (i.e., infrastructure, hardware, software) and staff (i.e., contract and non-contract) costs.
The Cost Management Plan is a core document for PMO governance activities.
| Item Number |
| D-011 |
| Deliverable Name |
| SCDHHS PMO Project Management Plan (PMP) – |
Schedule Management Plan
| Type of Data | | | |
| |X| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |_| | Recurring | |
| |_| | Not Applicable (N/A) | |
| Type of Deliverable Due: |_| Submission |X| Adherence | |
| Status | | |
| Initial | | |
| |_| | Preliminary | |_| | Baseline |
| |X| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |_| | Annual Update | |_| | Other: ________________ |
| |_| | Not Applicable (N/A) | | |
| Deliverable Specification |
| PROJECT KICKOFF + ten (10) calendar days, the Contractor (Vendor) will adhere to the SCDHHS PMO Schedule Management Plan requirements as well as the related schedule management processes and procedures. |
| Note |
| The SCDHHS PMO is the owner of the Schedule Management Plan at an Enterprise level. The contractor (vendor) will be notified and provided an updated copy if changes are made to this PMP. |
| Description |
| The project schedule is a formal, approved document used to guide both project execution and project control and serves as a roadmap for managing project activities throughout the life of the project. The primary functions of the project schedule are to document planning assumptions and decisions, facilitate communication among stakeholders, and document approved scope, cost, and schedule baselines. Project schedules are an important part of any project as they provide the project team, sponsor, and stakeholders a snapshot of the project’s status at any given time. The approved schedule management process ensures a defined, documented, repeatable and measurable process exists for successful quality management. |
The Schedule Management Plan is a core document for PMO governance activities.
| Item Number |
| D-012 |
| Deliverable Name |
| SCDHHS PMO Project Management Plan (PMP) – |
Requirements Management Plan
| Type of Data | | | |
| |X| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |_| | Recurring | |
| |_| | Not Applicable (N/A) | |
| Type of Deliverable Due: |_| Submission |X| Adherence | |
| Status | | |
| Initial | | |
| |_| | Preliminary | |_| | Baseline |
| |X| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |_| | Annual Update | |_| | Other: ________________ |
| |_| | Not Applicable (N/A) | | |
| Deliverable Specification |
| PROJECT KICKOFF + ten (10) calendar days, the Contractor (Vendor) will adhere to the SCDHHS PMO Requirements Management Plan requirements as well as the related requirements management processes and procedures. |
| Note |
| The SCDHHS PMO is the owner of the Requirements Management Plan at an Enterprise level. The contractor (vendor) will be notified and provided an updated copy if changes are made to this PMP. |
| Description |
| The purpose of the Requirements Management Plan is to outline the requirements management approach, methodology, and tools used to define, manage, verify, monitor, control and report requirements-related components of the SCDHHS program and/or project(s) in the portfolio. The approved requirements management process ensures a defined, documented, repeatable and measurable process exists for successful quality management. |
Requirements Management is the process of gathering, documenting, analyzing, tracing, prioritizing, and validating requirements. This also includes the requirements are implemented in accordance to standards and based on in scope of the program or project. Finally, controlling requirements in a defined, consistent and repeatable manner is inclusive of the requirements management process.
A requirement is a function or capability to which a project outcome should conform and meet the expectations of the customer and internal and external stakeholders. Requirements will be defined and managed throughout the life of the project via requirements traceability.
The Requirements Management Plan is a core document for PMO governance activities.
| Item Number |
| D-013 |
| Deliverable Name |
| SCDHHS PMO Project Management Plan (PMP) – |
Quality Management Plan
| Type of Data | | | |
| |X| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |_| | Recurring | |
| |_| | Not Applicable (N/A) | |
| |_| | Not Applicable (N/A) | |
| Type of Deliverable Due: |_| Submission |X| Adherence | |
| Status | | |
| Initial | | |
| |_| | Preliminary | |_| | Baseline |
| |X| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |_| | Annual Update | |_| | Other: ________________ |
| |_| | Not Applicable (N/A) | | |
| Deliverable Specification |
| PROJECT KICKOFFContract Start Date + ten (10) fifteen (15) calendar days, the Contractor (Vendor) will adhere to the SCDHHS PMO Quality Management Plan requirements as well as the related quality management processes and procedures. |
| Note |
| The SCDHHS PMO is the owner of the Quality Management Plan at an Enterprise level. The contractor (vendor) will be notified and provided an updated copy if changes are made to this PMP. |
| Description |
| The Quality Management Plan details the approach, method, processes and any tools that the QMO will use to independently examine, review and assess SCDHHS project delivery processes. |
This plan describes the approach to measuring the quality of work being performed, assessing compliance and incorporating continuous improvement across the project delivery area. The SCDHHS Quality Management Plan is built for:
Quality Planning Quality Assurance (QA) Quality Control (QC) Quality/Continuous Improvement
A well-established and disciplined quality management framework drastically reduces the risk of failure or unacceptable delays for completion, reduces the number and types of defects, understands the root cause of defects, demonstrates end-to-end requirements traceability, allows for more thorough and results-driven testing and provides thorough documented evidence throughout the life of the project.
All SCDHHS projects are subject to quality reviews. Quality reviews include evaluating services, processes and/or activities provided and comparing evaluation results with the accepted standards. Deviations from stated requirements or acceptable results are considered deficiencies and identified for improvement.
The Quality Management Plan is a core document for PMO governance activities.
| Item Number |
| D-014 |
| Deliverable Name |
| SCDHHS PMO Project Management Plan (PMP) – |
Contractor Management Plan
| Type of Data | | | |
| |X| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |_| | Recurring | |
| |_| | Not Applicable (N/A) | |
| Type of Deliverable Due: |_| Submission |X| Adherence | |
| Status | | |
| Initial | | |
| |_| | Preliminary | |_| | Baseline |
| |X| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |_| | Annual Update | |_| | Other: ________________ |
| |_| | Not Applicable (N/A) | | |
| Deliverable Specification |
| PROJECT KICKOFF + ten (10) calendar days, the Contractor (Vendor) will adhere to the SCDHHS PMO Contractor Management Plan requirements as well as the related contractor management processes and procedures. |
| Note |
| The SCDHHS PMO is the owner of the Contractor Management Plan at an Enterprise level. The contractor (vendor) will be notified and provided an updated copy if changes are made to this PMP. |
| Description |
| SCDHHS has many contractors (i.e., contractor(s) engaged to provide approved services in accordance with their specific contract terms. A contractor’s scope of work (SOW) may be integrated with other contractors’ SOW with the goal for SCDHHS to have a fully integrated and successfully operational State Medicaid Agency (SMA). |
Having consistent and well-defined deliverables and a process to manage these deliverables are critical for effective contractor management as well as successful project delivery. To this end, SCDHHS must identify and manage the contractor’s contracted deliverables throughout the life of the project.
The Contractor (Vendor) Management Plan identifies the process, procedures and tools used to identify and manage deliverables during the life of the project and includes this Consolidated Deliverables Management List and contains the SCDHHS Deliverables Management process.
An approved deliverables management process ensures a defined, documented, repeatable and measurable process exists for successful quality management.
The Contractor (Vendor) Management Plan is a core document for PMO governance activities.
| Item Number |
| D-015 |
| Deliverable Name |
| Requirements Document (RD) |
| SCDHHS Owner(s) |
| SCDHHS Approver(s) |
| Vendor Owner(s) |
| Vendor Approver(s) |
| Type of Data | | | |
| |X| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |_| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |_| | Recurring | |
| |_| | Not Applicable (N/A) | |
| Type of Deliverable Due: |X| Submission |_| Adherence | |
| Status | | |
| Initial | | |
| |X| | Preliminary | |_| | Baseline |
| |X| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |_| | Annual Update | |_| | Other: ________________ |
| |X| | Not Applicable (N/A) | | |
| Deliverable Specification |
| Ten (10) business days after beginning the Requirements and Analysis, the Contractor (Vendor) will provide preliminary Requirements Document to SCDHHS for review. The final version is due ten (10) business days before the Design Phase begins. SCDHHS needs to review and approve prior to the Contractor (Vendor) commencing the Design Phase. |
Note
| Description |
| The purpose of the Requirements Document (RD) is to provide full identifying information related to the automated system, application or project’s business case for which the RD applies. Pursuant to the scope located on the Intake Request Form and/or Project Charter, the requirements identified will provide internal stakeholders a narrative of the intended requirements’ information, both business and technical and any links to external documentation. A sanitized version of the RD may be provided to external stakeholders with the approval of the project’s leadership. |
The RD also provides a summary of the tools which will used to enter, store and manage business requirements, business rules, user requirements and functional and non-functional requirements for the project through to traceability.
| Item Number |
| D-016 |
| Deliverable Name |
| Turnover Plan |
| SCDHHS Owner(s) |
| SCDHHS Approver(s) |
| Vendor Owner(s) |
| Vendor Approver(s) |
| Type of Data | | | |
| |_| | Governance or Project Management | |_| | Other: ___________________________________ |
| |_| | Security | |X| | Transition to Operations (Post-Implementation) | |
| |_| | Systems/Software Development | | | |
| Submission Due Indicator | |
| |X| | Initial |
| |_| | Recurring | |
| |_| | Not Applicable (N/A) | |
Type of Deliverable Due: |X| Submission |_| Adherence
| Status | | |
| Initial | | |
| |X| | Preliminary | |_| | Baseline |
| |_| | Final | | |
| |_| | Not Applicable (N/A) | | |
| Recurring | | |
| |X| | Annual Update | |_| | Other: __________________ |
| |_| | Not Applicable (N/A) | | |
| Deliverable Specification |
| Six (6) months Three (3) prior to the end of the first calendar year of operationsinitial Contract period, automatic renewal, or any extension thereof, the Contractor (Vendor) will provide preliminary Turnover Plan to SCDHHS for review. SCDHHS needs to review and approve prior to the completion of the first calendar year of operations. The Turnover Plan will be updated minimally on an annual basis. |
Note
| Description |
| The Turnover Plan describes the activities needed to ensure an uninterrupted and transparent turnover at the completion of the Contractor (Vendor)’s Contract. |
This plan shall describe the activities that will be performed to ensure that required system and operational knowledge is transferred to the new Contractor (Vendor). This includes the conversion and migration of all pertinent information and work in progress, leases, etc. Additionally, the plan shall discuss roles and responsibilities of the organizations and the workflow between the current Contractor (vendor) and new Contractor (Vendor). High-level timelines and contingency plans should be included.
V6.0 20180124 SCDHHS – (Enter Vendor Name) - Confidential Page 2 of 49 image1.png