Retrospectives are certainly one of the most important techniques used in Scrum as they form the foundation of the continuous improvement and adjustment to the context for the Scrum team. It is however not always easy to facilitate this activity with a bunch of software developers that are often mostly introverted.
Agile coaching for Scrum software development teams
When you observe a well-knit team in action, you’ll see a basic hygienic act of peer-coaching that is going on all the time. Team members sit down in pairs to transfer knowledge. When this happens, there is always one learner and one teacher. Their roles tend to switch back and forth over time with, perhaps, A coaching B about TCP/IP and then B coaching A about implementation of queues. When it works well, the participants are barely even aware of it. They may not even identify it as coaching; to them, it may just seem like work.
When your organization is thinking to adopt Scrum or is just beginning to use it, there are always questions that people will ask about how Scrum really works. As an independent Agile Coach, Roger Brown has collected 85 of them that he has arranged under major topics like people or technology.
Rachel Davies, the author of the book “Agile Coaching” published by Pragmatic Programmers, discusses Agile Coaching.
One of the cornerstones of Scrum is the self-organizing team: one able to make decisions in relation to the target to which it has committed. “Coaching Scrum Teams” addresses how to form groups of individualists into cohesive teams, where the members support each other and make use of each other’s strengths.