Many development teams hold Scrum meetings every morning. But why do many developers consider Scrum one of the 'most hated tasks'?
Scrum is a term originally derived from rugby. You may have seen the scene where players from both teams put their heads together and push each other to compete for the ball when the ball stops during the game. What's important in this scene is role division, cooperation, and immediate execution. It's not just a meeting, but a moment of focused tactical execution to regain the ball.
However, in many companies, Scrum is merely used as "a short report of what you did yesterday and what you will do today." In fact, when I first joined a startup, the CEO said, "Scrum is done standing up!" and made everyone stand up and only reported for an hour. The essence of Scrum was gone, leaving only the format of 'a meeting held standing up'.
Real Scrum is a process where the team shares accurate information in a short amount of time, establishes strategies to overcome problems through cooperation, and quickly transitions to execution. It should be a real "movement to win the ball," not a report-like feeling.
Manager: "Developer A, what did you do yesterday?" rather than
Developer A: "Some design modifications are needed for the feature I am currently implementing."
It's time for a Scrum where practical discussions and requests like this are exchanged.
Scrum is coordination, not reporting.
How about rethinking Scrum that the development team doesn't hate, starting now?
