In test-driven development, tests are written first, and just the bare minimum of code is created in order for the tests to pass. TDD is a well-known technique for feature development that can raise the standard of the code and increase test coverage. What about other, non-functional requirements such as scalability, reliability, observability, and other architectural concepts? How can we make sure that features are resilient and operable when they are put into production? In the same way the test-driven development incorporates code quality and test coverage, fitness functions help product teams avoid architectural drift and objectively measure technical debt. By definition fitness function-driven development is a natural extension of continuous integration. It encourages teams to incorporate these architectural standards into the core of their development.

In this session I will present that architecture, like business capability and infrastructure, can be expressed in code through the use of appropriate fitness functions. After this session participants will know how they can ensure every new service or piece of software they build is developed in a way that passes the fitness functions and supports the architectural qualities they value.