Beta Phase Project Summary

Question;

1. What are the improvements in the practice and alpha phases of each member in the beta phase?
2. What lessons did the team draw from those alpha stages during the beta phase?
3. 12 Agile Development Principles, the team did the best and the worst of the list of 2 points.
4. Against the cathedral and the Bazaar (the cathedral and the bazaar), what is your team development model, and where are the strengths/weaknesses?

Answer:

1. What are the improvements in the practice and alpha phases of each member in the beta phase?

Members	How the beta phase has improved in practice and alpha
Huang Zixuan	The beta phase is more familiar with the setup and basic functionality of the interface than the alpha phase.
Wei	The beta phase has a deeper understanding of the database and algorithms than the alpha phase
Cheng Vision	Provides statistical functionality to the team
Huang Weipeng	More familiar with software testing

2. Did the team draw lessons from those alpha stages during the beta phase?

In the alpha phase, the team is not clear about the team's goals, is not careful in team work and team productivity, and leads to development difficulties and inefficiencies in the development process. There is a lack of careful analysis of software requirements. The beta phase, combined with lessons from the alpha phase, analyzes software requirements and clarifies team goals, adding a bit of statistical functionality.

3, 12 Agile Development Principles, the team to do the best and the most difficult to enumerate 2 points.

The best two points:

1, within the team, the most effective and efficient way to convey information is face-to talk

In software development, we first integrate a variety of information and then face-to-head communication, say the software development recommendations.

2, throughout the development of the project, business personnel and developers must work together every day.

The worst two points:

1, the agile process to develop sustainable development speed. Responsible people, developers and users should be able to maintain a long-term, constant development speed.

Agile development requires stable and sustainable development, but in our software development, there are obvious overtime processes.

2. At a certain time, the team will reflect on how to work more effectively, then adjust their behavior accordingly.

In development, the team did not introspect the development work at every time, but at the end of the day.

4. against the cathedral and the Bazaar (the cathedral and the bazaar), what is your team development model, and where are the strengths/weaknesses?In our team development model, we tend to make closed churches in the alpha phase, and then change slowly to the market in the actual development, and we prefer the market model. The advantage is that it is closer to the user's requirements.

Beta Phase Project Summary