retrospective
|
Book Review: The Retrospective HandbookSteve Berczuk reviews Patrick Kua's book The Retrospective Handbook: A Guide for Agile Teams. Among the issues Kua addresses are how to lead a retrospective when you are part of the team and how to deal with retrospectives with distributed teams. | 
|
|
Why People on Agile Teams Need FeedbackAgile teams work by continually improving, and feedback is essential for agile methods to work well. Giving feedback to your team members and peers is hard, and receiving it is sometimes harder, especially when it’s not delivered with the right amount of thought. |
|
|
Why Retrospectives Are Important in Agile Software Development Periodically reviewing how things went—and looking for ways to improve—is an essential part of agile software development. Retrospectives are one way to do this, but it’s important to understand that there is a difference between a structured retrospective and “just talking about what happened.” |
|
|
How to Avoid Poorly Conducted Sprint RetrospectivesThe sprint retrospective is an important ceremony in Scrum. Of course, it’s bad if you don’t perform retrospectives at all. However, more often than not, it is not the retrospective itself, but rather a poorly conducted retrospective that results in an ineffective, stale, and meaningless effort. | 
|