Attachment_I.xlsx
XLSX spreadsheet 30 KB Posted
- Attached to
- Comprehensive Child Welfare Information System
- Solicitation number
- 2000018525
- Issued by
- Ramsey County, Minnesota
About this file
This is a Requirements Traceability Matrix (RTM) attachment for the Comprehensive Child Welfare Information System (CCWIS) Design, Development, and Implementation (DDI) project, jointly procured by the Minnesota Department of Information Technology Services (MNIT) and the Department of Children, Youth, and Families (DCYF). The document outlines non-functional project management requirements and minimum deliverables that responding vendors must address in their proposals. The RTM is organized into two primary sections: PM1 covering project management requirements across governance, evaluation, deliverables, quality controls, communication, resource management, and risk management; and PM2 specifying 40 minimum deliverables required throughout the project lifecycle. Responders are required to complete and submit this attachment as an MS Excel file, indicating with a "Y" or "N" response code whether each requirement will be met by their proposed solution.
The project management requirements emphasize PMI best practices and a hybrid-Agile methodology, mandating a full-time PMI-certified Project Manager and collaborative oversight with the State's CCWIS Project Director. Key deliverables include project governance documents, work breakdown structures, project management plans, status reports, testing and training materials, security and compliance documentation, cutover and rollout plans, and disaster recovery and business continuity plans. The document specifies that all deliverables must be submitted to an Independent Verification and Validation (IV&V) team for quality control review within State-defined timeframes, with weekly status reporting required to the CCWIS Project Director and bi-weekly performance monitoring reports across multiple project dimensions including scheduling, requirements, configuration, data conversion, training, and operational readiness.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment_J.xlsx | XLSX spreadsheet | |
| Sample_Contract.docx | DOCX document | |
| Attachment_E.docx | DOCX document | |
| Attachment_N.docx | DOCX document | |
| CCWISRFP.pdf | ||
| Comprehensive_Child_Welfare_Information_System.pdf | ||
| Attachment_F.docx | DOCX document | |
| Attachment_L.docx | DOCX document | |
| Attachment_K.docx | DOCX document | |
| Attachment_B.docx | DOCX document | |
| Attachment_M.docx | DOCX document | |
| Attachment_G.xlsx | XLSX spreadsheet | |
| Attachment_C.xlsx | XLSX spreadsheet | |
| Attachment_H.xlsx | XLSX spreadsheet | |
| Exhibit_A_Supplement_1_Prevailing_Wage_Rates.pdf | ||
| Attachment_O.docx | DOCX document | |
| Attachment_D.pdf | ||
| Attachment_A.docx | DOCX document |
Show all 18
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Introduction Attachment I: DDI Project Management Services Requirements Traceability Matrix (RTM)
| Introduction |
| This document captures the Project Managment Non-Functional Requirements for the DCYF's CCWIS Project. |
Within this document, the requirements are categorized by area as detailed below. Each category has its own tab in this workbook.
| ID | CCWIS Project Management Requirements Section Titles |
| PM | Requirement Section |
| PM1 | Project Management |
| PM2 | List of Minimum Deliverables |
Responder Instructions
| Responder Instructions |
| This workbook contains Requirements for the CCWIS system. The response codes below should be used by Responders to indicate the fit of its solution to the State Requirements specified in this workbook. |
This attachment should be completed and submitted as an MS Excel file as part of the response to this RFP.
| Responses | Definition |
| Response Code: Y or N -- Will this Non-Functional Requirement be met by your solution? | Indicate whether the requirement, as currently written, will be met by the Respondent's proposal. Respond Y=Yes or N=No. |
PM1 Project Management Req # Requirement Subcategory Requirement Description Response Code (Y,N)
| PM1.1 | Project Governance & Management Approach | In collaboration with the Comprehensive Child Welfare Information System (CCWIS) Project Director, create a Scope Statement as part of the joint Project Management Plan (PMP) that defines what is in and out of scope for the Project, provides an updated list of requirements, and includes entrance and exit criteria for each project phase in accordance with the State's Project Management Methodology. |
| PM1.2 | Project Governance & Management Approach | Provide at least one full-time Project Manager for project management activities and coordination with the Comprehensive Child Welfare Information System (CCWIS) Project Director on project-related decisions. Require the Project Manager to maintain Project Management Institute (PMI) certification, such as Project Management Professional (PMP) or PMI Agile Certified Practitioner (PMI-ACP). |
| PM1.3 | Project Governance & Management Approach | Provide a robust Project Management methodology founded on industry best practices and covering all key project management processes. DCYF prefers a hybrid-Agile project management methodology. |
| PM1.4 | Project Governance & Management Approach | Establish and carry out Design, Development, and Implementation (DDI) project management planning and implementation services in coordination with the State's approved Project Management Office, aligned with Project Management Institute (PMI) best practices. |
| PM1.5 | Project Governance & Management Approach | Provide a Final Project Close-Out Checklist that includes exit criteria for closing the project and entrance criteria for moving the CCWIS System to Sustainable Support. |
| PM1.6 | Project Evaluation | Create, maintain, and update CCWIS project evaluation dashboards in alignment with software development lifecycle activities, State-defined reporting needs, and Department of Children, Youth, and Families (DCYF)/Minnesota IT Services (MNIT) CCWIS project evaluation objectives. |
| PM1.7 | Project Evaluation | Provide DDI vendor team personnel access to information, meetings, documentation, and System data needed to participate in DCYF/MNIT CCWIS project evaluation activities, subject to State-defined access, security, confidentiality, and audit requirements. |
| PM1.8 | Project Evaluation | Provide State Authorized Users with access to global System data needed to support DCYF/MNIT CCWIS project evaluation activities, subject to State-defined access, security, confidentiality, and audit requirements. |
| PM1.9 | Project Evaluation | Provide State Authorized Users with access to user-level System data needed to support DCYF/MNIT CCWIS project evaluation activities, subject to State-defined access, security, confidentiality, and audit requirements. |
| PM1.10 | Deliverables, Reviews & Approvals | In collaboration with the CCWIS Project Director, create a Work Breakdown Structure (WBS) that outlines project phases, deliverables, and work packages from planning through implementation within State-defined timeframes. |
| PM1.11 | Deliverables, Reviews & Approvals | Manage day-to-day project personnel activities, including subcontractor personnel activities, and lead development of deliverables related to the required services. |
| PM1.12 | Deliverables, Reviews & Approvals | Provide a Deliverables Expectation Document (DED) for approval by the CCWIS Project Director and review by Independent Verification and Validation (IV&V) for all project and software deliverables before development begins. |
| PM1.13 | Deliverables, Reviews & Approvals | Follow the Deliverable Review and Approval process defined by the State. |
| PM1.14 | Deliverables, Reviews & Approvals | Support State review and approval processes for project planning, deliverables, readiness decisions, and implementation activities. |
| PM1.15 | Quality, Compliance & Administrative Controls | Collaborate with the CCWIS Project Director to create the CCWIS Project Management Plan aligned with Project Management Institute (PMI) standards and reflective of the joint project management processes used to manage the project. Include, at a minimum, the following: |
• Project schedule
• Implementation plan
• Risk management plan, including issue and risk identification, impact quantification, monitoring, and mitigation planning
• Deliverable review and acceptance processes and other acceptance criteria
• Requirements management plan, including the process and tools used for functional and technical requirements tracking, maintenance, and traceability in the requirements traceability matrix (RTM)
• Quality management process
• Resource management for project and subcontractor resources
• Project success evaluation criteria and project closeout activities
• Identification and management of relationships to other information technology (IT) or business efforts
• Status report templates, including deliverable status reports, issues, risks, and plan-versus-actual status, as identified by the State
• Status and other reporting activities identified by the State
• Tools used for project management processes, including change management, documentation management, and issue and risk management
| PM1.16 | Quality, Compliance & Administrative Controls | Submit all deliverables to the Independent Verification and Validation (IV&V) team for quality control review within State-defined timeframes as part of the deliverable review process. |
| PM1.17 | Communication, Reporting & Stakeholder Coordination | Include the Independent Verification and Validation (IV&V) Project Team in all project meetings and allow access to project management tools, schedule tools, and any other data, software, or deliverables requested by the CCWIS Project Director. |
| PM1.18 | Communication, Reporting & Stakeholder Coordination | Provide a weekly status report to the CCWIS Project Director that includes metrics specific to schedule including work completed and work remaining, in hours or another approved denomination, deliverable status and variances, resources changes, and needed State resources. Timelines and content are at the discretion of the CCWIS Project Director. |
| PM1.19 | Communication, Reporting & Stakeholder Coordination | Provide a Cutover Plan for the 14 days prior to CCWIS go-live, including applicable weekend activities. Include, at a minimum, the following: |
• Communication plan
• Notifications to Authorized Users
• Roles and responsibilities
• Testing schedule
• Data conversion
• Defect resolution
• Service Desk responsibilities
• Rollout schedule
• Entrance and exit criteria
| PM1.20 | Resource, Staffing & Workforce Management | Update schedule milestones, deliverables, tasks, and work remaining on a weekly basis, or at the discretion of the Project Director, in hours or another approved denomination for resources that have dependencies on the CCWIS Project Team in the CCWIS Project Master Schedule. Define details in the Schedule Management Plan. |
| PM1.21 | Resource, Staffing & Workforce Management | Provide a CCWIS Rollout Plan within the State-defined timeframe before System go-live that defines the preparation and planning needed for implementation. Include, at a minimum, the following: |
• Roles and responsibilities
• Decision authority and escalation processes
• Rollout strategy
• High-level rollout schedule
• Risks and mitigations
• Testing plan
• Needed State resources
• Impact to State offices
• Entrance and exit criteria
• Rollback plan
| PM1.22 | Resource, Staffing & Workforce Management | Include in the integrated CCWIS Master Project Schedule the number, knowledge, and skill levels of resources needed to support Project activities and deliverables. |
| PM1.23 | Risk, Issue, Decision & Change Management | Manage risks and issues in the CCWIS Project, including providing detailed risk mitigations for all Independent Verification and Validation (IV&V) observations related to project management or system development activities within two weeks after the State approves the IV&V Monthly Project Assessment Report. |
PM2 Minimum Deliverables Req # Requirement Description Response Code (Y,N)
| PM2.1 | Deliverable Expectation Document (DED) CCWIS Bi-weekly Project Status Report |
| PM2.2 | CCWIS Bi-weekly Project Status Reports |
| PM2.3 | CCWIS Project Deliverable DEDs |
| PM2.4 | CCWIS Deliverable Review and Approval Plan |
| PM2.5 | CCWIS Configuration and Implementation Strategy and Methodology |
| PM2.6 | CCWIS System Architecture |
| PM2.7 | CCWIS Project Management Plan as defined by the Project Management Institute (PMI) unless plan is scheduled at a different time |
| PM2.8 | CCWIS Detailed Vendor Project Schedule |
| PM2.9 | CCWIS Detailed Scope Definition, including at a minimum a detailed Work Breakdown Structure (WBS) |
| PM2.10 | CCWIS Integrated Master Project Schedule |
| PM2.11 | CCWIS Bi-weekly Project Performance Monitoring, Metrics, and Control Reports for the schedule and requirements |
| PM2.13 | CCWIS Data Exchange / Interface Plan |
| PM2.14 | Rational Data Model (RDM) comprised of both Physical (PDM) and Logical (LDM) data models for the both the “Current-State legacy system and the “To-Be” modernized CCWIS system |
| PM2.15 | CCWIS Data Dictionary |
| PM2.16 | CCWIS Data Conversion and Migration Plan |
| PM2.17 | CCWIS Bi-weekly Project Performance Monitoring, Metrics, and Control Reports for the configuration, data exchanges, and conversion |
| PM2.18 | Catalog of Requirements for Federal Reports |
| PM2.19 | CCWIS Federal Report Plan |
| PM2.20 | CCWIS Federal Reports Design Documents |
| PM2.21 | CCWIS UAT Test Support Plan |
| PM2.22 | CCWIS Testing Methodology and Master Plan |
| PM2.23 | CCWIS Training Plan |
| PM2.24 | CCWIS Training Materials |
| PM2.25 | CCWIS Bi-weekly Project Performance Monitoring, Metrics, and Control Reports for Training and Operational Readiness |
| PM2.26 | CCWIS Security Plan |
| PM2.27 | Update to the Security requirements, reflecting all NIST and other compliance requirements as well as proposed best practices standards |
| PM2.28 | Documentation that the Responder is Cloud Access Service Broker (CASB) |
| PM2.29 | Documentation that the Responder’s Solution is in compliance with multi-factor authentication and ransomware management practices |
| PM2.30 | CCWIS Service Level Agreement (SLA) with security metrics consistent with NIST SP 800-55 v1 or CIS Consensus Security Metrics V1.1.0 |
| PM2.31 | CCWIS Cutover Plan |
| PM2.32 | CCWIS Sustainability Support Plan |
| PM2.33 | CCWIS Disaster Recovery Plan |
| PM2.34 | CCWIS Business Continuity Plan |
| PM2.35 | CCWIS Maintenance Operations Manual |
| PM2.36 | CCWIS Support Service Level Agreements |
| PM2.37 | CCWIS Final Project Close-Out Checklist |
| PM2.38 | CCWIS Service Catalog |
| PM2.39 | CCWIS Vendor Transition Plan |
| PM2.40 | Final Acceptance Document |
File details come from the government source that posted it. Updated .