CMMI-DEV Organizational Process Definition

Overview

Draft CMMI-DEV Organizational Process Definition (OPD) deliverables: standard processes, tailoring guidelines, and process asset library for ML3.

Getting Started

Add your source materials to the project workspace, then activate the CMMI-DEV Organizational Process Definition skill. The agent will guide you through the process step by step.

Example Conversation

You: We’re building our organizational process asset library for CMMI OPD. We need standard process descriptions for project planning, requirements management, and development, plus tailoring guidelines. Can you draft the structure and one sample process?

Agent: I’ll draft a process asset library structure: standard processes (PP, REQM, RD, TS, VER, VAL, etc.), process architecture (how they connect), tailoring guidelines (what can be tailored, approval), and work environment standards. I’ll flesh out one process (e.g. Project Planning) as a sample.

You: Tailoring needs lead approval for schedule/scope; project lead for method details.

Agent: I’ve added tailoring guidelines with approval levels: lead approval for schedule/scope/resource changes; project lead for method details (e.g. review depth, tool choice). The library structure and sample PP process are in process-asset-library-structure.md and standard-process-pp.md.

Sample Output Excerpt

Excerpt from Organizational Process Definition documents produced with this skill.

Process asset library — contents

• Standard processes: Project Planning (PP), Requirements Management (REQM), Requirements Development (RD), Technical Solution (TS), Verification (VER), Validation (VAL), Configuration Management (CM), Measurement and Analysis (MA), Process and Product Quality Assurance (PPQA), Risk Management (RSKM), Supplier Agreement Management (SAM), and supporting process elements.
• Tailoring guidelines: Projects shall use the organization’s set of standard processes. Tailoring allowed for: lifecycle model (waterfall, iterative, agile), depth of documentation, tool selection. Schedule/scope/resource tailoring requires lead approval; method details require project lead approval.
• Work environment standards: Git for code; Confluence for docs; Jira for requirements and defects; shared build and test infrastructure per org standards.