How to do code review and why it matters

Good code review is not just about finding bad code smell or Reducing bugs. it benefits everyone and makes the process smooth.

The problem

In the software team, we do Agile and Scrum. then after 1–2 sprints. many codes have not been merged, which slowed down and blocked QA and DevOps releases.

Then due to release timeline pressure, after a few sprints suddenly merged everything, scrum becomes a waterfall.

What is the issue? Obviously, the code merged is late. but why?

Not everyone is doing code reviews

It could be some from below:

• I am too busy with my own ticket, I do not have time to review others’ codes.
• Why I should bother to review others’ code? Is it impacting my performance? I should focus on finishing more tickets then the audit log looks better at year’s end. and I will get a better bonus.
• I am still a junior, I am not good enough to review senior’s code
• I am not familiar with the changes this guy is pushing.
• Ok, time pressure, Let me click on the Approve without thinking much.
• No, I can not click the approve button, later when got bugs due to this code, I will be blamed. Let me wait for someone else to do it.
• …