In scrum, The Sprint plan meeting is the most important event, and the second important event is the review meeting, because this is the best time for the team to make improvements. If you do not review it, you will find that the team is making the same mistake again. After the sprint review meeting, the team needs to hold a review meeting. I will list the main content of the meeting below. (The following meetings are from scrum checklists and scrum-and-XP)
Meeting content
Target
Improve team productivity by summing up previous practical experience.
Meeting preparation
- Participants: Scrum master,All team members ,Product owner (optional)
- Ancillary tools: highlighter, sticker, whiteboard magnet, whiteboard and board mounted for all participants
- Prepare a review whiteboard in three columns. The first and second columns review the past, and the third column looks forward to the future.
- Good: What can I do if I redo the same sprint?
- Cocould have done better:What should I do if I redo the same sprint?
- Improvements: thoughts on how to improve in the future
Meeting process(1-3 hours)
- Introduce the objectives and agenda of the meeting
-
- Preparation(Setting the stage): develop and review team values and conventions (Team values and working agreements): (10-30 minutes)
- No matter what problems we have found, we must understand and firmly believe that everyone, through what they knew at the time, has the skills and resources they can get, in a limited environment, all of them did their best to make the best achievements
- Everyone participates
- Honest Communication
- More I, less use you
- Do not delve into the internal problems of specific business details
-
- Collect data: Collect hard data: events, metrics, and completed stories.
- Events: any events that are important to everyone in the team, including meetings, decision points, milestones, and adoption of new technologies, suchWhether the improvement items identified during the previous review meeting were implemented
- Measurement: contains the combustion chart, speed, number of bugs, number of completed stories,CodeNumber of reconstruction, etc.
-
- Generate insights: ask "why" and find out the advantages and problems from the collected data.
- Explain to attendees how to use the sticker for work: when using the sticker, note that only one sticker is recorded.
- Distribute stickers and brainstorm all the ideas on the three columns of the whiteboard.
- Determine the improvement items (decide what to do)
- Each person has three votes and votes to determine which improvements will be made in the next Sprint (about 2-5 items ).
-
- Close the audit spective)
- Make a summary of the meeting to show which practices should be tracked in the next review meeting
Meeting results
- Review the whiteboard and the practices to be improved in the next sprint. In the next review, we will track the implementation of these improvements.
- Increase the barrier to the barrier backlog.
Others
Agile topology spectives: making good teams great
Project
Except spectives:A
Handbook for Team reviews
Http://www.retrospectives.com/
Resources on Alibaba spectives
Recommended:Online e-books you may need
Agile individual Sina apron:Http://q.t.sina.com.cn/135484
You are welcome to reprint it. Please note: Reprinted fromAgile personal website
