7.0------------------------------------------------
Sprint Review1. Review the theme of the organization: "How can we do better in the next sprint?" "Time: Set to 1 hours." Participant: Guang Shang department store team. Venue: Classroom S3011 Secretary: Yang Jingjing 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.
- At first, the working efficiency is lower, the done value of Burndown chart is above the ideal value, which is slower than the ideal one.
- In the middle and late, after everybody's running-in, cooperation efficiency is much higher, slowly catch up with the progress
- Update Kanban and Burndown charts every day to see how the team works
- Adhere to the daily meeting, the day's problems and difficulties proposed and resolved, prepare for the next day to do the content
- Scrum Master insists on leading people to study together
- Everyone learning while doing projects, have learned a lot of things, the relationship is much better
- 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.
- 102 Yang Jingjing: Teamwork is not very reasonable division of labor, boys do relatively more, but we also have a lot of power in other aspects, in the code we will continue to work to help the team better development;
- 105 Dong Tingting: Although the team members ability level is not quite, although the writing code ability is not strong, but other aspects of ability can complement;
- 106 Shing: The team process often communicate and discuss with each other to help solve the problem;
- 157 Jongeron: The task division is not clear enough, the timing is not very reasonable, the next sprint hope can be more detailed;
- 343 Xianghui: Other tasks more, spend less time in the team.
- Productivity Analysis : Compare the pre-estimated productivity to the actual productivity, and analyze the cause if the difference is large.
- Our pre-estimated productivity and actual productivity differences are small, and the scheduled time and tasks are implemented within the planned time, and the results are consistent with expectations.
- Improvement : At the end of the day, the Scrum master summarizes the specific recommendations and concludes where the next sprint needs to be improved.
- The Sprint's division should be more detailed and clear;
- Overlap of tasks, two people do similar tasks;
- The distribution of work is uneven, there are few;
3. Recalling the Auxiliary
Good: Practices that you can continue to maintain. 1. Regular exchanges and discussions; 2. Issue in a timely manner; 3. Daily meetings; 4. Helping each other to solve problems;
Could Better: The practice that needs to be changed. The division of 1.sprint should be more detailed, clear; 2. The overlap of tasks, the tasks of two people are similar; 3. Uneven distribution of work, the number of small;
improvements: Specific ideas on how to improve.
1. Specific tasks are assigned in accordance with the workload and can be specific to everyone. 2. Knowledge of the database should be enhanced by learning 4. Recalling the discussion through the voting, we need to improve the most is 1. Assignment of work assignments. And there is 2. We need to spend more time together to write code, so that more exchanges, not only the daily meeting has a problem to come out. 5. Review deadline: 2015.5.25 10 o'clock in the evening team contribution: 102 Yang Jingjing 18105 Dong Tingting 16106 Shing 17157 Jongeron 27343 Xianghui Jay 22 The function we are now doing is mainly registration and login. 1. Merchants and users can register and login, 2. When you enter a password less than 6 will be prompted password length, 3. When you click Register, the user will be detected, and if you have already registered, you will be prompted to exist. 4. The user's account password is not logged into the merchant account number, 5. When the input content is blank when registering, the input is blank, 6. When you enter blank at logon, you will be prompted for login failure, re-enter, 7. When you enter a password incorrectly, you will be prompted for a password error, 8. Our sprint plan also has access to the main interface can modify the user profile, you can exit login back to the login screen function is still in perfect.
app icon:
Welcome Screen (click the app to see the interface) real-computer testing:
Registration, Login interface:
You can select the user and business portal and click on the page that appears after registering:
The Merchant page, if the user name is already in use, will show that the user name is already in use. If the input information is blank, the login failure is displayed .
after entering the Merchant registration page, you also need to fill in the relevant information. When the input is empty, the prompt cannot be empty. when registering a password that is less than 6 digits, the password must not be less than 6 digits.
Real-Machine testing:
Scrum Project 7.0
