BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Retrospectives Content on InfoQ

  • Retrospectives Applied as “PROspectives"

    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.

  • Scrum for Education - Experiences from eduScrum and Blueprint Education

    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.

  • The 4 Questions of a Retrospective and Why They Work

    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.

  • Dialogue Sheets Revisited

    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

    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.

  • Interview and Book Review: Essential Scrum

    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.

  • Interview and Book Review : The Retrospective Handbook

    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: A new tool for retrospectives

    Dialogue sheets allow teams to hold facilitator-less retrospectives. They promote self-organization and encourage everyone to speak in the exercise. This results in great levels of participation in and higher energy levels in teams. The sheet itself is A1 in size, 8 times larger than a regular sheet, pre printed with instructions and questions to motivation discussion.

  • The Retrospective Practice as a Vehicle for Leading Conceptual Change

    This paper tells how we coached the adaption process of agile software development in a specific company, with a focus on one mechanism – one-hour retrospectives – we employ to guide team members realize the needed change and let them lead it. From our perspective, the stage in which team members start facilitating the retrospective sessions by themselves is a landmark of success.

  • Questioning the Retrospective Prime Directive

    The 'Retrospective Prime Directive' is a practice used by many teams as part of their continuous improvement cycle. As outlined in Norm Kerth's book, it is intended to foster the deep learning that is the heart of a retrospective. This article is an enlightening conversation, captured by Linda Rising, between senior practitioners on the benefits and the challenges of using this practice.

  • The Secret Sauce of Highly Productive Software Development

    When Agile teams get stuck in the just-average Norming stage, rather than continuting to the exciting, high Performing stage of teamwork, sometimes they're suffering from an invisible "learning bottleneck" that stunts team performance. Agile practices require us to take time to reflect and learn - and a team that learns quickly succeeds.

  • How To: Live and Learn with Retrospectives

    Traditional SDLCs say how interactions within a team and between teams should happen; a prescription that doesn't always fit or isn't followed consistently. Rachel Davies explains how retrospectives allow teams to improve their processes by reviewing past events and brainstorming new ideas, and shows how to facilitate a retrospective for your team.

BT