Scrum Project 7.0

I. Content

1. Review the theme of the organization: "How can we do better in the next sprint?"　　"Time: Set to 1-2 hours.　　Participants: the entire team.　　Place: able to be discussed without interference.  Clerk: Designate someone as a secretary, prepare, record, and organize. 2. Review process

• Sprint Summary: Scrum Master shows you the sprint backlog, with the help of the team, summarizing the sprint, including important events and decisions.
• Take turns: Everyone has the opportunity to speak his mind without being interrupted: what he thinks is good, what can be done better, and what needs to change in the next sprint.
• Productivity Analysis: Compare the pre-estimated productivity to the actual productivity, and analyze the cause if the difference is large.
• Improvement: At the end of the day, the Scrum master summarizes the specific recommendations and concludes where the next sprint needs to be improved.

Two. Sprint Review Summary

We completed the compound interest calculation, the simple interest calculation, the interface setting, the computing function's Web application and so on in a sprint sprint, the whole process of our team launched the daily meeting, everyone tells about their own tasks and the difficulties encountered, because the Team Foundation is not very good, the process is more difficult, But we have also solved some practical difficulties, such as how to implement our computing and interface design on the Web page. We from the original idea to do an app, to the current computing function on the web version, because the development of Android is not very familiar with the need to learn, and the Web page class of contact, Web version as long as can open the Web page can be used, so you can reduce the cost of user download installation.
Productivity Analysis:
According to our Burndown chart, our actual curve is always above the ideal curve, a little gap, indicating that our efficiency is not up to expectations, the reason is that our foundation is not too good, the completion of a task point than expected to spend more time, encountered difficult to solve the problem will be stuck in that place can not go forward, And the team's task progress is not quite consistent.

Image:

Scrum Project 7.0