2.4: Generic Practices

What You'll Learn

By the end of this section, you will be able to:

• Explain how generic practices support process attributes
• Describe generic practices for each capability level
• Apply generic practices across all ASPICE processes
• Use generic practices to boost your process capability
• Understand how AI transforms the implementation of generic practices
• Prepare assessment-ready evidence using AI-assisted techniques
• Map AI capabilities to specific generic practices for targeted automation

What Are Generic Practices?

While base practices are process-specific, Generic Practices (GP) apply to any process to achieve a specific process attribute. They are universal.

Key distinction: Base practices answer "What does this process do?" while generic practices answer "How well is this process managed?" A process can produce correct outputs (base practices satisfied) yet still be poorly managed, unplanned, and unrepeatable (generic practices not satisfied).

Generic Practice Groups

In ASPICE 4.0, generic practices are organized into groups that correspond directly to process attributes. Each capability level introduces new process attributes, and each process attribute is supported by a defined set of generic practices. Understanding these groups is essential for systematic capability improvement.

GP Group Structure in ASPICE 4.0

ASPICE 4.0 note: Levels 4 and 5 are defined through process attributes PA 4.1/4.2 and PA 5.1/5.2, but ASPICE 4.0 does not prescribe explicit generic practices at those levels. Instead, organizations demonstrate quantitative management and continuous innovation through evidence of statistical process control and systematic improvement programs.

How GP Groups Relate to Each Other

The GP groups build on one another in a cumulative fashion. You cannot meaningfully implement Level 3 generic practices without first having Level 2 generic practices in place:

GP Group Scope and Boundaries

Each GP group has a distinct scope of concern:

Generic Practices by Level

Level 2 Generic Practices

GP 2.1: Performance Management (PA 2.1)

GP 2.1.1 — Identifying Objectives and Strategy

This is the starting point for managed process execution. Without clear objectives, monitoring becomes meaningless because there is nothing to measure against. The strategy defines how the process will be executed to meet those objectives.

AI opportunity: AI can analyze historical project data to suggest realistic objectives based on past performance. For example, an AI assistant can review defect rates from previous projects and recommend achievable quality targets for the current iteration.

GP 2.1.2 — Performance Planning

Planning the process means defining activities, sequences, dependencies, timelines, and milestones. This is where many organizations struggle because plans are often too generic or disconnected from actual execution.

GP 2.1.3 and GP 2.1.4 — Resource Determination and Availability

These two practices are closely related. GP 2.1.3 identifies what resources are needed, while GP 2.1.4 ensures those resources are actually available. Resources include personnel, tools, infrastructure, and budget.

GP 2.1.5 — Monitoring and Adjustment

This practice closes the plan-do-check-act cycle. Without active monitoring, plans become stale documents rather than living management instruments.

AI opportunity: AI dashboards can provide real-time process monitoring by aggregating data from project management tools, version control systems, and CI/CD pipelines. Anomaly detection algorithms can flag deviations from plan before they become critical.

GP 2.1.6 — Interface Management

Interface management addresses the coordination between all parties involved in or affected by the process. This includes internal stakeholders, suppliers, customers, and cross-functional teams.

GP 2.2: Work Product Management (PA 2.2)

GP 2.2.1 — Defining Work Product Requirements

Every significant work product should have defined requirements that specify its content, structure, and quality criteria. These requirements serve as the basis for reviews and acceptance decisions.

AI verification: AI tools can automatically check work products against their defined requirements. For example, an NLP-based tool can scan a requirements specification to flag ambiguous language, missing SHALL statements, or sections that fall below minimum content thresholds.

GP 2.2.2 — Storage and Control Requirements

This practice defines the configuration management regime for work products: where they are stored, how versions are managed, who can modify them, and how changes are tracked.

GP 2.2.3 — Identifying, Storing, and Controlling Work Products

This is the execution of the regime defined in GP 2.2.2. It ensures that work products are actually placed under configuration management and that the defined controls are followed.

GP 2.2.4 — Reviewing and Adjusting Work Products

Reviews ensure that work products meet their defined requirements. Adjustment ensures that issues found during reviews are resolved.

AI verification: AI-powered review tools can perform first-pass reviews of work products, checking for completeness, consistency, and compliance with templates. This allows human reviewers to focus on semantic correctness and domain-specific concerns rather than structural compliance.

Level 3 Generic Practices

GP 3.1: Process Definition (PA 3.1)

GP 3.1.1 — Establishing and Maintaining the Standard Process

The standard process is the organization's documented, approved, and maintained description of how a particular process should be performed. It serves as the baseline from which project-specific processes are tailored.

Tailoring with AI: When a new project begins, an AI assistant can analyze the project's characteristics (ASIL level, team size, technology stack, customer requirements) and recommend a tailored process derived from the organizational standard. The process engineer reviews and approves the recommendation, maintaining human accountability while saving significant setup time.

GP 3.1.2 — Determining Required Competencies

This practice requires that the organization identifies the competencies (knowledge, skills, experience) needed to perform the standard process effectively.

GP 3.1.3 — Determining Required Resources

At Level 3, resource requirements are defined at the organizational level as part of the standard process, not just per project.

GP 3.1.4 — Monitoring Methods for the Standard Process

