CMMI-DEV Causal Analysis and Resolution

Overview

Draft CMMI-DEV Causal Analysis and Resolution (CAR) deliverables: causal analysis reports and action proposals for ML5.

Getting Started

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

Example Conversation

You: We had a significant release delay and want to do a causal analysis for CMMI CAR. The delay was due to integration issues and late vendor delivery. Can you draft the causal analysis report and action proposals?

Agent: I’ll draft a Causal Analysis report: outcome (release delay), data (timeline, causes mentioned), root cause analysis (e.g. 5 Whys or fishbone: integration issues → why? → interface churn, late specs; vendor delay → why? → …), and root causes. Then I’ll propose actions to address each root cause (process or technical) and an implementation/validation plan. I’ll align with CMMI CAR.

You: We think root causes are: no formal interface freeze, and we didn’t have vendor milestones in the critical path. Propose actions for both.

Agent: I’ve written the causal analysis report with those two root causes and contributing factors. Action proposals: (1) Define interface freeze milestone and change control for interfaces after freeze; (2) Add vendor milestones to project schedule with buffer; track vendor in weekly risk review. The report and action plan are in causal-analysis-release-delay.md and action-proposals.md. I can add validation criteria (e.g. next release on time).

Sample Output Excerpt

Excerpt from a Causal Analysis Report produced with this skill.

Outcome

Release delayed by 4 weeks. Primary symptoms: integration rework in final 3 weeks; vendor delivery 2 weeks late for mobile component.

Root cause analysis

Action proposals