Weely Sprint Report needed.

Weely Sprint Report – Retrospectives
t is expected that during the next four class sessions each team will provide a Sprint Retrospective (regarding the accomplishments of the past Sprint.)  Since we are not going to do any coding, it makes sense to have a one-week Sprint and therefore we will have three retrospective meetings and the last meeting will be about team presentation on the project as a whole and on the product that “assuming” has been developed – more on the final presentation later.
What is Retrospective meeting?
Retrospective meeting is held at the end of every iteration/Sprint to discuss what really went well and what didn’t go well and any action items to carry over the next Sprint. Retrospective meetings are useful to identify the ways of continuous improvement of an Agile team. Retrospective meeting is NOT a backlog grooming session but past Backlog Grooming session(s) may be subject of discussion to improve teams practice on better BI Grooming.
Sprint Retrospective meetings can be facilitated by asking each person in the team to answer a variation on the above questions. Instead of asking what went well, what didn’t go well some teams prefer –
What should we start doing
What should we stop doing
What should we continue to do
Teams are asked to be specific in their answers so that effective actions can be taken. The retrospective meeting is usually conducted immediately after the Sprint review meeting.
It is recommended that the entire team participate in this exercise so that any issues or concerns that the teams face during the previous Sprint are addressed during the teaming and avoided in upcoming Sprints.
Sprint Report
Sprint report is a summary of what was discussed in the retrospective meeting (the three bullet points above) and you are expected to present that in about 5-10 minutes max. Additionally, you need to provide a brief review of where you are in your product design (that is, what have you accomplished so far,) show (in some form of visual aid) your conceptual design, a synopsis of the result of your Sprint BI Grooming session, report on expected Risks related to delivery and what is planned for the next upcoming Sprint.
Your report should not take more than 20 minutes. The report may be delivered by one person each time and a different person the next time – or, if you prefer, it could be presented as a team, i.e., each section by one person. Do remember that if you went over time, points would be deducted from your presentation assessment for the team.
If you find any part of this note ambiguous, please do not hesitate to ask.