Completing a Sprint

The team works hard during the course of the Sprint to complete the Sprint backlog items. The Burndown chart shows the regular progress of the team and how the backlog burns over the course of the Sprint. At the end of the Sprint, the team needs to get ready for the Sprint review or demo. And finally, the team completes the Sprint backlog.

While working on the backlog items, the team finishes the technical tasks created during the Sprint. Multiple team members work on different technical tasks for a Story. During the course of the Sprint, we also need to mark the Story as completed or done. While working on the task board in GreenHopper, if you are completing the last technical task for a Story, it allows you to change status for the parent task or Story also.

To change the status of a Story during the course of the Sprint once it is done (when you mark the last technical task as done), you can also mark the Story as done.

As shown in the preceding screenshot, you can choose...