Some of Google’s instructions for a good code review. It talks how code review can be used for mentoring, that imperfect changes that improve overall quality should be accepted, and remind us that design is not always an objective factor.
If you try to setup static analysis of a legacy project for the first time, you inevitably end up with thousands of errors and warnings. It usually leads to a demotion of the value of static analysis: “We will never fix all of this, it will always be red”. On this article, Sonar tell us that you are right, and sugest and approach on how incorporte static analysis on legacy projects.
A sprint in Scrum is not a mini-waterfall project, we can be flexible and pivot inside a sprint. If it may seem contradictory with the concept of Sprint Backlog, David Denham will explain this confusion and how to make sense of all of this.
“Risk Analysis: Impact x Probability”, right? Can be, but not always. Here Michael Bolton deep dives on the concepts of risk and analysis, and the complexities of these activities on testing. (Note: No complicated math, more concept discussion).