As a Scrum Master, I use a variety of different tools to help facilitate Sprint retrospectives. In this article, I’d like to specifically show you how I use Mentimeter to quickly gather data from the teams whilst working remotely. Icebreaker I always start with an ice breaker. I use a variety of different ice breaking […]
In part 2 of the Ctrl + Alt + Delete: Rebooting a Team series, we take a look into the next step of rebooting a team and learning more about each other as individuals. We’re going to run through a technique that allows you to reveal what skills the people in your team already have […]
Has your team lost motivation? Is it more a group of individuals doing work, instead of a group of people greater than the sum of it’s parts? Are there many arguments, none of them constructive? Well, maybe it’s time for a team reboot. In this article, I’ll show you to reboot your team and get […]
n this article we review how to measure team performance with a sprint score. The primary measure of progress for a scrum team is “working software”, however, by using some basic empirical data, you can get a quick overview on how your teams are doing in general. Armed with this data, you can decide as a team what to improve next.
In this article, we look at when scrum meetings occur in a typical 2 week sprint. In fact, this is the exact setup I use for one of my scrum teams. I hope it helps you plan your upcoming sprints.
The Team Retrospective is one of the most valuable Scrum meetings and has one clear purpose, to identify at least one improvement that will be enacted during the next sprint. In this article, we’ll get you started on how to run a great Team Retrospective