Sleep Monkey--beta Phase project summary

Beta Stage of Postmortem Report

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. 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?

Answers:

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

Each member in the beta phase, in addition to the Android technology itself is more proficient in the idea of our software itself is also more enriched, in the self-realization of the part is often able to provide constructive advice.

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

In the alpha phase, the need for functional analysis is not careful enough to understand the needs of real users, and the function is scattered, the overall effect is not ideal. The beta phase combined with the teachers and classmates to give us suggestions, added a histogram analysis of sleep quality, make our software more scientific, and add the instructions section, solve some students do not know how to use; unify the overall software style, beautify the interface, make the UI more friendly, enhance the user 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 c6> 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, especially after the alpha version of the release, we have come from teachers and students around the valuable advice, so 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.

Sleep Monkey--beta Phase project summary