6.2: Rollout Strategy

Introduction

The pilot succeeded—one team achieved CL2. Now comes the hard part: scaling ASPICE to 10, 50, or 200 developers without chaos. A poorly planned rollout creates process fatigue, tool sprawl, and organizational backlash. This section provides a phased rollout strategy that scales ASPICE incrementally while maintaining productivity.

Rollout Phases Overview

The 3-Wave Approach

The following diagram illustrates the 3-wave ASPICE rollout strategy: Wave 1 (pilot team), Wave 2 (controlled expansion to 3-5 teams), and Wave 3 (organization-wide deployment), with success criteria gating each transition.

Critical Rule: Do NOT skip Wave 2. Jumping from 1 team to 50 teams = chaos.

Wave 1: Pilot (Covered in 23.01)

Duration: 4 months Teams: 1 team (5 developers) Outcome: CL2 achieved, lessons learned documented

Key Artifacts from Pilot:

1. Refined Templates: User Story template, ADR format, DoD checklist (based on pilot feedback)
2. Tool Configuration: Jira workflows, GitHub Actions pipelines, SonarQube quality gates
3. Training Materials: 2-day workshop content, onboarding checklists
4. Metrics Baseline: Velocity, defect density, review time (before/after ASPICE)

Go/No-Go Decision for Wave 2:

• [PASS] GO: Pilot achieved CL2 + team satisfaction ≥70%
• [FAIL] NO-GO: Pilot failed CL2 or team satisfaction <50% → Investigate root cause, re-pilot with adjustments

Wave 2: Early Adopters (Month 5-10)

Objective

Scale from 1 team to 4 teams (20 developers total) while refining processes.

Team Selection Criteria

Wave 2 Teams (3 additional teams):

Selection Process:

## Wave 2 Team Selection (Month 4)

### Step 1: Call for Volunteers (Week 1)
- Email all-hands: "ASPICE Wave 2 - Join the Early Adopters"
- Attach pilot demo video + lessons learned report
- Application deadline: 2 weeks

### Step 2: Screen Applications (Week 2)
- ASPICE Program Manager reviews applications
- Criteria: Volunteer status, project suitability, team composition
- Select 5-7 candidate teams

### Step 3: Interviews (Week 3)
- 30-minute interview with each team lead
- Questions:
  - "Why does your team want to adopt ASPICE?"
  - "What's your biggest concern about ASPICE?"
  - "Can you commit to 2-day training + weekly ASPICE office hours?"

### Step 4: Selection (Week 4)
- Select 3 teams (ranked by suitability)
- Notify accepted + waitlisted teams
- Kickoff Wave 2: Month 5, Week 1

Wave 2 Execution Plan

Month 5: Training & Setup

Week 1-2: ASPICE Training

• Format: 2-day workshop (same as pilot team received)
• Content:
  • Day 1: ASPICE fundamentals, V-Model, process overview
  • Day 2: Hands-on (create User Story, write ADR, run CI pipeline)
• Trainers: Pilot team members (knowledge transfer + champion building)
• Outcome: 15 developers trained, confident in ASPICE basics

Week 3-4: Tool Onboarding

• Jira: Configure 3 new project boards (one per team)
• Git: Set up repositories with pre-commit hooks (MISRA, traceability checks)
• CI/CD: Clone pilot pipeline template, customize for each project
• Outcome: Teams ready to start Sprint 1

Month 6-9: Development (Parallel Execution)

Each Team Runs 4-Month V-Cycle:

• Month 6: Requirements + Architecture (SWE.1, SWE.2)
• Month 7-8: Implementation + Unit Testing (SWE.3, SWE.4)
• Month 9: Integration + Qualification (SWE.5, SWE.6)

Support Structure:

• Weekly Office Hours: ASPICE Program Manager + Pilot Lead available for Q&A (2 hours/week)
• Bi-weekly Cross-Team Sync: 3 Wave 2 teams share learnings (1 hour, rotating facilitator)
• Monthly Check-in: ASPICE Program Manager reviews progress, identifies blockers

Month 10: Wave 2 Pre-Assessment

Objective: Validate all 3 teams achieve CL2.

Process:

1. Evidence Collection (Week 1-2): Teams package work products (Jira exports, Git logs, CI reports)
2. Pre-Assessment (Week 3): External assessor reviews 3 teams in parallel
   • Duration: 2 days per team (6 days total)
   • Format: Work product sampling + team interviews
