Retrospective

The Mountaineering Retrospective is a simple and fun Retrospective that I came up with to help teams reflect on the bigger picture. Sprint Retrospectives tend to focus on the past sprint (what’s in a name), but it does help to occasionally apply a broader view. Using the visual metaphor of ‘climbing the mountain’, this Retrospective helps teams to look at their growth, and what is needed to continue, from another perspective. It takes around 45 to 60 minutes and a room with sufficient room to move around. Here’s how to do it with your team Preparation (although you…

As a Scrum Master, I love trying out new and different Retrospectives. It prevent the monotony of always doing the same thing (like a regular ‘plus/delta’). And it offers a team a new and different perspective to evaluate the process and learn from it. The ‘Team Radar’ is one of my favorites. It strikes a nice balance between reflection as a team and as an individual. It’s also one of the best methods to make transparent where a team agrees and where it doesn’t, automatically prioritizing what needs attention. Setting up Create a large Team Radar on…

In Scrum, a basic principle is to deliver working software at the end of the sprint. For a webapplication, it is often obvious what this entails. Other than the functionality to be delivered, it also includes such things as text labels, error messages, help texts and user documentation. But for content-oriented websites (such as company sites), this is more challenging. After all, many websites feature sections for news, maybe a portfolio of projects or customers, a profile and a list of services or products. Traditionally, many (smaller) webdesign shops approach these projects by first completing the website with dummy content…