CMMI-DEV Workspace: From Ad Hoc to Appraised in 22 Process Areas

Preparing for a CMMI-DEV appraisal is one of the most documentation-intensive undertakings in software engineering. A first-time ML3 appraisal typically requires 12–18 months of process improvement work, with organizations documenting 18 process areas across project management, engineering, and organizational disciplines. The bottleneck is rarely knowing what to write — it is translating real engineering practices into the structured, evidence-based documentation that a SCAMPI Lead Appraiser expects to see.

Rakenne’s CMMI-DEV Process Improvement workspace template provides 22 specialized skills covering every CMMI-DEV v2.0 process area from Maturity Level 2 through 5. Each skill enforces a structured workflow, loads CMMI-specific references, and uses deterministic tools to check the agent’s output — catching the kinds of errors that plain LLM drafting misses: incomplete generic practices, orphaned work products, inconsistent terminology between project-level and organizational-level documents, and missing traceability between process descriptions and actual artifacts.

This guide walks through all 22 process areas in maturity-level sequence, shows real dialog excerpts from a live session, and explains what makes tool-assisted process documentation materially better than generic AI drafting or template-based approaches.

Why plain LLMs fall short for CMMI

A plain LLM can draft process descriptions, procedures, and plans. Where it struggles is appraisal-grade rigor:

The difference is structural: skills give the agent a spec (workflow + CMMI references + expected work products) and tools (deterministic checks) to verify its own output. This is what turns a draft into appraisal-ready evidence.

Maturity levels: a progressive journey

Unlike ISO frameworks that are pass/fail, CMMI-DEV is a maturity progression. Each level builds on the one below:

The workspace template installs all 22 skills but adapts to your target. When you tell the agent “our target is ML3”, it scopes the workflow to 18 process areas and calculates completion accordingly.

The 22-process-area journey

Maturity Level 2 — Managed: establishing project discipline

Step 1: Project Planning — the foundation everything else references

Every CMMI engagement starts with Project Planning. The PP skill produces a project plan that PMC, IPM, and RSKM all reference — making it the foundational artifact of the entire process area hierarchy.

Step 2: Requirements Management — maintaining the baseline

The Requirements Management skill establishes a requirements baseline with bidirectional traceability. It ensures that every requirement is tracked from source (customer need) through implementation to verification — the chain that appraisers follow.

Step 3: Configuration Management — controlling what you build

Steps 4–7: completing ML2

The remaining ML2 process areas follow the same pattern:

• Project Monitoring & Control (PMC) — defines earned value tracking procedures, status report templates, and corrective action triggers. The validation suite checks that monitoring frequency aligns with project milestones and that corrective action plans reference specific PP baselines.

• Process & Product Quality Assurance (PPQA) — produces the QA plan with audit schedules, checklists, and noncompliance escalation procedures. The objectivity checker verifies that QA auditors are independent from the work they review.

• Measurement & Analysis (MA) — establishes measurement objectives aligned to project and organizational goals, defines data collection procedures, and creates the measurement repository schema. The alignment checker verifies that every metric traces to a stated information need.

• Supplier Agreement Management (SAM) — documents supplier agreements, SOWs, and acceptance criteria. Only applicable if the organization uses external suppliers; the agent skips this if it learns no suppliers are in scope.

After completing all 7 ML2 process areas, the dashboard shows:

Maturity Level 3 — Defined: standardizing across the organization

ML3 is where the biggest shift happens. Instead of each project defining its own processes, the organization establishes standard processes that projects then tailor. This is also where most organizations target their first CMMI appraisal.

Step 8: Organizational Process Definition — the standard process library

OPD is the foundation of ML3. It produces the organization’s standard process set, tailoring guidelines, and process asset library — the artifacts that every project will reference through IPM.

Step 9: Organizational Process Focus — driving improvement

Steps 10–18: building the engineering and support processes

The remaining ML3 process areas build on OPD’s standard processes:

• Organizational Training (OT) — needs analysis identifies 4 training audiences (project managers, developers, QA engineers, process group) with role-specific curricula. Competency records track completion.

• Integrated Project Management (IPM) — takes the ML2 project plan and aligns it with organizational standards. The tailoring rationale checker verifies that every deviation from the standard process is documented and approved.

• Requirements Development (RD) — extends REQM by eliciting stakeholder needs, deriving customer requirements, and allocating to product components. The allocation completeness checker verifies every requirement traces to at least one component.

• Technical Solution (TS) — selects and designs solutions. The decision rationale checker verifies that alternative evaluations use defined criteria and that design decisions are traceable to requirements.

• Product Integration (PI) — plans the integration sequence, defines interface management procedures, and establishes the build environment. The integration sequence validator checks that dependencies are respected.

• Verification (VER) — plans verification methods (peer reviews, testing, analysis) for each work product. The peer review coverage checker verifies that all critical work products have scheduled reviews with defined entry/exit criteria.

• Validation (VAL) — ensures the product works in its intended operational environment. The validation environment checker verifies that test conditions represent real operational scenarios.

