A team meeting held after each sprint or project to reflect on what went well, what didn't, and how to improve processes.
Retrospectives (retros) are the primary mechanism for continuous improvement in Agile. Common formats include Start/Stop/Continue, Mad/Sad/Glad, and 4Ls (Liked, Learned, Lacked, Longed For). Action items from retros should be tracked and addressed in subsequent sprints.
Running a retro after the glossary expansion sprint to identify that automated testing should be added before the next major feature push.
Teams that run consistent retrospectives improve measurably over time — skipping them means repeating the same mistakes.
An iterative approach to project management and software development that delivers work in small, in...
A visual workflow management method that uses boards and cards to track work items through stages fr...
The simplest version of a product that delivers core value to early users and generates validated le...
A prioritized list of features, enhancements, bug fixes, and technical debt that represents all plan...
An Agile framework using fixed-length sprints, defined roles (Product Owner, Scrum Master, Team), an...
Need help implementing this in your business?
Get Started