Report and Reflect on Sprint 2; Plan Sprint 3

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, take a moment to review this article on the Five Stages of Team Development.  What stage is your team currently at? Try to be honest. It is not uncommon for teams to be storming, at least occasionally, at about this period. 

Finally, plan what you will accomplish in Sprint 3 and prioritize each item. Ideally, this would be done in conjunction with your community partner. What barriers do you anticipate could cause your team to regroup and learn new skills  (this is called a “spike” and usually does not count against you in measuring velocity or effectiveness)??

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:

  1. A brief summary of what you have accomplished during sprint 2. What have you learned so far while working on this project? What have you done?  
  2. A review about how the team is functioning. What is working and what should be changed?  Which of the 5 stages are you (usually) in right now??  If your team is struggling, what can the Scrum Master try to do to improve the team functioning?
  3. What stage are you in developing tests for your code?  Even if you are not follow TDD processes, you should be creating unit and regression tests as you code.
  4. What do you plan to do for sprint 3?
The views and opinions expressed on individual web pages are strictly those of their authors and are not official statements of Grinnell College. Copyright Statement.