Product Backlog and Burndown Chart
At the end of the first two-week sprint, during the sprint review meeting, you show interested stakeholders the questionnaire you distributed to students (about membership fees and how to store materials) and discuss the findings. Students indicated that they did not want advertisements cluttering the app, so you remove the Establish advertising requirement from the product backlog. Arwin considers the acceptance criteria for the questionnaire and declares that PBI done. You also demonstrate the Create Membership feature of the Android app. Because changes were made to this PBI that are not reflected in its current operation, Arwin does not declare it done, but rather moves it to the top of the product backlog, so that it will be included in the next sprint.
In your second sprint, you finish the Create Membership works on Android requirement and fulfill the Credit card processing requirement. Both are declared done by Arwin. At the end of the sprint review meeting for Sprint 2, you discuss your velocity and show your burndown chart. In your first sprint, you completed one small task (questionnaire) worth 2 story points, added PBIs (Web app works on MacBook, Web app works on PC, App works on iOS) worth 16 total story points, and deleted a PBI (establish advertising) worth 6 story points. In your second sprint, you completed one medium task (Create Membership works on Android) worth 4 story points and one large task (Credit card processing) worth 8 story points. Your average velocity, based on actual effort, at this point is (2 story points in first sprint + 12 story points in second sprint) / 2 sprints = 7 story points per sprint.
