The Loop

We improved on the original devops pipeline, giving it a meaningful start and end

Start

Requirement

We need to collect requirements and use-cases to create meaningful services.

Concept

A clear concept on what we will build and what the value is will be created as starting point

Project

People and Resurces need to be allocated, as well as internal requirements need to be observed

Commites

More often the Less, applications need to pass commites (work councils, privacy, etc). By shifting this left, we can get approval before starting the work, minimizing the waiting time here.

The Loop

Plan

Collect Use Cases from Stakeholders, Priorize them, Manage the backlog, decide what to do in the next sprint

Code

Create Code and Tests. This step normally ends with a code review and a merge into production.

Build

Using a CI / CD Pipeline, deployable artifacts will be created

Test

Automatic Tests, as well as SAST and DAST run here. Finally acceptance tests will be run to allow for release into production

Release

Create a finalized version for production

Deploy

With zero-downtime, replace the running release with the new artifact

Operate

The release will run and be managed

Monitor

Measure Metrics and use the understanding to create new user-stories

End of Life

If the service is no longer needed or is superseeded by another service, it musst be deacitvated.