Agile Retrospective: Making Good Teams Great | Book Series


This book focuses on how to fix the problems on a software development project and streamline it. An Agile retrospective happens at the end of an iteration in Agile software development (ASD) cycle. During the retrospective, the team says on what happened in the iteration; what went right; what went wrong and identifies actions for improvement going forward. The contents of the book take us through significant information like how to architect retrospectives in general, how to design specifically for your team and organization, how to run productively, and how to scale these techniques up throughout the project not just at the end.


Esther Derb

Diana Larsen

Published In:



Impediment | Glossary

Impediment in Software development, is anything that slows down the team from delivering the intended result or output. It can be any issue like lack of resources, bugs in the source code, a team member falling ill and so on.

Further Reading

  • “Scrum: The Art of Doing Twice the Work in Half the Time”, Jeff Sutherland
  • “Essential Scrum: A Practical Guide to the Most Popular Agile Process”, by Kenneth S. Rubin.

Know more about overcoming impediments by signing up for our workshops by visiting our website.