The organization must define how it monitors whether the standard process is effective and followed.

GP 3.2: Process Deployment (PA 3.2)

GP 3.2.1 — Deploying the Defined Process

Deployment means instantiating the standard process for a specific project context. The tailoring must follow the guidelines defined in GP 3.1.1 and be documented with justifications.

GP 3.2.2 — Ensuring Competencies

Once the defined process is deployed, the organization must verify that the people performing the process have the required competencies.

GP 3.2.3 — Ensuring Resources

Resources identified in the standard process must be available for the project. This includes tools, infrastructure, and personnel.

GP 3.2.4 — Monitoring the Defined Process

Monitoring at Level 3 goes beyond project-level status tracking. It focuses on whether the defined process is effective, followed, and producing expected results.

Applying Generic Practices

Let's see how this works in practice with real examples:

Example: SWE.1 at Level 2

Example: SWE.4 at Level 3

Generic Practice Evidence Matrix

Level 2 Evidence Checklist

Level 3 Evidence Checklist

AI Impact on Generic Practices

AI fundamentally changes the economics and practicality of implementing generic practices. Tasks that were previously expensive, manual, and error-prone become automated, consistent, and scalable. This section examines the structural impact of AI on each GP group.

Shift from Manual to Automated Process Management

AI Impact on Performance Management (GP 2.1.x)

AI Impact on Work Product Management (GP 2.2.x)

AI Impact on Process Definition and Deployment (GP 3.x)

Critical principle: AI augments but does not replace human accountability. An AI tool can flag that a work product fails quality criteria (GP 2.2.4), but a human must decide whether to accept, reject, or waive the finding. ASPICE requires demonstrated human judgment in process management decisions.

AI Support for Generic Practices

AI can boost your generic practice implementation:

Evidence Generation

One of the most time-consuming aspects of ASPICE assessments is producing evidence that generic practices are implemented. AI can dramatically reduce this burden while improving evidence quality.

AI-Assisted Evidence Collection Strategies

Building an Evidence Repository

A systematic approach to evidence generation ensures assessment readiness at all times rather than scrambling before an assessment.

Traceability from GP to Evidence

For each generic practice, assessors need to see a clear chain from the GP requirement to the evidence that demonstrates its implementation.

Practical tip: Configure your AI tooling to generate a "GP Evidence Report" at regular intervals (e.g., monthly). This report should list each GP in scope, its current evidence status (green/yellow/red), and links to the evidence artifacts. When an assessment is announced, the report immediately shows your readiness level.

Assessment Preparation

Preparing for an ASPICE assessment is a significant effort. AI can streamline this preparation by automating repetitive tasks and ensuring consistency across the assessment scope.

Pre-Assessment Readiness Check

Before an assessment, organizations should verify that evidence is complete, current, and accessible. AI can automate much of this verification.

Assessment Simulation

AI can conduct mock assessments to identify weaknesses before the real assessment takes place.

Assessment simulation example: An AI tool reviews your SWE.1 implementation and reports: "GP 2.1.5 (Monitoring) — evidence is rated P (Partially achieved). Status reports exist for 3 of 8 milestones. Recommendation: generate status reports for remaining milestones or provide alternative monitoring evidence such as dashboard screenshots and metric trends."

During the Assessment

Mapping GPs to AI Capabilities

Different AI capabilities support different generic practices. This mapping helps organizations target their AI investments for maximum impact on capability improvement.

AI Capability Categories

GP-to-AI Capability Mapping

Investment Prioritization

When deciding which AI capabilities to invest in first, consider the following priority matrix:

Common Assessment Findings

Understanding typical assessment findings related to generic practices helps organizations anticipate and prevent weaknesses. The following findings are among the most frequently observed in ASPICE assessments.

Level 2 Common Findings

Level 3 Common Findings

Finding Severity and Remediation Priority

Practical advice: The most common reason organizations fail to achieve Level 2 is not a lack of technical capability but a lack of documented evidence for GP 2.1.x practices. Plans, objectives, and monitoring records must exist as explicit artifacts. AI tools that automatically generate these artifacts from project management data can eliminate this class of findings entirely.

Implementation Checklist

Use this checklist to verify that your organization has addressed all generic practices at Levels 2 and 3. For each item, record the status (Done, In Progress, Not Started, N/A) and link to the relevant evidence.

Level 2 Implementation Checklist

Level 3 Implementation Checklist

Using this checklist with AI: Configure an AI agent to periodically scan your project repositories, document management systems, and project management tools against this checklist. The agent should update the status column automatically based on artifact detection and generate a report highlighting items that require human attention.

Summary

Generic Practices:

• Apply universally across all processes
• Support process attribute achievement
• Define how well processes are managed (not what they do)
• Enable consistent capability improvement
• Can be augmented by AI for efficiency
• Are organized into groups that map directly to process attributes at each capability level
• Require documented evidence that withstands assessment scrutiny
• Benefit significantly from AI automation in evidence generation, monitoring, and review

Understanding and implementing generic practices is essential for climbing the capability levels. They are the "how well" to the base practices' "what." With AI support, the overhead of implementing generic practices — particularly the documentation, monitoring, and evidence generation aspects — can be reduced dramatically, allowing teams to focus on the substance of process improvement rather than the mechanics of compliance.