Charger ART

type: unit
unit-type: ART , work-system
flightlevel: 2
member-of: Voltfeld
contributes-to: Portfolio
delegator: Henrik Dahl
version: 1.0
decision_date: 2026-01-12
review_date: 2027-01-11
created_at: 2026-10-10

In context

Inferred from the org folder · scroll to zoom, drag to pan, click a box to open it

Inferred from the org folder · click a box for its details, +/− to collapse, scroll to zoom, drag to pan

Purpose

Coordinate the three product lines and three FL1 work systems that develop Voltfeld’s chargers so that features land in releases together — hardware, firmware and backend in step — on a ten-week Program Increment cadence. The ART coordinates across the three FL2 product lines — Wallbox, DC Charger, Connectivity — which sit on its level and contribute to it; it plans, syncs, integrates and releases across them, and the product lines coordinate their own teams.

Key Responsibilities

Run PI planning, the weekly ART sync, the system demo and the inspect-and-adapt workshop, facilitated by the Release Train Engineer.
Turn portfolio epics into a ranked feature backlog (Product Management) and an architectural runway (System Architect).
Resolve cross-team dependencies — above all between the two product lines and the two platform teams they draw on, HW Base and Firmware Platform.
Release: integrate, certify and ship a system release at the end of each PI.

Customers and Deliverables

Portfolio — delivered epics, a PI predictability measure, an honest capacity signal.
Manufacturing — a release that can be built: drawings, BOM, test firmware.
Field Service — release notes, recovery procedures, OTA packages via Connectivity.

Dependencies

Depends on Supply Chain for long-lead parts and tooling, on Manufacturing for ramp capacity and design-for-manufacturing feedback, and on System Integration for certification slots.

External Constraints

Certification cycles (IEC 61851, EMC, regional approvals) that take longer than a PI.
Component availability and tooling lead times set by suppliers.

Key Challenges

Enclosure and tooling lead times exceed one PI; the ART plans in ten-week increments while Supply Chain works on fourteen-week lead times and is not in the room at PI planning.
Two product lines pull on the same two platform teams with different priorities.
Hardware integration happens late — the first time a new power stage meets production firmware is on the system rig, not before.

Key Resources

Three product lines (Wallbox, DC Charger, Connectivity, each with two teams) and three FL1 work systems (HW Base, Firmware Platform, System Integration); the ART roles Release Train Engineer, Product Management, System Architect; the HIL and system test rigs.

Delegator Responsibilities

Henrik Dahl chartered the ART and keeps it funded per PI through the Portfolio.

Competencies, Qualities and Skills

Cross-team planning under hardware lead times, systems thinking across power electronics, firmware and cloud, facilitation of thirty-plus engineers at once.

Key Metrics and Monitoring

PI predictability (committed vs. delivered objectives); feature lead time; release cadence held; cross-team dependencies open at PI planning.

Evaluation Schedule

Inspect-and-adapt at the end of every PI; domain description reviewed yearly, next 2027-01-11.

Like what you see? → Start — build your own org folder in ~2 min

Charger ART.md

---
type: unit
unit-type:
  - ART
  - work-system
flightlevel: 2
member-of: "[[Voltfeld]]"
contributes-to: "[[Portfolio]]"
delegator: "[[Henrik Dahl]]"
version: "1.0"
decision_date: 2026-01-12
review_date: 2027-01-11
created_at: 2026-10-10
---

## In context

```dwsd.topology
mode: infer
radius: 2
```

```dwsd.units
mode: infer
focus: self
radius: { up: 1, down: inf }
```

## Purpose

Coordinate the three product lines and three FL1 work systems that develop Voltfeld's chargers so that features land in
releases together — hardware, firmware and backend in step — on a ten-week Program
Increment cadence. The ART coordinates across the three FL2 product lines —
[[Wallbox]], [[DC Charger]], [[Connectivity]] — which sit on its level and contribute to it;
it plans, syncs, integrates and releases across them, and the product lines coordinate their
own teams.

## Key Responsibilities

- Run PI planning, the weekly ART sync, the system demo and the inspect-and-adapt
  workshop, facilitated by the [[Release Train Engineer]].
- Turn portfolio epics into a ranked feature backlog ([[Product Management]]) and an
  architectural runway ([[System Architect]]).
- Resolve cross-team dependencies — above all between the two product lines and the
  two platform teams they draw on, [[HW Base]] and [[Firmware Platform]].
- Release: integrate, certify and ship a system release at the end of each PI.

## Customers and Deliverables

- [[Portfolio]] — delivered epics, a PI predictability measure, an honest capacity signal.
- [[Manufacturing]] — a release that can be built: drawings, BOM, test firmware.
- [[Field Service]] — release notes, recovery procedures, OTA packages via [[Connectivity]].

## Dependencies

Depends on [[Supply Chain]] for long-lead parts and tooling, on [[Manufacturing]] for ramp
capacity and design-for-manufacturing feedback, and on [[System Integration]] for
certification slots.

## External Constraints

- Certification cycles (IEC 61851, EMC, regional approvals) that take longer than a PI.
- Component availability and tooling lead times set by suppliers.

## Key Challenges

- Enclosure and tooling lead times exceed one PI; the ART plans in ten-week increments
  while Supply Chain works on fourteen-week lead times and is not in the room at PI planning.
- Two product lines pull on the same two platform teams with different priorities.
- Hardware integration happens late — the first time a new power stage meets production
  firmware is on the system rig, not before.

## Key Resources

- Three product lines ([[Wallbox]], [[DC Charger]], [[Connectivity]], each with two
  teams) and three FL1 work systems ([[HW Base]], [[Firmware Platform]],
  [[System Integration]]); the ART roles [[Release Train Engineer]],
  [[Product Management]], [[System Architect]]; the HIL and system test rigs.

## Delegator Responsibilities

- [[Henrik Dahl]] chartered the ART and keeps it funded per PI through the [[Portfolio]].

## Competencies, Qualities and Skills

- Cross-team planning under hardware lead times, systems thinking across power
  electronics, firmware and cloud, facilitation of thirty-plus engineers at once.

## Key Metrics and Monitoring

- PI predictability (committed vs. delivered objectives); feature lead time; release
  cadence held; cross-team dependencies open at PI planning.

## Evaluation Schedule

Inspect-and-adapt at the end of every PI; domain description reviewed yearly, next
2027-01-11.