Giving feedback as a developer: models for teamwork in 2025

The changing role of feedback in agile development teams

Feedback among colleagues is becoming much more important in view of modern working methods in IT. Software development is no longer an individual battle. Teams rely on open communication, transparency and a culture that promotes continuous improvement. Giving feedback has therefore evolved from a traditional management task to a key qualification at all levels - from young start-ups to complex structures in large tech companies. Giving constructive feedback directly contributes to turning individuals into a functioning team that can shoulder challenging projects together.

The growing shift to working from home and collaboration across national borders is also leading to new challenges. Digital communication, infrequent face-to-face meetings and different working rhythms make it difficult to exchange ideas on an interpersonal level. Especially for developers with a strong technical focus and less practice in dialogue, giving reflective feedback is becoming a key team skill. Sharing knowledge, constructively addressing errors and contributing new ideas strengthens your position far beyond pure code.

Current models and practical methods, which are explained below, show how feedback can work profitably in everyday working life.

Giving feedback will remain a relevant success factor in 2025

Technological changes and demanding market conditions require development teams to be constantly ready to adapt. Innovation cycles are becoming shorter, work equipment changes regularly and requirements can hardly be predicted in the long term. Without the opportunity to talk openly about mistakes and learning opportunities, professional and personal development quickly comes to a standstill. Teams particularly benefit from feedback if it enables them to exchange knowledge more quickly and find new solutions. Tools such as sprint retrospectives, code reviews or pair programming form the institutional framework for this - but it is only through honest feedback that these formats realise their value.

Constructive feedback not only influences soft skills such as motivation or team spirit. It also provides orientation in culturally and linguistically diverse groups. While the demand for IT specialists is increasing and teams have to deal with fluctuation, a practised feedback culture pays off in terms of long-term loyalty and satisfaction - for projects as well as for individual development.

Structured methods for effective feedback in the IT sector

Brief feedback such as "well done" or "that was suboptimal" rarely does justice to the complex tasks involved in software development. Feedback that is specific, empirically based and solution-orientated is more effective. Various methods provide guidance on how to organise feedback in a targeted and respectful manner.

The SBI model (Situation-Behaviour-Impact) has proven particularly effective in a technical context. According to this approach, the specific situation is described first, then the observed behaviour, and finally its impact on the team or the project result. Something like this: "In yesterday's daily (situation), you very clearly presented your progress on the new feature (behaviour). This enabled us to quickly recognise the backend problem and fix it together (Impact)."

The WWW/WZW model is also helpful here. It asks: What was noticeable? What would have been desirable? What do I learn from this? In the context of a code review, this could be something like: "In the current pull request, the tests only cover one positive case (perceptible). I would suggest taking more account of boundary conditions (desirable). Next time, we could discuss the tests together to highlight different starting points (consequence)."

The following applies across all models: feedback is particularly effective when it is formulated in a differentiated and collaborative way. Sweeping judgements can be avoided by specifying the situation and avoiding generalisations. This creates openness for feedback - regardless of hierarchy, experience or personal preferences.

Feedback in everyday developer life: examples and potential stumbling blocks

Whether in code reviews, when prioritising technical debts or in the context of team meetings - feedback accompanies all phases of software development. The challenge often lies in the timing: spontaneous comments on the side or resorting to written communication harbour the risk of losing impact or even being misunderstood. Best practice: Consciously plan time slots, for example for brief feedback directly after the stand-up, a clear reference in the pull request to a specific line of code or an appreciative comment after a bug has been solved. Such concrete feedback strengthens trust in the team.

A common mistake is to mix feedback with unconscious judgements or emotions. A sentence like "You always program incomprehensibly" offers no approach for improvement - and inhibits dialogue. It is more effective to say: "In your last implementation, I noticed that the method name was not self-explanatory. It would be helpful to name functions more clearly for later maintenance." This opens up space for mutual understanding and invites clarification.

Especially in asynchronous exchanges via chat or collaboration platforms, the tone of voice often remains unclear. Before sending a comment, it is advisable to consider how the same content would come across verbally. Emphasising positive aspects or asking specific questions can prevent misunderstandings. For example: "I'm interested in the reasoning behind your solution for JSON parsing - would you like to briefly explain your idea? That way, we can further develop the robustness of the method together."

Dealing constructively with resistance in the feedback process

If feedback is not immediately well received, this is not uncommon - in intensive project phases, team members occasionally react cautiously or irritably. Acceptance of feedback grows over time and through experience. It is advisable to respond to the individual perspective of the other person, show empathy and offer a dialogue. A formulation such as "I realise how much effort you have put into the role. However, I have noticed a potential risk..." signals appreciation and promotes sustainable learning processes.

Integrate feedback into agile processes in a targeted manner: Code reviews, retrospectives, dailies

Agile methods such as Scrum or Kanban offer numerous structured opportunities for feedback. In code reviews, feedback is not only used to correct errors, but also enables knowledge transfer and strengthens the team culture. Appreciative comments such as "Your approach to dependency injection was well thought out" or factual suggestions such as "The use of an interface would make the component more flexible" promote mutual learning. The aim is always to further develop the practice together - never to expose mistakes. Both newcomers and experienced professionals benefit when feedback is concrete and comprehensible.

In the sprint retrospective, process aspects take centre stage. Positive feedback on successful processes, for example "Sharing our blockers in the channel has helped us to identify bottlenecks more quickly", creates motivation and reinforces desired behaviour. Critical points can be addressed as an "I" message, for example: "I had the feeling that the coordination in the last sprint came to a standstill. What were your experiences?" This encourages open discussion and promotes a sense of responsibility throughout the team.

Digital support: tools and methods for efficient feedback

Communication solutions such as Slack, Microsoft Teams or GitHub are an integral part of how development teams work together. However, written feedback has its own peculiarities: emotions and nuances are often lost, which increases the risk of misunderstandings. Thoughtfully used elements such as emojis - for example a friendly "Thanks for the quick adaptation! :)" - noticeably enhance short messages.

Specialised platforms, such as 360-degree feedback tools or applications like Miro and Mural for digital whiteboards, are ideal for planned feedback rounds. In code reviews, suggestion comments ensure that people work together on solutions instead of simply highlighting weak points. It remains essential: The context determines whether and how feedback is accepted. It makes sense to have clear guidelines that also serve as a reference for appreciative behaviour in remote teams.

Practical tips for a healthy and sustainable feedback culture in the team

Regular feedback can be trained in a targeted manner. Feedback should be given as promptly as possible in order to be directly effective - for example, a brief word of appreciation during the sprint instead of bundled evaluations in later reviews. It is also helpful to ask specifically for feedback, for example by asking "What do you think of my last proposal in the retro? Do you have any ideas on what I could do differently next time?" This encourages a willingness to learn from each other.

• Establish getting and giving feedback as an integral part of meetings
• Use targeted training and peer coaching to develop communication skills
• Visualise and reflect on successful feedback situations in the team
• Provide resources for soft skill development, for example via internal exchange formats

Visible added value is created when feedback is recognised as a useful tool - not only for improving code, but also for the sustainable growth of the entire team.

Conclusion: feedback as part of the developer personality

Giving feedback is not only one of the core competences of professional developers in 2025, it also significantly shapes the identity of the team. Those who formulate feedback empathetically, address technical and interpersonal issues in a differentiated way and firmly anchor it in everyday life support sustainable learning and make a decisive contribution to ensuring that teams grow with every project - both professionally and personally.