At the end of each sprint, Agile (scrum) teams typically do two things: a sprint review and a sprint retrospective. The sprint review focuses on the project code itself. The sprint retrospective focuses on how the team’s processes worked and what could be changed to improve the functioning of the team. While these two activities are related and sometimes confused or combined, you should do them as two separate activities. Alternatively, do the review followed by the retrospective, if you need to do it in one sitting.
The sprint review often involves a report and demonstration of the current state of the program to all stakeholders. Ideally, you should meet with your community partner and show them what you have done so far. You will show the class something similar in the demonstration. And you will also summarize this in a report to your instructor. The sprint review should be lead by the current Product Owner, since it focuses on the advances made in developing the product (app).
The sprint retrospective is a time in which you should discuss as a team how well the nuts and bolts of the team roles and organizational tools are functioning. This discussion is often facilitated by the Scrum Master, whose role it is to organize the inner workings of the team. One framework is to talk about what specific things the team should start doing, what it should stop doing, and what it should continue to do. Write down you ideas and turn them in as a document (in Pioneer Web).
Finally, plan what you will accomplish in Sprint 2 and prioritize each item. Ideally, this would be done in conjunction with your community partner. Unlike the plan for sprint one, you only need to list the new objectives/user stories for the next round of work and include a description of any new tests you will be creating for this sprint.
What to Turn In
Turn in one document for all three parts. You only need to turn in one copy for the entire team. Submit this in PioneerWeb. This document should include:
- A brief summary of what you have accomplished during sprint 1. We do not expect that you will have made much headway on the project code!! What have you learned so far about your project? What have you done?
- What user stories or feature specifications do you have from your community partner? Include any screen sketches or drafts of page layouts that you have created so far. Do you have UML class diagrams for the objects that will be in your database? If so, share them!
- A review about how the team is functioning. What is working and what should be changed?
- What do you plan to do for sprint 2?