A conversation with my scrum master friend
The convernsation
“Scrum has too many processes, most of them seem useless,” my friend told me, who was a lead and scrum master in a team.
“Do you mean the stand-up meetings, sprint review and planning and retro?” I asked.
“Yes, no one cares what others are doing and may not even listen to what others are saying (most of the time, I was the one only listening) so what’s the point of getting everyone to stand there and waste 15 minutes a day they can just come to me and tell me the status one by one”, he said
“And more than that. there are other meetings to attend which doesn’t make sense to developers at all, sprints sometimes don’t make sense either” he said.
“What do you mean by sprint doesn’t make sense?” I asked.
“If items are unable to be finished by the team and pushed to the next sprint, happens again and again, which looks like kanban.” He said.
“But do you see some incremental value after each sprint?” I asked.
“Do you mean extra features added in? Sometimes yes, but often other features are broken due to these new features added in from the last sprint”. he said.
“I have seen 3 issues in most software development teams. again and again. and I see no one talk about them”
Here is the first one.
