Beta Phase Project Summary

Questions:

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. in the Agile development Principle , the team did the best and the worst of the list 2 points.

4. Against the cathedral and the Bazaar ( Cathedral and Bazaar ), your team develops a model

What are the advantages / disadvantages of the formula ?

Answers:

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

each member is Beta In addition to being more proficient in the Android technology itself, the idea of our software itself is enriched, and it is often possible to make constructive comments when the ego part is realized.

2. did the team draw lessons from those Alpha stages during the beta phase ?

in the Alpha stage, the function of the demand analysis is not careful enough to understand the real user's needs, and the function is more fragmented, the overall effect is not ideal. the Beta phase combines the advice of teachers and classmates around us , distinguishes the login status, makes our software more scientific, and adds the instruction section to solve some of the students do not know how to use; unify the overall software style, beautify the interface , making the UI more user-friendly and enhancing the experience.

3. in the Agile development Principle , the team has done the best and the worst of the list of 2 points.

The best two points:

(1) always summarize how to improve team efficiency and put into action.

In the Alpha phase, the analysis needs to determine the task of each individual after the team members began to struggle for the day, but each of us is very free of time distribution, so in the end we have done is only ordinary, and possibly flawed original plan. But in the beta phase, we often come up with daily results through discussion, and agreed time together programming, mutual running, not only completed the original plan, many times, we will revise the original plan more beautiful, in line with the actual operation.

(2) in the team, the most effective and efficient way to convey information is to face-to talk.

In the course of teamwork, we find a very interesting phenomenon, when we publish the content in the work group, few people make suggestions, and when we take the content out of face contact, we often can collide with each other sparks. And, of course, face not only brings us the sparkle. In this way, it makes our members more aware of their own responsibilities and, to a certain extent, regulates the atmosphere within the group, which is an important additional factor in the development process.

The worst two points:

(1) The agile process can be developed at a sustainable pace. Responsible people, developers and users should be able to maintain a long-term, constant development speed.

The Beta phase has not been able to develop at a constant rate due to objective reasons, and there have been overtime events. We must admit that some uncertain factors make our speed not constant.

(2) Our top priority is to make our customers happy by delivering valuable software early and consistently.

After our beta release , we got a lot of feedback and a lot of things we did not take into account at the initial design stage, so we got a lesson: delivering more valuable feedback as early as possible to continually strengthen our software. Time Is everything!

4. against the Cathedral and the Bazaar ( Cathedral and Bazaar ), What is your team development model , where is the advantage / disadvantage ?

Our team's development model in the Alpha stage is basically the cathedral mode, but in the actual development process we slowly to the market mode, especially after the Alpha version released, We have received valuable advice from our teachers and classmates, and we have been inspired: we should strengthen communication with users. And based on these recommendations, a substantial adjustment has been made. In general, we think our team is more inclined to market mode.

The benefits of the Bazaar model:

(1) More understanding of what users think, timely adjust the direction of software construction, make finished products more user market demand.

(2) motivate the team members to innovate and participate in the initiative.

The disadvantages of the market model:

(1) too frequent adjustment Sometimes the program is easy to collapse overall, causing tension in the atmosphere within our group.

(2) The non-screened adjustments sometimes make our software somewhat offset.

Beta Phase Project Summary