If you’ve been curious about Scrum and begun learning or exploring it, you’re the person I wrote my FAQ for.
I’ve had so many people ask me about Scrum over the years.
I would mostly answer questions ad hoc or point them to an article I had found helpful.
That FAQ section turned out to be more extensive than I initially planned. Mostly because I realized there are A LOT of questions people have about Scrum.
After working through almost 100 questions, here are 3 takeaways that surfaced for me.
While it’s a bit cliche, the saying certainly holds true.
Scrum is quite simple by design. And its power is in the daily application of this simplicity. It's not easy for an individual to alter their behavior and can be pretty challenging for teams or organizations to change.
And this is why scrum can be hard to master.
Scrum requires you and your team to work in a new way, and it’s tempting to import old behaviors or schemas that aren’t very compatible with Scrum.
I often get asked if the current team leader can just be the scrum master and product owner. Or how to add all these new scrum meetings on top of all the current meetings.
Both of these questions come from a desire to hold onto the old while trying to embrace the new. You can’t do both.
Questions abound again regarding the relationship between Scrum and the team or the organization.
Knowing all the pieces of Scrum is the first step, but these questions illustrate how learning the parts doesn’t equal understanding the whole.
Leaning Scrum for the first time can be a bit overwhelming. There are many new terms and concepts in Scrum.
Well we’re here to help.