How a framework just implying what needs to be done causes damage

Scrum proponents have long espoused that Scrum is intentionally simple and expect the teams to figure out what’s needed. I have never understood the validity of this approach. Simple is in the eyes of the beholder- a simple starting point may be simple for some but not for everybody. Being incomplete requires reinventing the wheel. Admittedly being more complete without adding complexity takes more effort to create. But that’s a methodologist’s job.

One of Scrum’s mandates is that there is only a team – no developer or tester role. The intention is both are working towards value add. But many organizations do have separate roles. Scrum provides no guidance here except be done at the end of the sprint.

As more companies use Scrum I see that more and more have the challenges of testers lagging. Yet Scrum provides no guidance for this. The answer, of course, is a lesson in flow and explaining why the gap between dev and test creates more work for both roles and therefore both roles have an incentive to work together.

Some teams figure this out, others don’t. Many Scrum proponents blame teams with this problem for not achieving the intended objective of Scrum. This shirks the responsibility Scrum proponents have.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.