PEDCO
Reference Model to Agile Mappings

Move toward agile ways of working without losing regulatory alignment.

Transform existing regulated processes toward agile product development while remaining aligned with the reference models, standards, and regulatory constraints that apply.

Book a walkthroughSee how it works
Model expectation → agile practice
Requirements are reviewed and agreedBacklog refinement & acceptance criteria
Integration is planned and verifiedContinuous integration & system demo
Safety impact is assessed and recordedAdditional process element required
Where agile already satisfies the intent — and where it does not.
Overview

Regulated processes were designed around reference models.

Organizations in regulated industries often have established processes designed around reference models such as Automotive SPICE, CMMI, ISO standards, medical-device requirements, or company-specific models.

Moving those processes toward agile product development requires both deep process knowledge and an understanding of how agile practices can satisfy the intent of existing requirements.

Objective

Shorten the path to an organization-specific agile development method that remains compatible with required reference models and standards.

Service scope

Reference models the service can address

  • Automotive SPICE
  • CMMI
  • ISO standards
  • Functional-safety standards
  • Medical-device and FDA-related models
  • Industry-specific models
  • Internal reference models
How the service works

Four steps, traceability kept throughout.

  1. Understand the current process and obligations

    Review the existing process landscape and the reference models that apply.

  2. Identify agile equivalents and extensions

    Determine where lean-agile practices already satisfy the intent of the reference model and where additional process elements are required.

  3. Redesign the process where needed

    Integrate appropriate agile practices while retaining the process elements necessary for compliance.

  4. Maintain traceability

    Keep the relationship between reference-model expectations and the resulting process visible.

Deliverables
  • Mapped reference-model expectations
  • Agile-practice relationships
  • Identified gaps
  • Process-design recommendations
  • Revised process elements where included
  • Traceability between the model and the process
Benefits
  • Reduce engineering time when creating a regulated agile development method.
  • Build on existing proven processes rather than discarding them.
  • Add validated lean-agile practices where they improve the way of working.
  • Preserve alignment with reference models while transforming the process.
  • Use Applied SAFe® as an available starting point where appropriate.

Transform the process without disconnecting it from the standards.

Book a walkthroughAll Process Engineering & Compliance services