Process Assets in SPM
In mature software organizations, knowledge and experience are not allowed to reside solely in the minds of individuals. When a key developer or project manager leaves, their expertise should not leave with them. This is where Process Assets come into play.
Process Assets are the collective artifacts, documentation, guidelines, templates, historical data, and knowledge that an organization accumulates over time to support, define, and improve its software development and management processes. They represent the organization’s accumulated wisdom—the “how we do things here” captured in reusable form.
The term is most prominently used in the Capability Maturity Model Integration (CMMI) , where the Process Asset Library (PAL) is a required component of the Organizational Process Definition process area.
1. Definition and Purpose
A Process Asset is any artifact that contributes to the definition, implementation, or improvement of an organization’s processes. These assets are stored, managed, and made available to project teams to ensure consistency, efficiency, and quality across all projects.
Primary Purposes:
| Purpose | Description |
| Standardization | Ensures that all projects follow a consistent set of practices, reducing variability and improving predictability. |
| Reusability | Prevents “reinventing the wheel” by providing proven templates, checklists, and guidelines that teams can adapt. |
| Efficiency | Accelerates project startup by providing pre-existing frameworks, estimation data, and process definitions. |
| Organizational Learning | Captures lessons learned, best practices, and historical data so that future projects benefit from past experiences. |
| Process Improvement | Provides a baseline against which process changes can be measured and a repository for improvement ideas. |
| Compliance | Demonstrates adherence to industry standards, regulatory requirements, or contractual obligations. |
2. Types of Process Assets
Process assets can be categorized into several distinct types. A comprehensive Process Asset Library contains a mix of these categories.
A. Process Descriptions and Policies
These define what processes exist and how they should be performed.
| Asset Type | Description | Examples |
| Organizational Policies | High-level mandates that guide decision-making and ensure compliance. | Quality policy, security policy, software engineering policy, ethics policy. |
| Standard Processes | Defined, documented, and approved processes that represent the organization’s standard way of working. | Standard Software Development Lifecycle (SDLC) definition, standard project management process, standard change management process. |
| Process Tailoring Guidelines | Rules and guidance for how projects can adapt (tailor) the standard processes to fit their specific needs. | “For small projects (< 100 function points), the formal design review may be replaced by a peer review.” |
| Lifecycle Models | Defined lifecycle models that projects can select from. | Waterfall model definition, Agile (Scrum) process definition, DevOps pipeline definition. |
Challenges in Managing Process Assets
| Challenge | Description | Mitigation |
| Asset Overload | Too many assets, too much documentation, leading to “analysis paralysis.” Teams ignore the PAL because it is overwhelming. | Adopt a minimalist approach. Focus on critical assets. Use checklists and quick-reference guides rather than lengthy documents. |
| Outdated Assets | Assets that are not maintained become obsolete, leading to confusion and distrust. | Establish a regular review cycle. Assign clear ownership. Use version control and clearly mark retired assets. |
| Poor Organization | Assets are scattered across multiple locations (shared drives, email attachments, personal folders), making them impossible to find. | Centralize the PAL. Use a single, well-organized repository. Implement a clear naming convention and taxonomy. |
| Resistance to Use | Teams view process assets as bureaucratic overhead imposed by a remote process group. | Involve practitioners in creating and reviewing assets. Demonstrate value. Allow tailoring. Make assets easily accessible within existing tools. |
| Lack of Integration | Assets exist in isolation from the tools teams actually use. | Embed assets in the workflow. For example, embed checklists in pull request templates, make coding standards available as IDE plugins, integrate templates into project creation wizards. |
Summary
Process Assets represent the institutional memory of an organization. They are the collection of artifacts—process descriptions, templates, guidelines, historical data, lessons learned, and tool configurations—that enable consistent, efficient, and high-quality software development.
Key points to remember:
- Process assets are stored in a Process Asset Library (PAL) , which is a central, controlled repository.
- They enable standardization, reusability, efficiency, and organizational learning.
- The Process Database and Process Capability Baselines are specific, critical types of process assets—one providing raw data, the other providing analyzed, predictive understanding.
- In CMMI, process assets are fundamental to achieving Level 3 (Defined) and higher, with the PAL being a core component of Organizational Process Definition.
- The successful use of process assets requires not just a repository, but also governance, accessibility, integration with workflows, and a culture that values contribution and continuous improvement.