3. Results (Week 4): Assessor issues 3 pre-assessment reports
   • [PASS] CL2 achieved: Team approved for production deployment
   • [WARN] CL1 (gaps): Team gets 2-month extension to fix gaps
   • [FAIL] CL0 (fail): Investigate root cause, may need re-training

Wave 2 Success Criteria:

• ≥2/3 teams achieve CL2 (67% success rate minimum)
• Team satisfaction ≥70% (post-Wave survey)
• No schedule slips (teams delivered on time)

Wave 3: Organization-Wide (Month 11-18)

Objective

Scale ASPICE to ALL teams (50-200 developers) across the organization.

Rollout Strategy: Gradual vs Big Bang

Two Approaches:

Recommended: Gradual Rollout

## Wave 3 Gradual Rollout Plan

### Phase 3A: New Projects (Month 11-14)
**Policy**: All NEW projects starting after Month 11 MUST use ASPICE processes.

**Implementation**:
- Product Management: Review project pipeline, identify new projects
- Projects starting in Month 11-14: ~6-8 teams (30-40 developers)
- Training: 2-day workshop offered monthly (accommodates staggered start dates)
- Support: ASPICE Center of Excellence (see below)

### Phase 3B: Existing Projects (Month 15-18)
**Policy**: Existing projects adopt ASPICE at next major milestone (e.g., version release).

**Implementation**:
- Projects reaching v2.0, v3.0 milestones → Adopt ASPICE for next version
- Retrofit cost: ~2 weeks to set up Jira, Git, CI/CD for legacy project
- Training: Teams attend standard 2-day workshop
- Exemptions: Projects in maintenance mode (no active development) can defer

### Phase 3C: Full Compliance (Month 18)
**Policy**: 100% of active projects on ASPICE.

**Measurement**:
- Jira metrics: % of projects using ASPICE Jira template
- Git metrics: % of commits with requirement IDs
- Target: ≥95% compliance (allow 5% for edge cases)

ASPICE Center of Excellence (CoE)

Purpose: Provide ongoing support during Wave 3 scaling.

Structure:

ASPICE Center of Excellence
├── Program Manager (1 FTE) - Strategy, reporting
├── Process Owners (2 FTE) - Maintain templates, process updates
├── Tool Champions (3 FTE) - Jira admin, CI/CD support, Git help
├── Trainers (2 FTE) - Deliver workshops, onboarding
└── Assessor Liaison (0.5 FTE) - Coordinate pre-assessments, audits

Services Offered:

1. Training: Monthly 2-day workshops (capacity: 20 people/workshop)
2. Office Hours: 10 hours/week drop-in Q&A (Zoom or in-person)
3. Template Repository: Confluence space with 50+ templates (User Stories, ADRs, test specs)
4. Metrics Dashboard: Real-time ASPICE compliance tracking (% teams CL2)
5. Pre-Assessments: Quarterly pre-assessments for teams approaching milestones

Budget: $800k/year (8.5 FTE × $100k avg salary)

Communication Plan

Stakeholder Communication (Throughout Wave 3)

Monthly All-Hands Updates (15 minutes):

• Format: Email + slide deck
• Content:
  • Progress: "12 out of 20 teams now CL2 certified (60% coverage)"
  • Success Story: Feature spotlight (e.g., "Team X reduced defects by 50% with ASPICE")
  • Q&A: Address common concerns
• Audience: Entire engineering org (200 people)

Weekly Team Lead Sync (30 minutes):

• Format: Zoom meeting
• Attendees: All engineering team leads (20 people)
• Agenda:
  • Blockers: "Team Y stuck on traceability automation"
  • Best Practices: "Team Z's ADR template is excellent, let's adopt it org-wide"
  • Policy Updates: "New requirement: All PRs must pass SonarQube quality gate"

Quarterly Executive Review (60 minutes):

• Attendees: CTO, VPs, ASPICE Program Manager
• Content:
  • Metrics: Compliance %, defect trends, velocity impact
  • ROI: "ASPICE enabled $8M contract win (Tier-1 OEM)"
  • Risks: "3 teams behind schedule, need additional support"
  • Budget: "Wave 3 on track, $50k under budget"

Metrics for Rollout Success

Key Performance Indicators (KPIs)

Dashboard Example (real-time, Confluence-embedded):

