A Retrospective is a valuable way to improve how your team works together by reflecting on what has come before and using what you have learned to move ahead together. The authors present a structure with four simple questions to help you get started with using retrospectives in your team environment.
Last year Allan Kelly wrote an InfoQ article about a tool for retrospectives - Dialogue Sheets. A year and over 2000 downloads later he looks at how they are being used and ways they have been adapted in the wild.
DevOps@Nokia Entertainment is the first article of the “DevOps War Stories” series. Each month we hear what DevOps brings to a different organisation, we learn what worked and what didn’t, and chart the challenges faced during adoption.
Essential Scrum by Kenny Rubin is a book about getting more out of Scrum. It’s an introduction to Scrum and its values, principles and practices, and a source of inspiration on how to apply it.
Patrick Kua has recently published The Retrospective Handbook which provides practical advice on how to make retrospectives much more effective. 1
Dialogue sheets allow teams to hold facilitator-less retrospectives. They promote self-organization and encourage everyone to speak in the exercise. Resulting in great levels of participation. 10
This paper tells the story of the adaption process of agile software development with a focus on one mechanism – retrospective – we employ to guide team members realize the needed change.
The 'Retrospective Prime Directive' is often used during retrospectives to encourage learning without recriminations. Here a group of senior practitioners looks at its benefits and difficulties. 10
Why do Agile teams get stuck in the just-average "norming" stage, never making it to the exciting high "performing" stage of team growth? The invisible "learning bottleneck" can stunt performance. 16
When we discard traditional SDLC rules, how should we work? Rachel Davies explains how teams can use Retrospectives to reflect on their process and to improve it gradually over time. 3
As we practice various Agile disciplines, the effects of our words and actions actively create, and re-create over time, the environment in which our teams and projects operate - for good or ill. 3
Retrospectives are traditionally held at the end of a project - too late to help. Agile teams need retrospectives that are iterative and incremental, so improvement can start as soon as possible.