Scrum is really simple, barely a process, more a framework. The hard
work in using Scrum is fixing the things that it exposes, actually
inspecting the things that it makes transparent and adapting to
optimize the results and the organization that produces the results.
Scrum is not the organization that produces the results, or the
amalgam of procedures, tools, automation, and standards that are
implemented as a result of the inspection, as part of the adaptation.
Scrum is the very simple mechanism that helps an organization be more
effective in accomplishing its goals.
I've been following the threads about type N, A, B, C and advanced
Scrum. Although these may represent the engineering, personnel, and
product management practices that an organization adopts as a result
of Scrum's inspect and adapt, they aren't Scrum. I think we are
mistaking the consequences of Scrum with Scrum itself.
What may be most destructive about these supposed extensions is that
they will divert people from the real work of Scrum ... seeing what is
going on in their organization and going through the change process to
become effective. And learning how to continually inspect and adapt to
keep their organization's practices optimal. Instead, people may think
that all of these things that use the Scrum name are advances in
Scrum, templates that they can mimic and then, amazingly, they are
advanced development organizations, also.
We are running the danger of any small process. People want to make it
bigger. Well, Scrum isn't bigger. Each organization's total ability to
build complex products is certainly bigger, and hopefully continually
evolving, but it isn't Scrum.
Scrum is really simple, barely a process, more a framework. The hard work in using Scrum is fixing the things that it exposes, actually inspecting the things...
... itself. Nicely said. Thanks for the clearing up the differences between the two; having a clear separation between the two (ie Scrum and the consequences...
... Thank you for speaking up Ken. Possibly the most refreshing post I've seen here in a year. It does seem that we in the Agile community (just like every...
... This is probably fair. However it seems that there are a set of other patterns "for" Scrum that work in multiple contexts. The thing that's great about...
Alex, I think you may have missed my point. I agree that there are useful patterns and techniques that can be applied to certain contexts in using Scrum or...
Alex, When we started collecting them at the gatherings, it started to look a whole lot like a methodology. Aside from patterns being written, and writing ...
What if inspecting & adapting is the core of the "advanced course?" --Hubert ... -- All opinions in this message are my own, and are not necessarily shared by...
Then it isn't an "Advanced ScrumMaster Course." It is a course for ScrumMasters to practice their craft. I have to wonder, though, because based on the below...
Ken and I have worked off-line to settle this misunderstanding. A few clarifications: - The course does not certify, nor replace the CSM course - The course...
... Yes, well. If it only takes a few days to be Certified, why would it take longer to become Advanced? That train already left. ... Do most of the people who...
Ken, I see your concern about people stopping thinking. I have a classic book on flying where the author at one point said, "And now I need to ask you to...
... This is definitely true; as I've evolved as a coach I've learned that there's a lot more value in nudging a team to discover a pattern on their own than to...
I like Victor's example of a chess book. We can read and read and study it. Then we use the practice in our first chess game and get whompfed, because we...
Lets follow the chess analogy a bit further: - There are perfectly viable courses in "advanced chess". Here, the meaning is clear - students learn how to play...
Definitely in the public domain. And, we as the Scrum community are responsible for its integrity and value. It works because of certain key values and...
... This for some reason reminded me about "Life Cycle of a Silver Bullet". This cute (or is it scary?) little 3 page anecdote even got pigs in it! See...
... I want to sign up for most of this, except for the part about common sense. If there is such a thing as common sense, it would be something that people...
... Like - People on your team don't like to work together. - People are selfish, and don't comitt to doing the "team's" work. - That the tools you have slow...
Reality is painful! I often see PMs that try to "manage by hope." They'll assign the team too much work, tell them when it "must be done", and "hope" the team...
... I suspect that the best way to accept the need for change and respond to it, is to have our nose rubbed in it: ... Yes, if we want to avoid doing the work...
You know that Scrum is gaining traction when all of the things that have been ignored to date become painfully obvious and you just wish you had never started...
Well said Ken. Jim ... From: scrumdevelopment@yahoogroups.com [mailto:scrumdevelopment@yahoogroups.com] On Behalf Of Ken Schwaber Sent: Tuesday, 28 March 2006...
... Yes, well put. (WTF have you BEEN!?!?) Scrum is a small simple machine that puts the team's work in clear view, from which they can figure out what to do...
... Agree, of course. So, then what is that infinite richness called (agile software development?), and where do we discuss it without codifying or branding...
... I don't think anyone said not to discuss it here, or not to codify it. Ken suggests that calling it "Scrum" (or "Agile" for that matter) suggests to people...