I love retrospectives. They’re one of the easiest and most effective ways of directly implementing an agile principle. (At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.) Retrospectives should be something that the team looks forward to because they know that it means that during the next iteration… Read More
Every now and then every ScrumMaster or Agile Coach meets a team that doesn’t show any of the Scrum values in their day to day interactions. This can be frustrating to the agilist, but to the team it can be psychologically harmful and have a severe impact upon their performance. Taking a lead from professional… Read More
I’ve been watching my team for a couple of sprints now, and I’ve generated some questions around how they groom stories. When stories are brought into sprint they are typically between 25% and 50% of the team’s average velocity. The ideal is that every story is around 6% to 10% of the average velocity. The… Read More
Our team is comprised primarily of relatively new staters, with all but one being here between four months and four weeks. One developer (let’s call him Jack) has been here much longer and is very familiar with the product. As I’m sure we’ve all seen in this scenario the team has developed a level of… Read More
This week is my first week with the team I’m going to be working with for the next few months. I started on the last day of sprint 28, which was also my predecessor’s last day. This week we setup sprint 29 and I broke the golden rule of not changing anything in the first… Read More
Are you getting full value from your user stories? Do you know why you’re writing them? Are the right people involved? Does everyone understand the work? Read More
The role of ScrumMaster is becoming more and more popular. As this popularity grows, so do the amount of people who are trying to break in. Here are five things I would advise any budding ScrumMaster to do.
Agile retrospectives are something that all agile teams are by now familiar with, to one extent or another. Retros are built into the manifesto in Principle 12; At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly. Retros were built into frameworks such as eXtreme Programming… Read More