Last Thursday we finished our first applicative sprint .There was another sprint (sprint 0) that focused on infrastructure and on the building of the skeleton of our application. Last Sunday we had two summary meetings about finishing the sprint: Sprint review meeting and Sprint Retrospective meeting.
You probably ask yourself:
· What are the purposes of those meetings?
· What are the goals of those meeting?
· What is the different between these two meetings?
· How those meeting can help me?
· Are these meetings a waste of time?
Please relax, I'll explain everything…
I'll start with the sprint review meeting. The main goal of the sprint review meeting is to present the project status on the end of the sprint. We usually invite managers, product owners, users and everyone who are interested to see the project progress.
For a good brainstorm we should demonstrate the product functionality (only a complete work that we committed at the beginning of the sprint). It will help us to clarify the items that will add on the next sprint.
On those meetings the team should talk about what went wrong and what went right on the last sprint.
The second meeting is the Retrospective. The main goal of the retrospective meeting is to look back on last sprint, and to think together how can we improve our enjoyable and productive work on the next sprint? The sprint review looks at "What" the team is building whereas the Retrospective looks at "How" they are building. In this meeting the team can talk about all the things that affect on the product development.