Complete the following after each sprint throughout the semester.
Sprint Zero Retrospective
In 1-2 pages (bullets OK), what are each of the following as it relates to your new group?
Project Mission
Initial Group Roles
Processes to be followed
Initial feature list
Initial plan/schedule
Initial Hardware/Software needs/setup
Anything else pertinent to sprint zero or the upcoming sprint 1
Sprint 1 Retrospective
This retrospective will be completed in 2 parts.
Part 1
Each Team Member should answer the following questions in bullet form, and each member's results should be included in the final submission.
What should the group start doing?
What should the group stop doing?
What should the group keep doing?
Part 2
The Group should answer the following questions for submission. The first three are based on individual answers to part 1.
What should the group start doing?
What should the group stop doing?
What should the group keep doing?
What work was completed in sprint 1?
What lessons have been learned thus far?
Sprint 2 Retrospective
These restrospective includes 2 parts.
Part 1
Each Team Member should answer the following questions, and each member's results should be included in the final submission.
What have you completed so far as an individual team member? Provide evidence similar to what you might present to the product owner in a review meeting (screenshots, artifacts, etc).
Are you proving valuable in an agile environment that relies on "strength of the individual rather than strength of the process"?
Part 2
The Group should answer the following questions for submission.
Looking back at the sprint zero plans, in the project progressing as planned?
Has the group started/stopped/continued doing the items laid out in the sprint 1 retrospective?
Scrum Results
In a well organized paper, groups should summarize their scrum project experience. The following outline has been provided as reference.
Product
Problem description (at least partially from original brainstorming activity notes)
Initial requirements (at least partially from original brainstorming activity notes)
Listing of user stories and final status (Complete Sprint 1,2,etc., Partially Complete, Not Started, etc.)
Results of limited development cycle: code/class description, environment/tools used, screenshots/storyboards of product in action
Process
Sprint analysis: How did each sprint go, including Sprint 0?
User Story Quantitative analysis: # Completed, # that needed refactoring, accuracy of story point estimates, Estimation of Actual Story point length in hours of effort, anything else that you may fine relevant.
Burndown Chart: a copy of your burndown chart (well-cropped photo or electronic representation) with analysis. Why are the graphs shaped the way they are? Are there any trends developing? How do you think it compares to other burndown charts (in the class and in industry)?
Project
Team - How was your team organized? Roles?
Lessons Learned - a well organized description of the lessons learned for this project - potential areas to address are Schedule, Quality, Estimating, People, Process, Technology, Roadblocks? (This part will be a significant part of grading for this paper)
Future Plans - What would the next step be for this project?
