Internal retrospectives are one of the most valuable tools to a successful software development project. They provide an opportunity to reflect on processes, communication, tools, and plenty of other things. The right forum for voicing concerns or #praise is not always obvious when you’re in the weeds of a project. This exercise aims to create a safe space where professional candor and feedback is encouraged.
There are several situations where retros can be employed: after sprints, at the end of a release cycle, at the conclusion of a one-off website build, and more. But in this article, I’ll cover something slightly different: a recurring full-team internal retrospective.
Read the full article on viget.com.