In Scrum, Sprint each end of the meeting there will be two (Sprint Review / Demo and Sprint Retrospective Review). This is a summary of two meetings a Sprint past, where the Review / Demo is checked past a Sprint output (What), mainly to check the PO based on previous results of the work program in the Team Sprint in the past, including some Demo, and a summary and analysis section unfinished; and retrospective review the past is a mode of operation of the entire Team Sprint, what good and bad practice, how to do better the next Sprint, emphasizing how.
Sprint Retrospective (Review)
Sprint Retrospective meeting was mainly to discuss the operation of a whole Team Sprint in the past, how to improve the functioning of the Team better. The discussion can be any questions about Team building, including workflow, team practice, internal teams / external communication, team atmosphere and the use of related tools and so on.
Scrum is not a method, but to provide a framework for software development process, under the overall framework of different projects, the team needs specific conditions, timely adjustment practices. And it is a chance Retrospective meeting Scrum team self-adjustment.
Participants of the meeting include the entire Scrum team, Scrum Master and Product Owner. The meeting was chaired by the Scrum Master, which of the following two general problems began:
1. A Sprint past years, we have what the bright side?
2. What problems in the past a Sprint exist?
The whole Team open discussion on these two issues, ways can be diverse. We can discuss together, Scrum Master course everyone in the discussion of views recorded on a whiteboard; Team also allows each member to write down their answers on paper notes may be required to write each question at least three points, then everyone put their answers posted on the whiteboard, and give relevant explanations.
After the completion of the discussion, to discuss the results for classification. For better convenience, the next Sprint continue to maintain and carry forward; for the problems listed in the Action Point to solve the problem. Action Point listed a Sprint backlog will be reflected in the next, and is a high priority project.
In the existing project management tools , I found now only project plus project management products specifically asked for this, there is a separate module to manage [ iterative review ].