CMMI-DEV Configuration Management
Get Started with This SkillOverview
Draft CMMI-DEV Configuration Management (CM) deliverables: configuration management plan, baselines, and change request/status documentation for ML2.
Getting Started
Add your source materials to the project workspace, then activate the CMMI-DEV Configuration Management skill. The agent will guide you through the process step by step.
Example Conversation
You: We need a configuration management plan for our CMMI ML2 appraisal. Our project uses Git for code, Confluence for docs, and we have requirements and design baselines. Can you draft the CM plan?
Agent: I’ll draft a Configuration Management Plan aligned to CMMI CM. I’ll cover: (1) configuration items — code (Git), requirements baseline, design baseline, and key project docs in Confluence; (2) identification scheme and baselines; (3) change control process and status accounting; (4) roles. Loading the CM process area reference to align with specific practices.
You: Yes, and we use a CCB for requirements and design changes; code uses MR + review.
Agent: I’ve created
configuration-management-plan.mdwith: configuration items and storage (Git repos, Confluence spaces, baseline docs); baseline definitions (Requirements v1.0, Design v1.0) and approval authority; change control — requirements/design via CCB, code via merge request and peer review; status accounting (release tags, baseline change log); and configuration audit approach. I can add a change request template or expand the audit section if you want.
Sample Output Excerpt
Below is an excerpt from a Configuration Management Plan produced with this skill.
3. Configuration Baselines
| Baseline | Configuration items | Approval authority | Establishment |
|---|---|---|---|
| Requirements v1.0 | Requirements specification, traceability matrix | Product Owner + Tech Lead | End of elaboration |
| Design v1.0 | Architecture doc, interface specs, design docs | Tech Lead | End of design phase |
| Product release | Tagged code, release notes, deployed config | Release Manager | Per release |
4. Change Control
- Requirements / design: Change requests submitted via Jira; reviewed by CCB (weekly). Approved changes update baseline docs and change log.
- Code: Changes via merge requests; peer review required; main branch protected. Release tags created per release.
- Status accounting: Git tags and release notes; Confluence baseline change log; CCB minutes for baseline changes.