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

  • Yes, Hardware Can Be Agile!

    “You can’t do 2-week iterations with hardware!” This is the first thing you’ll hear when talk turns to Agile methods in hardware-software product development. A mix of existing robust hardware development ideas, plus a few newly taken from Agile software are being used now by real teams, even to get around - or through - the challenge of doing fast iterations.

  • Using Agile Retrospectives for Organizational Change

    The book Retrospectives for Organizational Change: An Agile Approach by Jutta Eckstein explores how agile retrospectives can be applied to initiate and implement organizational change. It describes the concepts for using retrospectives to develop a shared future and shares experiences of applying retrospectives to support change in organizations.

  • Interview and Book Review: Scrum Shortcuts Without Cutting Corners

    "Scrum Shortcuts Without Cutting Corners" by Ilan Goldstein is a must read book that delivers real world examples on how to effectively implement and embed Agile in your team or organisation.

  • Q&A with Jeff Sutherland on Scrum: The Art of Doing Twice the Work in Half the Time

    In his new book Scrum: The Art of Doing Twice the Work in Half the Time, Jeff Sutherland explains how the Scrum framework can be used as a general business practice to accelerate work of all kinds. An interview with Jeff about using Scrum outside software development, characteristics of great teams, increasing happiness, product owner teams, and on experiences from applying Scrum for education.

  • More Than LeSS

    While the agile community has come up with refreshingly new approaches to scale agile methods, these models still seem to fall short in addressing the organizational complexity around large projects. This article provides a holistic approach to scaling Scrum. It is based on LeSS, amending it to better face the challenges of large projects.

  • Q&A with Nadja Macht on Innovation, Flow and Continuous Improvement

    Retrospectives help teams to learn from their experiences and improve continuously. In this interview Nadja Macht, Flow Manager and Coach at Jimdo, talks about how to balance flow and slack time in teams, doing visual management with Kanban boards and deploying agile retrospectives for continuous improvement.

  • Kanban on Track - Evolutionary Change Management at the Swiss Railways

    Swiss Railways (Schweizerische Bundesbahnen, SBB) employed Kanban to transform a department from disappointing performance to predictable efficiency through a series of incremental improvements. The evolutionary nature of Kanban gained traction with early quick wins and resulted in better management and greater responsiveness to change. This is a brief report of their two year journey.

  • Culture is the True North - Scaling at Jimdo

    A lot of the pain that large and medium-sized organizations are facing boils down to scaling. It is not difficult to have 5-10 people working together in one room. However, as your business becomes more successful and your hiring increases, you will start to see problems. At Jimdo, the approach to scaling relies on three major factors: culture, communication, and kaizen.

  • Bug Fixing Vs. Problem Solving - From Agile to Lean

    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.

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

BT