7 hurdles to reach Scrum Drupal Nirvana in projects.
(in Buddhism) a transcendent state in which there is neither suffering, desire, nor sense of self, and the subject is released from the effects of karma and the cycle of death and rebirth. It represents the final goal of Buddhism.
For the last couple of years, i’ve been working as a Scrum Master and a Scrum Product Owner within Drupal Agencies.
The world is taken over by this “thing” called Agile and Scrum is one of the forms in which it surfaces.
As they say: Scrum is easy to understand but hard to master.
Specifically in Drupal Agencies there are some quirks and pitfalls when a team is trying to use scrum.
I like to take you on a bumpy ride through the challenges I’ve encountered trying to master Scrum in digital agencies using Drupal, although these hurdles are not restricted to Drupal. In having conversations with a lot of my peers I found out that there are a lot of great ways to make Scrum work, and I would like to share my insights on how to take the hurdles to reach Scrum nirvana, or at least be Kaizen :)
I think it will be recognisable for all you Agilistas out there.
The seven hurdles:
1. Scrum and Customers
“Sure we want this Agile thing! So where’s our functional design?!”
2. Scrum and Drupal development
Experts versus generalists, junior versus senior
3. Scrum and Human Resources
“We’re looking for a scrummaster, productowner and projectmanager in one who can lead the team!”
4. Scrum and Support
“Critical Security updates in the middle of a sprint.. again..”
5. Scrum and Technical dept
“New features are more important to the client then cleaning up your code”
6. Scrum and Projectbudgets
“Every team works at only one project at a time right?”
7. Scrum and Waterscrum aka ScrumBut
“We use Scrum in our own way, and call it Waterscrum!”
“We use Jira and post-its, so yes we are scrumming! A retro-what?”
This talk is interesting for anyone who has a basic knowledge of Scrum and Agile.