Alpha version display
1. Profiles and personal blog addresses of team members, and the address of the team's source code repository.
2. Ranking of contributions of team members (from largest to smallest, no tie)
3. A summary of the blog link of the team's 8-day Alpha sprint stand-up meeting (collection post)
4. The team can make an MVP (Minimum Viable Product) version, as long as the core functions (such as user registration, password retrieval and other non-core functions can be omitted). It can also allow teams to demonstrate rapid prototyping solutions to potential users for feedback.
5. If we want to do software engineering, we must have a little bit of engineering:
Where are the goals of the team project, expected typical users, expected functional description, expected number of users?
How does the team's product meet the needs of users?
How does the team's product meet the needs of users?
What goals has the team accomplished during the Alpha phase?
In terms of main functions, the main purpose of our team’s mini-programs is word learning. As shown in the mini-program learning interface, we are learning English words for students preparing for CET4/6, GRE, TOFEL and postgraduate exams. It is convenient to use your spare time to learn words at any time when you don't have related books with you.
In terms of auxiliary functions, although our punch-in function and statistical analysis function have been launched, they are still being gradually improved.
In terms of teamwork, each member of our team has gained a lot in the Alpha stage through the supervision of teachers and teaching assistants, and they are becoming more and more serious about teamwork.How do team members work together? What are the lessons learned?
Qi Zewen and Xu Lulin: responsible for the statistical analysis module: analysis of forgetting curve/total number of words learned/wrong word statistics/mastered word statistics, as well as the daily punch-in function and the design of the personal interface.
Lessons learned: For the statistical analysis module and the punch-in module, it can be said that I have never been exposed to the methods of these two modules at first, so I felt that I had no idea how to start. The error doesn't know how it ends. No way, I can only keep checking the similar source code, and learn from it, and I stumbled to make a general idea. In the process, the data was once covered because of the unfamiliarity with GIT, but I found it later.
Guo Qirong and Wu Ling: Responsible for the review module: example sentence review/note review/wrong word review/strengthening training, as well as the design of the home page interface.
Lessons learned: The cost of communication is relatively high. Due to the relatively short time of the stand-up meeting, it is necessary to communicate with members in private and ask for opinions and suggestions. On the second day of SCRUM, I preliminarily completed the note review module and completed a small part of the code in the review part. Every day I am making progress and I am getting more familiar with the development platform and language.
Zeng Yijia and Wang Xing: Responsible for the learning module: words and their definitions/words Pronunciation/example learning/adding notes, as well as server construction and learning interface design.
Lessons learned: It is troublesome to find a thesaurus, and I can't find a suitable interface. Later, I downloaded the txt file and used the database to store it. During the deployment of the development environment, an error occurred in the development environment switching of Tencent Cloud, and the service was successfully started after logging in to Tencent Cloud and modifying it. The HTML language is quite different from the WXML language, and I have never been in contact with Android development before, which is really a headache. When the program interface obtains data, the domain name has been wrong, and the data cannot be obtained. Later, the url is changed and the json data is obtained again.How does the team manage the project?
First of all, our team has a goal, first do the main functions of the WeChat applet (memorizing words and learning words according to their own needs), and then develop its auxiliary functions (check-in function, statistical analysis function). In order to achieve the goal, the time is fixed, within two weeks, which means that we need to reasonably arrange the task volume of each person in the team within these two weeks. So before the project started, we first did a resource integration, everyone downloaded the development tool platform of the WeChat applet, and learned the relevant knowledge in the component part of the WeChat applet. In addition, we also manage the quality and progress. Quality is the functionality of completing tasks today (such as whether they can be run, whether debugging is successful, etc.) Allocate personnel to facilitate the smooth running of the entire project.
How does the team balance time/quality/resources to meet deadlines?
In fact, in the two weeks of the Alpha stage, everyone in the team has a lot of things crowded together, so sometimes a day is a little less and a day is a little more, but everyone spends time on team projects every day.
The quality is mainly based on the modules assigned by each member. If there is a bug in the corresponding module, send the problem to the member responsible for the module and let the member issue an announcement to solve the bug, so that the speed of solving the problem will be much faster. .
In terms of resources, when we are in Baidu, if we find similar code with other members responsible for the module, we will also publish the resources on the group to share with everyone.