TL; DR: Beware of Becoming a Scrum Mom (or Scrum Pop)
Trying to be supportive and do good, is most of the time an honorable thing. This is particularly true in your capacity as a Scrum master. However, doing too much good can quickly have the opposite effect. It’s a known Scrum anti-pattern, often referred to as the Scrum mom syndrome.
Read on to learn more about its manifestations, and the damage to your team caused by being overly protective.
Disclaimer: Of course, this post is in no way intended to be gender-specific. In my experience, there is no difference between the Scrum pop and the Scrum mom. This post is all about the emerging trend of Scrum helicopter parenting.
TL;DR: Why Engineers Despise Agile
The agile consulting industry repackages an originally human-centered, technology-driven philosophy into a standardized, all-weather project-risk mitigating methodology. Sold to command & control organizations, their middle managers turn “Agile” into a 21. century adoption of Taylorism for knowledge workers. Beyond this meta-level, the reasons, why engineers despise Agile, fall into five categories: Control, manipulation, monitoring, technology and teamwork.
Do you want to get this article in your inbox? You can sign up here and join 24k other subscribers
TL; DR: Customer Care as a Litmus Test for Innovation and Agile Change
Customer care as an entity, its function, and status within a company, can act as a good litmus test for a company’s culture, its product management, and thus its potential for innovation and agile change.
If customer care is regarded solely as a cost center that needs to be outsourced, agile change is unlikely to happen in that organization.
Let’s Fix Agile
When I wrote the Agile Failure Patterns In Organizations post in October, I could not anticipate the feedback it would receive: Over 80 comments on the Hacker News thread and almost 15,000 readers on the blog and additional channels like DZone or Business2Community.
The Fine Line Between Risk Mitigation and Falling Back into Covering Your Butt
The team hasn’t met its commitments once. Not once.
The atmosphere was becoming thicker by the minute. The management was displeased with the progress of the project and was looking for answers, starring at a bunch of Jira charts, I prepared earlier. “How can we claim that we are working in Scrum mode if the team is not sticking with the rules?”
Throughout the majority of projects I have been working on I could observe an obsession with burn-down charts and other Scrum metrics, mainly team commitments. And as a consequence, a side product of backlog grooming, estimation, and sprint planning is elevated to the most important management indicator that “Agile” works: The team’s commitment is matching or outperforming its average velocity.
What Is the Most Important Agile Challenge You Are Facing At the Moment?
Everyone of us is dealing with numerous issues related to becoming, improving or even staying Agile every day. I would like to learn more about the spectrum of your Agile challenges. If you invest three minutes of your time, that would mean the world to me:
Click to complete the Agile Challenge Survey at Google Forms