CMMI-DEV Requirements Management

Overview

Draft CMMI-DEV Requirements Management (REQM) deliverables: requirements baseline, traceability, and change requests for ML2.

Getting Started

Add your source materials to the project workspace, then activate the CMMI-DEV Requirements Management skill. The agent will guide you through the process step by step.

Example Conversation

You: We need to document our requirements baseline and traceability for CMMI REQM. We use Jira for requirements and Confluence for the traceability matrix. Can you draft a short REQM procedure and a traceability matrix template?

Agent: I’ll draft a procedure covering: how the requirements baseline is established and placed under change control; how we maintain traceability (requirements ↔ design, test, project plan); and how we handle requirements changes (request, impact analysis, approval). I’ll add a traceability matrix template (Req ID, description, design ref, test ref, status).

You: Our CCB approves requirement changes; we need impact on schedule and design.

Agent: I’ve added CCB as the approval authority and made “Impact on schedule and design” a required part of the change request. The procedure is in reqm-procedure.md and the matrix template in traceability-matrix-template.md.

Sample Output Excerpt

Excerpt from a traceability document produced with this skill.

Requirements traceability matrix (excerpt)

Baseline: Requirements v1.2, approved by CCB 2025-01-15. Changes via change request; impact on design and schedule required.