R&D Management 6 min read

Guidelines for Conducting Retrospective Meetings in the Eagle Eye Financial App Project

This article outlines a structured retrospective process for the Eagle Eye financial app project, detailing how to create a safe environment, review iteration goals, collect data, identify improvement actions, set acceptance criteria, and strengthen documentation, testing, and requirement reviews to boost team efficiency and product quality.

JD Tech Talk
JD Tech Talk
JD Tech Talk
Guidelines for Conducting Retrospective Meetings in the Eagle Eye Financial App Project

The introduction explains the purpose of project retrospectives: to regularly review and adjust team processes, capture feedback, and improve iteration efficiency and outcomes, similar to rapid user feedback loops in product development.

The Eagle Eye project is a financial app that reaches users via SMS, WeChat, in‑app messages, and push notifications for acquisition, promotion, activation, retention, and re‑engagement, and the team seeks to maintain quality while meeting increasing business demands.

Retrospective meeting steps:

(1) Establish a safe environment, encourage open sharing, and set clear meeting rules.

(2) Review expected goals versus actual progress, using iteration data (card count, effort, completion, cumulative flow) to build consensus on goal achievement.

(3) Collect data: give each member 5 minutes in a quiet, safe space to write cards highlighting what went well and what needs improvement, then share these cards to foster self‑affirmation and team insight; vote on the top three improvement items.

(4) Define improvement plans for the selected items and set acceptance criteria to verify implementation in the next retrospective.

The team agreed on three action items with acceptance criteria:

01 Document improvement – use iteration‑3 requirements as pilots, link corresponding CFs in the management tool, record logic, issues, and lessons learned.

02 Strengthen test‑case review – ensure test cases cover business logic and data, be documented in product specs, delivered within two days after review, and notified by email.

03 Strengthen requirement review – set clear goals, schedule regular reviews, follow a defined review process (pre‑review PRD email, Q&A with developers/testers, change logs after Q&A), improving understanding and focus.

Using tools like X‑Cloud and CF has enhanced collaboration, face‑to‑face communication, and overall efficiency, while the retrospective reinforced goal focus and priority awareness.

Contact for the retrospective: HR‑Training & Corporate Culture, Jin Qi, 010‑89187643.

R&D managementproject managementprocess improvementteam collaborationRetrospectivefinancial app
JD Tech Talk
Written by

JD Tech Talk

Official JD Tech public account delivering best practices and technology innovation.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.