Scrum Master

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. ...

Returning to the time I was told by my team manager I was going to form a new team to work on a new product, I’ve never thought that in almost 4 years, my team has grown and sustained in a way different than other teams in the company. When I was in my previous team, many people struggled using Scrum. People are obsessed with Story Pointing. Some team members refused to attend the Sprint Review and Retrospective. Everyone works without a clear goal but only emptying the backlog and fighting the deadlines. Arguments like Code Refactoring versus meeting the deadlines and estimation versus actual were everywhere. There were times that I doubted if Scrum brought us a tough time. There were times that I almost wanted to quit the job due to the burnout. ...

In 2020, the Scrum Guide changed “Scrum Roles” to “Scrum Accountabilities”. This implies that a member of a Scrum Team is not tied to a role. A Scrum Team member takes accountability to work towards the same Product Goal. It also implies that a single member may take multiple Scrum Accountabilities. But is it recommended? Despite the influential people at Scrum.org not recommending us to take multiple Scrum Accountabilities, I had no choice but to take all three accountabilities since my team’s establishment. The team works quite smoothly most of the time, but there are unnoticed risks. ...