Feature

type: flight-item-type
uses-route: Feature Route
created_at: 2026-10-10

Where do Flight Items of this type come from?

From Product Management splitting an Epic into pieces one PI can hold, and from market requests that arrive feature-sized — a payment terminal variant, a new OCPP profile, a quieter fan curve. One feature is one capability a customer can see, spanning as many teams as it needs: a hardware change in HW Base, firmware in the product line, a backend change in Connectivity.

Why are you working on these? What is the customer value?

A feature is the unit the Charger ART plans, commits and demonstrates. It is the size at which hardware, firmware and backend can be promised together and shown together.

To whom is the finished Flight Item delivered?

To the customer as part of a system release — built by Manufacturing into new units, and rolled out to the fleet over the air by Connectivity where firmware alone carries it.

How long does it take?

One PI — ten weeks — from PI planning to the system release. A feature that needs new tooling or a certification slot usually takes two.

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

Feature.md

---
type: flight-item-type
uses-route: "[[Feature Route]]"
created_at: 2026-10-10
---

## Where do Flight Items of this type come from?

From [[Product Management]] splitting an [[Epic]] into pieces one PI can hold, and from
market requests that arrive feature-sized — a payment terminal variant, a new OCPP
profile, a quieter fan curve. One feature is one capability a customer can see, spanning
as many teams as it needs: a hardware change in [[HW Base]], firmware in the product line,
a backend change in [[Connectivity]].

## Why are you working on these? What is the customer value?

A feature is the unit the [[Charger ART]] plans, commits and demonstrates. It is the size at
which hardware, firmware and backend can be promised together and shown together.

## To whom is the finished Flight Item delivered?

To the customer as part of a system release — built by [[Manufacturing]] into new units,
and rolled out to the fleet over the air by [[Connectivity]] where firmware alone carries
it.

## How long does it take?

One PI — ten weeks — from PI planning to the system release. A feature that needs new
tooling or a certification slot usually takes two.