Constant attention to technical excellence and good design promotes agility

[suchona.kani.z]

First and foremost, a team or even a company should have a common definition of quality. The same applies to good design. Why are good design and technical excellence so important anyway? Isn't it enough if the software simply works?

A car that drives serves its purpose. If it doesn't drive and no one can see the reason, we have a problem. Now we have to find an expert who can identify and solve the problem. And even if we find him or her, the repair takes time. Now the gearbox has some defects because the work during production was not carried out properly.

Compromises were made so that the vehicle could be delivered early. Quality had to suffer, in this case the gearbox. We are no longer true to the above principle. Our customer is dissatisfied. Was it worth it?

Simplicity – the art of
maximizing the amount of work not done – is essential.
A team or organization should discuss what criteria must be met for an increment to be called done. Done should express that this piece of software is released and ready to be handed over to the customer. If we know what bulgaria consumer email list we mean by done, we will only do what is really necessary to declare an increment as done. We can save ourselves the rest of the work. If everyone has a different idea of ​​done, this will be reflected in the work of each individual, and as a whole this will mean a qualitatively inconsistent system.

A shared understanding of finished requires openness, transparency and a lot of communication. Adhering to this definition throughout the development process takes courage.

Courage not to overwork something I enjoy. Courage not to pay less attention to something I don't enjoy.


The key word in agile working is self-organization. Give the team an environment in which the members can work and agree with them on the goal to be achieved. The team does the rest. Self-organized and self-responsible. At first, that sounds like a green field and as if everyone can do what they want. That's not the case. There are frameworks (for example Scrum) that are intended to help people find their way around this high degree of freedom with the help of structures and processes.

on how it can become more effective and adapts its
behavior accordingly.
We don't just want to deliver working software on a regular basis. We also want to learn on a regular basis. The best way to do this is to find out how we can use the lessons we've learned to guide our next steps. Only by talking openly about successes and failures can we identify what we want to keep and what we should say goodbye to.