A team of 38 people, divided into 4 sub-product groups, how to do a retrospective meeting together?
This is a large retrospective meeting, which lasts from 0.5 to 1 day. It is divided into two parts. The brief introduction is as follows:
①Collect data
a) Visualize the project
i. The CPO explains from the project as a whole (expected and actual deliveries, technical debt, etc.) on a large flip sheet for others to add to
ii. Different sub-projects, visualize the project status, including important emails, early designs, prototypes, important events, challenges, etc., written on stickers and pasted in a timeline. Finally add a feeling for the status of the project (good, bad, average ... ). Status drawings of different sub-projects are generally placed on the wall sequentially and horizontally.
b) group communication
i. For each sub-project, introduce the project status drawing
②Analyze the problem and draw conclusions
a) Establish a topic of discussion
i. Discuss within each group, select the top three problems with the highest priority and the corresponding reasons and solutions, and write them on the sticker
ii. Put stickers of all internal discussions on the wall, and each group presents the results of the group’s discussions in front of everyone
iii. Everyone disrupts the scope of the project, and groups freely according to the topics they are interested in, and conducts further discussions on the topics
iv. Briefly share the final conclusions of all topics ( 12 in total), and the first three with the highest priorities are the ones that need the most attention at the large project team level
The above practices come from our own practice and the sharing of Joakimsunden . Among them, the most likely to prolong the time is that each group does the status drawing. It is recommended to do it in advance, which is very efficient.
