CMMI-DEV Measurement and Analysis
Get Started with This SkillOverview
Draft CMMI-DEV Measurement and Analysis (MA) deliverables: measurement plan, analysis reports, and measurement repository structure for ML2.
Getting Started
Add your source materials to the project workspace, then activate the CMMI-DEV Measurement and Analysis skill. The agent will guide you through the process step by step.
Example Conversation
You: We need a measurement plan for our CMMI MA process area. We want to track effort, schedule variance, and defect density. Can you draft the plan and a sample analysis report structure?
Agent: I’ll draft a Measurement Plan aligned to CMMI MA: measurement objectives (effort, schedule, quality); operational definitions for each measure; data collection (who, when, where); repository structure; and analysis/reporting schedule. I’ll also add a one-page analysis report template.
You: Add a section on how we use the results for project monitoring.
Agent: I’ve added “Use of results” — how monthly analysis feeds into PMC status reviews and corrective action decisions. The plan is in
measurement-plan.mdand the report template inanalysis-report-template.md.
Sample Output Excerpt
Excerpt from a Measurement Plan produced with this skill.
2. Measures and operational definitions
| Measure | Type | Definition | Unit |
|---|---|---|---|
| Actual effort | Base | Labor hours charged to the project per week | hours |
| Schedule variance | Derived | (Planned completion date − Actual/Baseline completion date) for milestones | days |
| Defect density | Derived | Defects found in verification/validation ÷ size (e.g. story points or KLOC) | defects/unit |
3. Data collection and storage
- Actual effort: Collected weekly from timesheet system; stored in measurement repository with project ID, week, and phase.
- Schedule variance: Computed at milestone completion; stored with milestone ID and date.
- Defect density: Defects from defect tracking; size from backlog/source; computed per release or phase.