Scrum replaces a personal responsibility with a team responsibility. This is tying up the team members together in the noble effort of producing a better product. But what is the downside of this approach?
By having no ability to identify personal commitment, a manager can’t know is someone can’t keep up with the team pace or level of commitment, or simply a skill. This is a big deal both for a small team where personal effort is of a great importance and for big enterprise where it’s so many employees that it’s hard to identify underperformers.
The add-on helped to identify a frontend developer that committed code of a much lower quality than other team members. As appeared after consulting with a quality control engineer, he was creating a big amount of functional defects each release (comparing to other team members).
The developer was replaced as the project is critical to the company.
Replacing underperforming team members helps achieve more at the end of the day. Time has shown that the replacement carried a great outcome for the project and even for the replaced developer. As he entered the project that suited better for his skills and a level of maturity. A new developer shown better fit to the existing team improving both delivery and code quality KPI’s.