A co-worker forwarded me an article from a 20 + year agile developer talking about why he thinks Scrum works. I thought it was worth sharing.
Here is a snip from the article hyperlinked above…
Why does Scrum Work?
OK, so why does Scrum work? Remember, I am not challenging that it does, just asking why. I would say Scrum works for the following reasons:
- The iterative nature of Scrum development (including the re-assessment of priorities between iterations)
- The work-cell nature of the Scrum team (everyone who needs to work together is together)
- The fact that many Scrum teams are given the chance to co-locate
- Most Scrum teams work on one project at a time
- Many old, cumbersome checkpoints/forms/status reports that used to be required are abandoned because the team is doing something new
- A focus on defining acceptance tests concurrent with requirements
- The availability of a product champion (product owner to Scrum enthusiasts)
May 25, 2007 — Posted by Alan Shalloway
So, how many of these bullet points have you implemented on your scrum team? I would venture to say that the teams than can say yes to all of these bullets in relation to their teams are the happiest, most regularly successful team we have. I would also venture to say that the farther you stray from these bullets, the less satisfied you are with Agile and Scrum and your performance to this point in trying to implement it.