Continuous improvement

A team that uses Scrum always seeks to improve in order to become increasingly more efficient and effective. Improve its knowledge and skills, improve its teamwork, improve its processes, improve the quality of its work and improve the product under development.

In the continuous search for improvements, the team is encouraged to experiment, learn and adapt based on what is learned. In this sense, just as important as conducting experiments that can improve its work, is finding out early what doesn’t work adequately and then modifying or discarding it. It is better to fail early and learn from failure than to delay the validation of something that may not be working.

In order to ensure that a product is continually improved, therefore, it is developed with Scrum in short feedback cycles. And to ensure that the team becomes increasingly effective, a mandatory retrospective meeting is held at the end of each product development cycle. At this meeting, points on how to improve the way the work was conducted are raised and discussed, and action plans to put the improvements into practice are defined.