What does the Scrum Team look like in context? In ScrumLand there are many many pictures of this. Here is one that is a bit different. In this case, the context is not the process but other things and other people. See here: One could start many places in describing this picture. I’ll start this […]
As with almost everything in Scrum, the purpose of the Sprint Burndown chart is to help the Team. First, we assume the Team (the whole team, including the implementers, the PO and the SM) are adults. And, as adults, they want to be successful. In every dimension that is relevant: more fun, higher quality, more […]
I enjoy everything Jeff Sutherland writes about Scrum. I found this document (see below) on OpenView Partner’s website (Jeff Sutherland is affiliated, especially regarding Scrum). In this case, I do not know for sure that he wrote this document (Executive’s Guide to Scrum), but I do know that, even if he did not write it all, […]
Here is a fairly recent Google Talk by Jeff Sutherland. (Late 2014.) The talk gives some key ideas from his recent book, “Scrum.” The talk is long, about an hour, but you can stop it any time.
It seems many people expect Scrum to make magic happen by itself. This is of course an illogical expectation. It is true that Scrum (the roles, meetings and artifacts) will, with a bit of introduction, cause your team to get better without much additional effort or investment. But the real power of Scrum comes when […]
All of you should be aware of the Agile Manifesto and the Agile Principles. To me, they are not perfect, but they are an excellent expression of many key ideas behind Agile. And we should be thinking about them every day. They require thought and common sense to consider how they should be applied on […]
To be honest, Scrum itself doesn’t ‘do’ anything. Scrum is just a basic framework that gives you some practices, etc (and includes some values and principles). It depends mostly on the people in the field, or, we might say, in the Team. Scrum will immediately help in some ways. But its main value, IMO, is […]
As you may know, I think in Scrum it is key to aggressively attack impediments. I think each Team should have a (mostly) public impediment list. The SM should be attacking the top impediment each day. This ‘kaizen’ should lead to improvements in velocity. Every Team can get better. Always. An impediment is anything (anything!) […]