In this conversation, Luke Hohmann discusses a new approach to conducting enterprise retrospectives that overcomes the limitations of traditional models used in Scrum projects. A scaled retrospective is a meeting where multiple Agile teams come together to identify critical organizational improvements and create a viable method for delivering and tracking …
You have been doing Agile for a few years now. With a regular cadence you have retrospectives and a lot of problems and great improvement opportunities are raised but you don’t seem to really improve. Let us put your retrospectives on steroids with the Toyota Kata.
Over the past ten years, software development teams using Agile approaches to work have adopted retrospective meetings as a critical practice for learning and continuous improvement. To the extent that practitioners say, “If you’re not holding iteration retrospectives, you’re not doing Agile.”
You have been doing Agile for a few years now. With a regular cadence you have retrospectives and a lot of problems and great improvement opportunities are raised but nothing seems to really improve. Stop doing retrospectives!
This session tells the story of how a team comprising of marketing, customer support and agency relations experts used Scrum to improve its communication and alignment. It will look at what went well, what we could have improved, what failed utterly and what we learned in the process!
Similarly to design patterns, present pedagogical patterns solutions to recurring problems in a given context. The wider context for the pedagogical patterns is teaching and learning, especially of technical subjects.