Final review report

Project name: About to run

Group Name: nice!

Group leader: Liquan

member: Liu Fangfang in Miao Han Yuanyuan Hong Lijun

Final Review Conference

Date: 2016.12.2

Conference Content

Vision and Objectives

1. What are the expected goals when the final phase is released, and what are the specific levels of implementation that are expected to be implemented?

Final phase of the user's proposed bug modified to further improve the product. Finally completed the user put forward the number of words too much to squeeze out and not completely quit the problem, but also to run the app's interface to beautify the user experience feedback is good.

Plan

1. Have you finished your original work? If there's anything unfinished, why?

Not fully finished, due to time reasons, want to add map positioning on the app, due to lack of time is not integrated into the product.

2. Did you find that you did something that didn't seem necessary or valuable afterwards?

No, the finished things are assigned according to the plan, because did not touch the Android, so everything is done by their own harvest is very valuable, and there is no time to do a useless.

4. Is the whole process of the project carried out according to the plan?

Yes, every function is implemented as planned.

Resources

1. Do we have enough resources to complete the tasks?

In the test, because there are few users around the Android phone, in order to achieve a good user experience, in the search for users to spend a lot of time and energy. Everyone coding ability is general, so in the code development part of the resources are insufficient.

Change Management

1. Every relevant employee is informed of the change in time?

In the final stage of the increase in enthusiasm, the product of all kinds of progress are actively follow-up, and the team leader is responsible for timely notice to everyone.

2. What methods have we adopted to determine the "delayed" and "must be" functions?

Open the Group meeting, we discuss the decision.

3. Can a contingency plan be developed for possible changes?

Yes, for unnecessary to do things can be done in time to discard.

Design/implementation

1, when the design work, by whom to complete? Is it the right time for the right person?

The design work shall be decided by the leader.

2, the design work has encountered ambiguous situation, how to solve the team?

Will encounter, want to add some features to become the highlight of the product, but the implementation of the time is not enough, so the meeting decided to lose.

3, what function produces the most bugs, why?

Small partner dialog, because the dialog box is not designed to cause a bug to occur.

Test/Release

1. Does the team have a test plan? Why not?

There are, in each stage, due to the continuous improvement and improvement of the product to be tested, to further modify it.

2. What unexpected problems were found during the release process?

The product release is generally smooth, but the display of the product on the projector is poor.

each member is Final What is the stage improvement ? ?

member	Final What is the stage improvement ?
Leader	Find yourself in the beta phase of the technology is less than and quickly modified the run-around bug.
Liu Fangfang	Understand to always cooperate to do product testing, in the final product to improve the group will actively express their views.
Yu Yu	Put forward the interface beautification valuable advice, and actively look for material, is the product more beautiful, friendly.
Hong Lijun	The task of the team leader to assign the access information can be completed seriously.
Han Yuanyuan	Actively implement map functions that may be expanded

The team drew on those Beta stages of lessons learned ?

In the beta phase of user feedback is not good, in the implementation of the lack of functionality, in the product release is not ready enough. Improved functionality in the final phase, and was prepared before the product was released.

Final review report