Code reviews for quality assurance | Martin Hinshelwood

📍 📍 Are multiple schools of thought. One school of thought is that code reviews help us improve our code quality, help reduce defects because we get multiple eyes looking at the product. But I think that’s only part of the story. As we shift left, another school of thought starts to come to the forefront, which is our code should be pre reviewed.

A code review, a person manually code reviewing our code should not actually be required because our code should already have been reviewed by the time we submit a pull request. And that would then enable us all of our pull requests to be almost totally automated or as automated as we can get to so that the pull request process itself is not becoming a blocker to delivering value in our business.

So there are lots of different techniques and practices within the context of code reviews. I very much support and value code reviews and pull request systems that are in place in GitHub and Azure DevOps. I would absolutely recommend that nobody is able to commit code to master to main without going through a pull request and without passing validated checks.

But those validated checks should be in place. As automated as they can possibly be within the context of your system. And Naked Agility has helped others and can help you create. automations and practices and procedures that enable you to have the highest quality possible code and detect defects as early as possible.

#agile #scrum #agileprojectmanagement #agileproductdevelopment #agileproductmanagement #productdevelopment #projectmanagement #projectmanager #productmanager #developer Watch on Youtube

Shifting Left. Quality from the Start

Code reviews for quality assurance | Martin Hinshelwood

What to read next