Lean has proved to be instrumental in moving beyond Agile to set up a practice of continuous improvement with direct effects on team performance and engagement. Making a clear distinction between bugs and problems has proved to be instrumental in this improvement.
We can view situations in our work as opportunities from which to learn how to better handle similar situations in future, by looking back and asking “How will I deal with future situations like this to improve my results?” PROspectives help us to reflect more often, independently of acute, unexpected problems and without time pressure, to uncover ideas for future improvements.
Schools use Scrum to help students to learn more effectively and develop themselves in an enjoyable way. The self-organized student teams work in sprints to learn subjects and evolve the learning process. Results from the agile way of working are improved quality of education, higher grades and motivated students. InfoQ interviewed people from several schools involved in teaching with Scrum.
A Retrospective is a great way to encourage your team or group to reflect on what has happened and plan for what’s ahead, constantly improving how you work together. This article provides some ideas. 1
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 in the wild.
This article is part of the "DevOps War Stories" series.Each month we hear what DevOps brings to a different organisation, what worked and what didn’t and 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. 8
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