Agile Retrospective Meeting Techniques: 7 Practical Methods from the 7FRESH R&D Team
This article introduces seven practical retrospective meeting techniques—Thermometer, Emotion Meter, Emotion Journey, Practice Box, Problem‑Solution Board, and more—explaining their purpose, execution steps, and visual examples to help agile teams foster continuous improvement and stronger collaboration.
Author Introduction Wang Xin, Agile Coach at JD Retail Technology R&D Center, holds SAFe DevOps, SAFe 4 Certified Agilist, Certified Scrum Professional‑ScrumMaster™ and Certified Scrum Professional‑Product Owner™ certifications, with extensive agile practice experience.
Many people worship flashy theories, yet simple, practical ideas often achieve better and more lasting results. Regular retrospective meetings are essential for reflection, problem discovery, experience accumulation, and team cohesion.
NO.1 Thermometer Team members share their overall feelings about the project. Around 36°C is comfortable; higher temperatures indicate anxiety, lower temperatures indicate frustration.
NO.2 Emotion Meter Team members annotate specific emotions on a horizontal axis, identifying the causes behind each feeling. The lower‑right area highlights problems that need solutions.
No.3 Emotion Journey Similar to the previous method, but the horizontal axis lists major project milestones. Team members plot their emotional curve across the development timeline, revealing ups and downs and encouraging open discussion.
NO.4 Practice Box A box contains the team's agile practices, both effective and lacking. The board is divided into three columns: Drop (discard), Keep (retain), Add (try new). This visual helps the team decide which practices to eliminate, maintain, or introduce.
NO.5 Problem‑Solution Board The board has three columns: solved problems (left), problems with agreed solutions (center), and unsolved problems (right). This clear categorization lets the team focus on actionable items and prioritize them.
Summary Retrospective meetings must produce concrete, actionable solutions that are fed into the next iteration. Issues such as low feature usage, electronic board drawbacks, tight schedules, long business chains, ambiguous task splitting, front‑end dependencies, and frequent urgent requests should be addressed with specific counter‑measures. Sustaining effective retrospectives requires the Scrum Master, agile coach, and leaders to cultivate a habit and culture of reflection and continuous improvement.
(Image shows R&D team members expressing their viewpoints.)
JD Retail Technology
Official platform of JD Retail Technology, delivering insightful R&D news and a deep look into the lives and work of technologists.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.