CMMI-DEV Quantitative Project Management
Get Started with This SkillOverview
Draft CMMI-DEV Quantitative Project Management (QPM) deliverables: quantitatively managed plan and quality/process performance objectives for ML4.
Getting Started
Add your source materials to the project workspace, then activate the CMMI-DEV Quantitative Project Management skill. The agent will guide you through the process step by step.
Example Conversation
You: We need a quantitatively managed project plan for CMMI QPM. We have quality and process performance objectives (defect density, cycle time) and we use the org’s process performance baselines. Can you draft the plan?
Agent: I’ll draft a Quantitatively Managed Project Plan: quality and process performance objectives (from org or project); which subprocesses we’ll manage statistically; measures and data collection; use of organizational process performance baselines/models; thresholds and criteria for intervention; and how we’ll take corrective action when performance deviates. I’ll align with CMMI QPM.
You: We statistically manage code review and test; our objective is defect density ≤ 2 per KLOC and cycle time ≤ 5 days per story. Threshold for action: 2 consecutive sprints above target.
Agent: I’ve documented objectives (defect density ≤ 2/KLOC, cycle time ≤ 5 days), selected subprocesses (code review, test), measures and collection, and the “2 consecutive sprints above target” as the trigger for root cause analysis and corrective action. The plan is in
quantitatively-managed-plan.md.
Sample Output Excerpt
Excerpt from a Quantitatively Managed Project Plan produced with this skill.
Quality and process performance objectives
| Objective | Target | Measure | Subprocess(es) |
|---|---|---|---|
| Defect density | ≤ 2 defects per KLOC | Defects in V&V / size (KLOC) | Verification, Validation |
| Cycle time | ≤ 5 days per story (average) | Story completion date − start date | Development, integration |
Statistical management and corrective action
- Data collection: Weekly: defects by phase, story cycle times. Size (KLOC or story points) at release.
- Baselines: Use organizational process performance baselines for comparison; control charts or equivalent for trend.
- Threshold: If defect density or cycle time exceeds target for 2 consecutive sprints, trigger root cause analysis and corrective action plan. Document in project records and update plan as needed.