# CMMI-DEV Causal Analysis and Resolution

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



Tags: CMMI, CMMI-DEV, Process Improvement, Causal Analysis, ML5


## Example Prompts

- Conduct causal analysis for a significant defect and document root cause
- Draft action proposals from causal analysis for CMMI CAR
- Document causal analysis and action implementation results

URL: https://rakenne.app/skills/cmmi-dev-causal-analysis-resolution/index.md

Try this skill: https://rakenne.app/a/?skill=cmmi-dev-causal-analysis-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

| Root cause | Contributing factors | Analysis method |
|------------|----------------------|-----------------|
| No formal interface freeze | Late interface spec changes; ad hoc integration order | 5 Whys |
| Vendor not on critical path with buffer | Vendor milestones not tracked; no escalation path | 5 Whys |

### Action proposals

| ID | Action | Owner | Success criteria |
|----|--------|-------|-------------------|
| AP-1 | Establish interface freeze milestone and change control for interfaces after freeze | Tech Lead | Interface change requests after freeze in next release: 0 or approved exception |
| AP-2 | Add vendor milestones to project plan with buffer; weekly vendor status in risk review | PM | Vendor delay risk identified and mitigated before slip |


---

Back to [Skill Library](https://rakenne.app/skills/index.md)