Solution life cycle

From idea to value delivered

Waardestromen/ Value streams

Valuestreams are used to describe the sequence of activities (end to end) needed to deliver a product or service to a customer (as an organization. The value streams of ABB where Digiteam is contributing to - at the time of writing- are:

• Met gelinkte sjablonen maken lokale besturen kwaliteitsvolle besluiten met authentieke herbruikbare gegevens

• Gelinkt publiceren en melden zorgt voor doorzoekbare besluitinformatie

• Gestroomlijnd communiceren tussen Vlaanderen en lokale besturen

• Vereenvoudigde en interactieve toegankelijkheidsinformatie leidt tot meer data en een groter inclusiviteitsbewustzijn

• Het duurzaam, betrouwbaar en herbruikbaar open stellen van (contact)gegevens van lokale besturen

• Het beleid rond geloofsgemeenschappen steunt op duurzame, betrouwbare en herbruikbare informatie

• Kennisgedreven digitale end-to-end dossierbehandeling

Ondersteunende waardeketens

• De IT-dienstverlening wordt op een duurzame, kwaliteitsvolle en efficiënte manier ontwikkeld en ondersteund

A new idea for a solution always fits into an existing or new value stream.

Value streams are coordinated and synced on a solution level.

Ideally every value stream has a clear and representative description.

Oplossingen/ Solutions (How?)

A solution describes the way Digiteam contributes to the enhancement or the creation of a values stream. Every solution that is built within Digiteam must contribute to one (or more) value streams.

A solution might need development in one or more products. When various products are involved, alignment is very important to deliver the solution in the existing cadence.

A solution can be built and delivered over more than one groeispurten/ growthspurts.

Solutions are initiated, described and managed at solution level.

Whom is responsible for the management of the solution can either be

1. A dedicated member of the solution level, or

2. A PM when the solution has a very good fit with the product he or she is managing.

Every solution is described clearly and in a condesed way on a Solution Index Card

Epics and stories in the product backlogs (What?)

We use Epics to clarify how an end user functionality in the product concerned should be developed. An Epic is a description of a functional block that, once built and made available in the product to end users, will deliver a certain value to the business owner. The time needed to realize an Epic is usually longer than a sprint. At ABB, we try to dimension Epics in such a way that they can be delivered in 1 growth spurt. We do this because the planning focus on a central planning day - in principle - does not extend beyond 1 growth spurt.