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.
Patrick Kua has recently published The Retrospective Handbook which provides practical advice on how to make retrospectives much more effective. In this book Patrick draws upon his 8 years of valuable experience with retrospectives in real agile teams.
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. 11
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.
David Spann introduces Jean Tabaka's book, in which she shares stories and facilitation techniques to make teams and entire organizations effective, and provides templates to get them started.