Quality Shift-Left

Integrate functional testing early in the development process instead of leaving it later.  The classic test phases in projects cannot prevent errors from occurring. They only reveal them – at high cost.  Quality assurance before the first line of code is written is much cheaper. In development itself, test-driven procedures are a means of preventing errors. They allow consistent quality to be ensured through high automation of regression tests and a build pipeline. Other approaches such as machine-generated tests also save time and increase test coverage.

Prevention of errors being built into production through evolutionary (incremental) concepts.  Methodologies such as baby steps, test and acceptance test-driven design enable work to be carried out as error-free as possible.  Consistent collaboration and direct feedback establish a four-eyes principle and promote knowledge distribution within the team.  This includes working methods such as pair programming, swarming or ensemble programming.

Development of a common (technical) language for a clear exchange of ideas and expectations.  The world of experience of those involved in the project is often very different. Apparently clear terms can be understood differently (e.g. homonyms) and in extreme cases lead to high error costs, which can be elegantly prevented in this early phase.  Ideas and expectations are tested early and regularly using understandable models and enable the common intention to be verified. This results in a gradual adjustment of the initial idea and expectation.

Experimental testing of ideas in order to find the best possible solutions.  A swimming ring forged perfectly from gold will not be of any use to you.  Even in the early stages of idea development, these must be constantly tested for their usefulness and added value when communicating. Only through systematic experimentation with ideas can the value-creating approaches emerge. This prevents bad investments. Shift-Left saves money