Architecture

02. We develop value streams

Why we develop chains

So that you understand how the architecture should work for users and through which processes you will support it. Doing so will lay the groundwork for the further development IT architecture.

Our activities at this stage

  1. Describing the customer journey of a value stream.
  2. Establishing the basic level (L2/L3) of the processes that come under the customer journey.
  3. Revising the settings from the previous stage, especially from the perspective of sector independence in interactions and processes. If a high level of interconnectedness is found, the definition of chains is revised.
  4. Defining roles in the team, and therefore ensuring the smooth functioning of the value streams. This team becomes the primary team responsible for the architecture in the following stages.

Results

  • A customer journey for the value stream
  • Processes for the value stream
  • Composition of the team

Useful tips

  • In this phase, do not be afraid to go back to the definition of chains and add other activities as you go along.
  • The goals, language and rhetoric of the workshop should be in line with the purpose. Should you wish to change the architecture completely, do not consider it through the perspective of the existing architecture. If you require optimization, here you should compare reality with the limitations.

Methodology applied

  • Scaled Agile Framework (SAFe)
  • BPMN
Part 3/6
We define business services
03