Scrum Exposes Dysfunction? Not So
One popular saying in the agile community is "Scrum exposes dysfunction." If you're struggling to implement scrum effectively, as the thinking goes, this indicates dysfunction in your environment. (By the way, other agile frameworks are also said to have this effect. However, I hear the statement made predominantly about scrum, so that's what I'll focus on here.)
In my experience, this belief is not only wrong, it’s also a detractor to genuine attempts at transformation. This category of unhelpful accepted wisdom already contains at least three other beliefs:
- That Shu-Ha-Ri  is the way to agile
- That agile results in "cheaper better faster"
- That there are "agile best practices"
Allow me to explain the heresy. In most organizations, an attempt to implement scrum will encounter trouble. Existing team structures, processes, roles, motivational schemes and power structures are probably not agile-friendly. People will misunderstand the new framework and fear a loss of identity, power or self-worth. With partial or inconsistent understanding of the framework, it will not be easy to lead people toward an effective implementation of it.
You might think of these challenges as impediments to scrum, and that would be correct. Contrary to very popular advice (430,000 hits on Google), I suggest you avoid presenting these
Please log in or sign up below to read the rest of the article.