Again, you are asked to “report to management” about your progress not only on the project itself but also on how the team is functioning.
For the sprint review, summarize what you have accomplished during this two-week period. What user stories or features have you worked on? Have you completed any? If you are calculating velocity or using some other measure to evaluate progress, what are those numbers?
For the sprint retrospective, report on how your team is functioning and how your team has changed during the term. Have you rotated roles? Did you keep roles throughout the term? How often did you meet and where? Did that evolve over time? What have you as a group learned about Agile development as part of this project?
Finally, plan what you will accomplish in Sprint 5 and prioritize each item. Ideally, this would be done in conjunction with your community partner. During this last sprint, it is important to review your documentation, task list, and any materials that you will pass along to the next development team. Alternatively, if you think your project is ready to hand over to the community partner, what do they need to know in order to run and maintain the code? What documentation will they need to use the code you have created?
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 4. What have you learned so far while working on this project? What have you done?
- How would you measure your progress this term? How many user stories did you complete or tests that you wrote? What metric are you using and what is the current “score”?
- A review about how the team is functioning.
- What do you plan to do for sprint 5?
