Mob Programming

Last time, I wrote about how I started the Scrum Team without stressing the Scrum terms. After the preparation before everything begins, it’s time to start our development cycle. Daily Scrum Our Daily Scrum is similar to the standard one. Apart from developers, our manager also attends the Daily Scrum. Some might argue against the existence of the managers in the Daily Scrum. The Scrum Guide states that Daily Scrum is an event for Developers, but it isn’t meant to disallow managers’ existence. ...

Values provide direction for a team’s work. Scrum consists of five values essential for a Scrum Team to succeed. As a Scrum Master, I often consider how practices support Scrum values, allowing us to align new initiatives with Scrum. Our mobbing experiment is still ongoing, which leads me to think about how mobbing supports Scrum Values. The Scrum Team commits to achieving its goals and to supporting each other. Their primary focus is on the work of the Sprint to make the best possible progress toward these goals. The Scrum Team and its stakeholders are open about the work and the challenges. Scrum Team members respect each other to be capable, independent people, and are respected as such by the people with whom they work. The Scrum Team members have the courage to do the right thing, to work on tough problems. ...

In my passage about the myth of lengthy Scrum meetings two weeks ago, I mentioned that people often misinterpret the Scrum events and leave all the pre-Scrum meetings to exist. Code review is a common practice in many software development teams nowadays. There are various styles of code review, each serving different purposes. In traditional development teams, the developer submits their code to the source control, and a more experienced developer checks the code quality and logic before approving it for deployment. However, this process has been largely replaced by continuous integration tools like SonarQube. ...