• Risk Management (RSKM) — extends ML2’s basic risk identification into a systematic risk management strategy. The risk taxonomy checker verifies comprehensive coverage across technical, programmatic, and business risk categories.

• Decision Analysis & Resolution (DAR) — formalizes significant decisions. The criteria weighting checker verifies that evaluation criteria are explicitly weighted and that scores are consistently applied across alternatives.

Maturity Level 4 — Quantitatively Managed: statistical process control

ML4 adds statistical rigor. Most organizations reach ML4 only after operating at ML3 for 1–2 years, accumulating enough measurement data to establish meaningful baselines.

Step 19: Organizational Process Performance — establishing baselines

Step 20: Quantitative Project Management — using baselines for decisions

QPM applies the OPP baselines to active project management, using statistical techniques to detect process instability and predict outcomes.

Maturity Level 5 — Optimizing: continuous improvement

ML5 closes the loop with systematic root cause analysis and strategic performance management.

Step 21: Causal Analysis & Resolution — fixing the system, not just the symptom

Step 22: Organizational Performance Management — strategic improvement

OPM completes the CMMI journey by aligning process improvement with business objectives and deploying innovations across the organization.

Cross-process-area traceability: the appraiser’s perspective

SCAMPI Lead Appraisers don’t evaluate process areas in isolation — they trace chains. “Show me the organizational standard process. Show me how this project tailored it. Show me the measurement data that proves it works.” If one link breaks, the appraiser rates the goal as unsatisfied.

Rakenne’s cross-PA validation tools enforce these links automatically:

• Project Plan → Organizational Standards: IPM’s tailoring rationale checker verifies that every project process references the OPD standard and documents deviations
• Requirements → Design → Verification: The traceability chain from RD through TS to VER is checked bidirectionally — every requirement has a design element, every design element has a verification method
• Measurement Data → Baselines: MA data feeds OPP baselines; the statistical validity checker ensures baselines are derived from sufficient, representative data
• QA Findings → Process Improvement: PPQA audit findings feed OPF improvement plans; the reconciliation checker ensures no finding is orphaned
• Risk Register → Project Plan: RSKM risks cross-reference PP risk sections; the alignment checker ensures consistency

When you run the appraisal readiness assessment after completing all process areas, these checks aggregate into a single readiness score — broken down by CMMI category (Project Management, Engineering, Process Management, Support, High Maturity).

The dashboard: tracking progress across maturity levels

As each skill completes, the agent updates the project dashboard. The dashboard provides a single view of process improvement progress:

Key metrics tracked:

• Program Completion — percentage of process areas completed for the target maturity level
• Target vs. Current Maturity Level — where you’re aiming vs. where you are
• ML2/ML3/ML4/ML5 Completion — per-level progress bars
• Process Area Capability — radar chart showing current vs. target capability ratings across all PAs
• Documents Produced — total output artifacts
• Risk Distribution — breakdown by severity
• Improvement Actions — open vs. closed from OPF
• Appraisal Readiness — weighted composite score across 5 categories

The dashboard adapts to the target maturity level. If you’re targeting ML3, the ML4 and ML5 progress bars show as “Not in scope” rather than penalizing you for incomplete high-maturity process areas.

Effort comparison: consultant time with and without tool assistance

Based on typical CMMI consulting effort breakdowns for first-time ML3 appraisal preparation:

The heaviest activities (process definition, project documentation, evidence collection) are exactly where the validation tools add the most value — not by replacing consultant judgment, but by catching the structural gaps and traceability breaks that consume review cycles and lead to “Not Satisfied” ratings.

Getting started

1. Create a new project in Rakenne and select the CMMI-DEV Process Improvement workspace template
2. All 22 skills are automatically installed
3. Tell the agent your target maturity level — ML2, ML3, ML4, or ML5
4. Start with Project Planning (PP) to establish the foundation, then follow the maturity-level sequence
5. Use the dashboard to track progress per maturity level and monitor appraisal readiness

Each skill is independent but reads artifacts from earlier steps. You can run them in any order, but the recommended sequence ensures each skill has the context it needs from prior outputs — and that the artifact chain will survive SCAMPI scrutiny.

Summary

The CMMI-DEV Process Improvement workspace template turns appraisal preparation from a scattered documentation effort into a structured, validated process. The 22 skills cover every CMMI-DEV v2.0 process area from ML2 through ML5, and the validation tools enforce the same checks a SCAMPI Lead Appraiser would apply — consistently, automatically, and traceably.

What sets this apart from template-based approaches or generic AI drafting is the maturity-level-aware progression and cross-process-area traceability. The workspace adapts to your target — whether you’re a small team targeting ML2 or a defense contractor pursuing ML5. And at every step, deterministic tools verify that project plans align with organizational standards, requirements trace through design to verification, measurement data supports process baselines, and improvement actions close the loop from findings to prevention.

The result is not a set of generic process templates. It is a set of internally consistent, organization-specific, CMMI-aligned artifacts that reference each other, trace goals to practices to work products to evidence, and flag gaps before an appraiser does.