I wanted to introduce you to the cause and effect clock as a workshop tool for coaches AdvertisementsRead More The cause and effect clock for agile coaches
In my last article, I talked about “story walls” but in fact, I focused on task walls. The difference is minor but choosing one over the other can help improve collaboration among the team. Task walls, predictably, are about tasks – “today I will do task 1” while story walls focus on the thing being […]Read More Notes on story walls – story or task?
Some different sets of questions to ask when doing retrospectives.Read More Different Retrospectives and pre-mortems
[Editors note – this is a long an obscure article that made sense to me and some people I explained it to. If it is not making sense half way through abort rather than continuing … it either makes sense early on or does not make sense at all] I was running an agile course […]Read More Dealing with baddies on agile projects
I went through this quick meeting with an agile class recently and I said I would post this for the crew to refer back to. In agile teams there are a couple of core roles and then the rest depends on the kind of work the team does. But we can give some more clarity […]Read More Clarifying agile roles – speed dating?
I just wrote a couple of entries on “velocity” and now I want to look at some of the implications of using it. Here I will be looking at how we interpret velocity and how we can use it. In particular I will be looking at how it relates to concepts such as “done”, “regression […]Read More Velocity is great but meaningless on its own
In my last article I gave a brief description of “velocity” and how I might use it in a training course. I ended up measuring progress in “coffee points.” This allowed me to plan my training topics and to share our progress during the day with the students in the class so we could continuously […]Read More What does a velocity chart look like in an agile team?