Decide knowingly

Feedback-Driven is the method for making software engineering decisions. It can be used for steering agile architecture, for guiding migrations, or for splitting monolithic applications.

Everyone makes decisions

The goal of Feedback is decision making. Managers decide the strategy. Architects decide the technical direction. Developers decide the implementation. Daily.

Decisions require accurate information

Effective decision making requires accurate information. But, software systems are large. Thus, manual code reading does not scale. You need analysis tools.

Details are essential

Software systems are complicated in specific ways. The system details are essential for your decisions. You need custom tools that provide the information that matters. Craft them.

Feedback is a human activity

Analysis tools are important to handle the scale of problems, but in the end, assessment is a Feedback-Driven activity. Regardless of how smart the tools are, it is still the Feedback that has to infer the relevant information and transform it into action.

Approach problems individually

Not all problems are created equal. Some are of continuous concern. They deserve daily attention. Some only appear once. These require different approaches. Learn their particularities. Deal with them individually.

Why a method?

Decisions are made everyday. It’s just that the effort is implicit and unoptimised. Feedback must become explicit and made integral part of the overall process. You need to approach it systematically. You need a method.