In the middle of the Sprint, the PM initiates a planning meeting with the client to pick features from the project backlog and move them to the next Sprint backlog. Also, the PM starts working on a specification for the next Sprint.
What else happens in the last few days of Sprint 1-N:
- Daily meetings
- Code freeze (day 9)
- Preparing of Sprint and test reports
- Product Demo (day 10)
At the end of the Sprint, the Project Manager prepares a Sprint Report with information about the time spent and time initially planned. Sprint Report also includes:
- List of completed features
- Not completed features (and why)
- Change requests (if any) implemented during the sprint
- Change requests not implemented during the Sprint (and why)
- Time spent, including bug fixes and change requests
Finally, the team works on the Product Demo. This process may take from 24 up to 150+ hours per Sprint. Before the Demo, QA team checks features added in the current Sprint as well as goes over the whole app making sure new functionality doesn't break the old.
Product owners test Demo for some time (for example, till the end of the working day). If the clients find any issues, they should list them. These issues must be added to Project Backlog and fixed at no additional cost.
Sprint 1-N deliverables:
- Builds on the stage (testing) server
- Sprint report
At the end of the Sprint, the team gathers for a Sprint Retrospective. It goes after the owners accept the Demo but prior to the next Sprint planning meeting.
The team discusses:
- What went well
- What could be improved
- How they're going to improve it in the next Sprint
Finally, let’s see how the release process goes.