Why is our Scrum course organized the way that it is?
First, is a Scrum Team organized?
Well, a good Scrum is usually described more as adaptive than organized. Of course, we can debate the meaning of these words, during a day or during a sprint, or during a release. I would rather that the Team be adaptive than follow an organized plan, as one example.
This is one small reason our Scrum course is not organized in a strictly logical way.
Second, why do Scrum Teams fail?
Well, there are many reasons. Do Scrum Teams have a problem because Scrum is too complex? No.
The attendees have no problem with the explicit knowledge around the bare framework of Scrum, but they do often have problems ‘getting it.’
In fact, the bare framework of Scrum is very very simple. (On purpose.) Understanding the explicit knowledge around that is quite easy.
Hence, I am not worried that I need to organize the course so that the attendees build in their minds ‘complexities upon complexities’ about Scrum. If Scrum were complex, for example, like calculus, then we would have to organize the course a different way.
Again, Scrum is ‘holistic’ or interdependent. One cannot understand one part of Scrum without understanding how it works or plays with another part. ‘No man is an island’ as John Donne famously said. So, I like to continually weave from one thing to another, so this weaving becomes embedded in the back of the minds of the attendees.
One of the key problems is tacit knowledge. Getting the tacit knowledge and all that it means into their heads. Honestly, not just into their heads, but their hearts, their souls, their guts, their bodies.
Continues in Part 2, tomorrow…