# ASPICE Rollout Dashboard
class ASPICERolloutDashboard:
    """Track organization-wide ASPICE adoption metrics"""

    def __init__(self, jira_client, survey_db):
        self.jira = jira_client
        self.survey = survey_db

    def get_rollout_status(self) -> dict:
        """Calculate rollout KPIs"""
        total_teams = self.jira.count_projects(type="software")
        aspice_teams = self.jira.count_projects(with_label="aspice-cl2")

        coverage_percent = (aspice_teams / total_teams) * 100

        # Training completion
        total_developers = 180
        trained_developers = self.survey.count_training_completed()
        training_percent = (trained_developers / total_developers) * 100

        # Team satisfaction (latest quarterly survey)
        satisfaction = self.survey.get_latest_satisfaction_score()

        return {
            "team_coverage": {
                "aspice_teams": aspice_teams,
                "total_teams": total_teams,
                "percent": round(coverage_percent, 1),
                "target": 95,
                "status": "[PASS] On Track" if coverage_percent >= 80 else "[WARN] Behind"
            },
            "training": {
                "trained": trained_developers,
                "total": total_developers,
                "percent": round(training_percent, 1),
                "target": 100,
                "status": "[PASS] On Track" if training_percent >= 90 else "[WARN] Behind"
            },
            "satisfaction": {
                "score": satisfaction,
                "target": 70,
                "status": "[PASS] Good" if satisfaction >= 70 else "[WARN] Needs Improvement"
            }
        }

# Example output (Month 15 of rollout)
dashboard = ASPICERolloutDashboard(jira, survey_db)
status = dashboard.get_rollout_status()

print(f"""
ASPICE Rollout Status (Month 15/18)

Team Coverage: {status['team_coverage']['aspice_teams']}/{status['team_coverage']['total_teams']} ({status['team_coverage']['percent']}%)
  Target: {status['team_coverage']['target']}%
  Status: {status['team_coverage']['status']}

Training Completion: {status['training']['trained']}/{status['training']['total']} ({status['training']['percent']}%)
  Target: {status['training']['target']}%
  Status: {status['training']['status']}

Team Satisfaction: {status['satisfaction']['score']}%
  Target: {status['satisfaction']['target']}%
  Status: {status['satisfaction']['status']}
""")

Output:

ASPICE Rollout Status (Month 15/18)

Team Coverage: 16/20 (80.0%)
  Target: 95%
  Status: [PASS] On Track

Training Completion: 165/180 (91.7%)
  Target: 100%
  Status: [PASS] On Track

Team Satisfaction: 74%
  Target: 70%
  Status: [PASS] Good

Common Rollout Challenges (and Solutions)

Sustainment Phase (Month 19+)

Objective

Maintain ASPICE CL2/CL3 compliance indefinitely (not a "project" but "how we work").

Activities:

1. Annual Audits: External ASPICE audit (full scope, 5 days, $100k)

   • Frequency: Every 12-18 months (OEM contract requirement)
   • Outcome: Maintain CL2/CL3 certification

2. Continuous Improvement (Path to CL3):

   • Retrospectives: Quarterly process improvement workshops
   • Metrics: Track process efficiency (e.g., "Code review time decreased from 3 days to 1 day")
   • Tool Evolution: Upgrade tools (e.g., migrate from Jira Server to Jira Cloud)

3. New Hire Onboarding:

   • All new developers attend 2-day ASPICE workshop within first month
   • Onboarding checklist includes "Complete ASPICE training" (mandatory)

4. Knowledge Retention:

   • Document tribal knowledge in Confluence (e.g., "Why we chose ADRs over UML diagrams")
   • Annual refresher training (1-day workshop, focus on updates/changes)

Summary

Rollout Strategy Recap:

1. Wave 1 (Pilot): 1 team, 4 months → CL2 achieved
2. Wave 2 (Early Adopters): 3 teams, 6 months → Refine processes, scale to 20 developers
3. Wave 3 (Organization-Wide): All teams, 8 months → Gradual adoption (new projects first)
4. Sustainment: Ongoing → Annual audits, continuous improvement

Critical Success Factors:

• Don't skip Wave 2 (1 team → 50 teams = disaster)
• Gradual rollout preferred over Big Bang (unless <50 developers)
• ASPICE Center of Excellence provides ongoing support (8.5 FTE)
• Metrics-driven: Track coverage, training, satisfaction monthly
• Executive mandate: ASPICE non-negotiable for strategic projects

Timeline: 18 months from pilot kickoff to full organizational compliance.

Next: Build team competency through training (23.03 Training and Competency).