Secret-field team sprint Beta blog record

GitHub address a group project: https://github.com/ShangXuecheng-git/2019software

A, Scrum Meeting

1, the tenth week meeting

2, Week 11 Minutes

Second, the test report

Beta phase of testing report

Third, we are pleased difficulties Difficulties & places

(Tenth week)

We encountered difficulties:

1. First, each member of the group must learn as responsible for the project, a lot of things are the first contact, such as grammar, asynchronous programming ideas, as well as the use of javascript on GitHub, we have before no contact with how to use Git Bash upload their own code and synchronize the local code, publishing issues on GitHub

2, we have some differences on the front-end interface design, everyone has their own opinion, it is difficult to reach a consensus

3, the project design is not detailed enough in advance, leading to repeatedly adjust the structure of the project, greatly reducing the efficiency of the development

We are pleased place:

1, although we are busy, but we can actively carry out their tasks

2, after entering the Beta stage of the project, we have greater clout. Remember the beginning of the beginning of the Alpha stage, we are very confused and do not know how we should be division of labor, whether it can achieve the desired objectives. But as we become more aware of the development of the project, we are increasingly confident, I feel we are confident this project will help us to do better and better

3, we have learned to allocate published on GitHub issues to assist project work, no longer as Alpha stage when there is no unified management tasks. After the introduction of the use of the issues, we have developed more efficient.

(Week 11)

Difficulties encountered difficulties:

1, last week we developed members to prepare a lot of new features, but because of asynchronous programming and do not understand the logic of chaos, resulting in a lot of BUG

2, we gradually discovered that some pages are too complex logic, may now be better "component-based" programming can solve this problem, but would like to go to the trouble to re-move the entire directory structure of the project is very difficult, so we decided to follow the original plan to continue to prepare

We are pleased place:

1, although the software produces a lot of BUG, ​​but with the gradual improvement of function, our software also tends to be more of a complete product, which makes us feel very pleased

2, we applied to issues and Git Bash increasingly handy, let us greatly improve development efficiency

Fourth, the working principle soft learned \ method

1, in the design process, taking into account the large number of target audience, not easy to statistics, the team decided to narrow the scope of a user, the first small-scale evaluation of curriculum design and promotion, the overall functional, and then expand its scope.

2, and taking into account the practical problems that may be encountered after we make the appropriate changes to the function point program implementation, work as a functional point of weakening.

3, learning to use software blade, based on the original interface design, a certain amount of improvement and expansion.

Guess you like

Origin www.cnblogs.com/secret-field/p/12008059.html