Retrospectives help teams to learn and improve their way of working. Several agile coaches have scaled retrospectives to cover larger projects or programs with multiple teams. Let’s explore how they did it.
Two video lessons covering agile coaching and organizational change were released by Pearson/Addison-Wesley in the last quarter of 2012. They provide a different way to increase knowledge on agile adoption for visual and audible learners.
To become more flexible, durable and increase organizational effectiveness, retrospectives can be used in adopting agile. Some experiences stories and examples of how teams use retrospectives as a sustainable and adaptable solution for agile adoption, to implement continuous improvement with them.
Double-loop learning can be a great model for encouraging transformational improvements in teams by challenging key assumptions and strategies. Retrospectives and Lean Startup provide a framework to incorporate this learning model.
Tony Wong, a project management blackbelt, enumerates some practical points on individual procutivity. This article wonders how well these apply to software development and contrasts his list with that of other lists.
Usually failures result in anger, frustration and playing the blame game. However, failures are wasted if there is no learning from them. How can Agile teams make failures beautiful?
Retrospectives and feedback loops are at the heart of any successful Agile/Scrum implementation. They’re the tool we use to help teams improve. Yet in two day introduction to Agile classes they often get glossed over. Lacking time trainers (including this one) often race through the topic outlining only one simple type of retrospectives.
Angela Harms recently blogged about the Agile Retrospective Prime Directive. She discusses how the language of the prime directive around "everyone doing their best" could be seen as patronizing and insulting to team members. Other commentators who have discussed the intent of the Prime Directive include Esther Derby and George Dinwiddie. How useful is the Retrospective Prime Directive?
James Carr recently published a list of five rules to help improve the effectiveness of retrospectives. The rules are based on his experiences in hundreds of retrospectives, both successful and not.
It is often assumed that once the pilot Agile teams are successful, the process of Agile adoption is on the right track. Dave Nicolette shares very intriguing insights into situations where the adoption failed even after very successful pilot implementations.
Many consider the retrospective to be an agile team’s most powerful tool for continuous improvement. The retrospective captures learning and insights while experiences are fresh, and the lessons are immediately applied to the teams on-going work. A discussion on the Retrospectives Yahoo Group examined how to adapt a retrospective to work across multiple sites, with a distributed team.
A month has passed since Agile 2009 and there is now a good variety of feedback on the conference, the sessions and what participants found most valuable.
Once all your teams use Agile and are busy implementing local improvements, what happens to the larger organization formerly called "IT" or "Systems Development"? A coach with a large Agile program shared the strategy they designed to let the larger community spot trends and benefit from all this learning. Paulo Caroli calls it "Retrospective of Retrospectives".
Agile retrospective helps the team examine what went well during the past sprint and identify the areas of improvement for the future sprints. However, sometimes the exercise of conducting a retrospective ends up as a futile effort due to lack of preparation. Moreover, key members of the team end up either not attending or not participating in the meeting.
A sprint burn-down chart tracks the size of the sprint backlog over the course of the sprint. During the sprint retrospective, the burn-down chart can provide valuable data about how the sprint went. Mike Sutton uses annotations to capture more data on the burn-down chart, making it even more useful during the retrospective.