BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Assessment Content on InfoQ

  • 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.

  • Good Agile Karma

    Agile relies heavily on discipline, rather than genius. We're told that average teams, even in the early stages, can achieve dramatic performance improvement if they are disciplined. As we do these things, 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.

  • Book Excerpt: Agile Retrospectives: Making Good Teams Great

    Project retrospectives help teams examine what went right and what went wrong on a project. Traditionally held at the end of a project, they're actually too late to help - no wonder we call them "post-mortems". Agile teams need retrospectives that are iterative and incremental, to find problems and design solutions to help teams improve early on, when improvement yields the most benefit.

  • Book Review: Collaboration Explained: Facilitation skills for software project leaders

    David Spann, himself an experienced facilitator, provides an insightful review of "Collaboration Explained: Facilitation Skills for Software Project Leaders" by Jean Tabaka. Jean, an experienced teacher, consultant and coach, offers techniques to enhance group effectiveness, provides some templates to assure their first efforts are well planned, and tells some great stories along the way.

BT