This is the end... (of sprint)

Yeah !!

All sprint backlog items are done, and then what?

If you have accomplished all of your tasks before the end of the sprint, there are still a couple of things you can do:

• Refactor your code in order to improve code readability, reusability or structure
• Help prepare the review
• Add details, acceptance tests to user stories
• Write unit tests for non tested existing code

---

Nope...

What if we did not finish on time?

When sprint goal is not met on time for the review, there are two solutions: Either you postpone the sprint review if everyone agrees or you only showcase the completed user stories. Incomplete user stories will be showcased in an incoming review. You should not present partially developed user stories because the customer will not be able to give proper feedback.

At the end of each sprint, a sprint review meeting is held. During this meeting, the Scrum team shows what they accomplished during the sprint. Typically this takes the form of a demo of the new features.

The Product Owner is responsible for preparing the review and leading the demo.
This is the most important time of the sprint.

How to Prepare the review?

• List what has been achieved during the sprint
• Integrate missing tests
• Investigate code quality and keep your issues up to date
• Be sure your user stories' branches has been merge into master
• Individually test your user stories on the master branch
• Prepare your demo by featuring the sexiest user stories first
• Completely rehearse your demo at least once before the review

---

Just before the review

• Get your workstation ready
• Launch the scripts (localhost... )
• Use a clic display tool (i.e. key-mon )
• Ultimate rehearsal of the demo

---

During the review

The demo is done on the master branch.

• Be commercial!
• Focus on good/positive points
• Do not speak with future tense (the demo is about what has been done and not what will come later)
• Be sure someone is taking notes
• Do not hesitate to let code owners answer questions if they are concerned
• Lead the demo (i.e. postpone a question if the actual moment is not suitable)

After each review, it is time for the scrum team to meet up and analyze the PROs and CONs of the past sprint (basically what went well/wrong).

---

During the Sprint Retrospective, the team discusses:

From www.scrum.org: The Scrum Master encourages the Scrum Team to improve its development process and practices to make it more effective and enjoyable for the next Sprint.
During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of “Done” if appropriate and not in conflict with product or organizational standards.

By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint. Implementing these improvements in the next Sprint is the adaptation to the inspection of the Scrum Team itself. Although improvements may be implemented at any time, the Sprint Retrospective provides a formal opportunity to focus on inspection and adaptation.

After the retrospective, it is time to fill in your next sprint backlog.
Don't forget to take the customer's feedback during the review into consideration. If you don't remember how to start a new sprint, go back to previous workshop

An awesome sprint review !

So, to WOW your instructors' panel, rehearse at least once your demo with :

• An introduction about the client, your team, and the solution you will provide to customer.
• A demonstration of features you finalized during this sprint
• A conclusion of the sprint and an opening on next sprint

A sprint retrospective artifact !

Spend some time with your team to think about how this sprint worked. Led by the scrum master, choose one of this workshop to talk about how the team works :

• 4 Ls: Liked – Learned – Lacked – Longed For
• Speed boat: an agile method to discover
• Or any of those listed on that site : the Hyper Island toolbox

When you'are done, call your instructor and discuss about how you will improve your team working methods.

A report to client based on client feedback !

At the end of your demo, your client (played by the teaching team) gives you some advice about your delivery.
Summarize all those feedback in a mail.

The report of a review is usually done by an email that you send to the customer. Remember to copy all participants, including trainer and campus manager, and copy the content of the mail onto a gist.
Here is the framework of a good report:

• Thanks the customer (thank you for coming...)
• Lists all the feedback he made about the demo
• Details the content of the next sprint, what the team has positioned itself on as a task for the next review
• Reminds the date of the next review (which was defined during the meeting)
• If your customer has told you that he or she will send you documents or put you in contact with a particular person, remind him or her in this email.
• Signed on behalf of the entire team