Before you start with retrospectives, there are a couple of basics that you should take care of. Skip this chapter, and chances are that your retrospectives will suck and you can't figure out why.
As many options as there are to design a retrospective, there are just as many ways to muck it up.
Instead of suggesting specific formats (there are enough out there), this chapter presents guiding principles that help you build your own retrospective formats and enable you to anticipate what may work and what doesn't.
Everyone talks about creative retrospective formats. Reflecting about how to define great actions often falls short. Even though the value of retrospectives is highly coupled to the effectiveness of outcomes.
It's time to shift the attention!
There are many good ways to start a retrospective. In this post I would like to introduce three different retro check-in formats. Each check-in format fulfills a special one
Software development and predictable results go about as well as safe investment and casino. Too many – variables such as fluctuating productivity, unexpected problems, and new ones
The goal is clear: you want to develop a product that provides customers with high added value. You want to achieve an outcome with which team members and stakeholders alike