Agile teams attempt to use Retrospectives as a tool for Team Improvement. Yet our improvements often lead nowhere. Consider making your improvements into concrete actions, or even full-blown experiments, and adding them to the Sprint Backlog.
This is at the core of our eBook: The Guide to Effective Agile Retrospectives – hint: plan your improvements into the Sprint, track them on the Sprint Backlog, and review them in the next Retrospective.
At an organizational level: Agile Change or Adoption: Define Small Organizational Changes
Bringing them into your Sprint: The Humble Sprint Backlog
- Plan of Action – the simplest approach here
- Improvement Stories – using an approach like User Stories to create actionable change
- A3 Experiment Template – a full blown experimental model
Mark Levison has been helping Scrum teams and organizations with Agile, Scrum and Kanban style approaches since 2001. From certified scrum master training to custom Agile courses, he has helped well over 8,000 individuals, earning him respect and top rated reviews as one of the pioneers within the industry, as well as a raft of certifications from the ScrumAlliance. Mark has been a speaker at various Agile Conferences for more than 20 years, and is a published Scrum author with eBooks as well as articles on InfoQ.com, ScrumAlliance.org an AgileAlliance.org.
*Thank you for visiting the World's Largest Opinionated Agile Reference Library. This content is created and the links are curated through the lens of Agile Pain Relief Consulting's view of what is effective in the practice of Scrum and Agile. We don't accept submissions and emails to that effect are marked as spam. Book listings may use affiliate links that could result in a small commission received by us if you purchase, but they do not affect the price at all. From experience, this won't amount to anything more than a cup of coffee in a year.« Back to Glossary Index