postmortem report beta stage
1. What are the improvements in the practice of each member of the alpha and beta phases stage?
| member |
Beta stage of practice and alpha phase What are the improvements |
| Zhou Bo |
beta stage than the alpha stage is more familiar with the technologies, more efficient, and timely communication and user summed up the problem. |
| Qu Xiangjia |
beta stage than the alpha stage understanding of the structure and algorithm of the more profound, can deal with unexpected problems. |
| Zhang Qiuliang |
A certain increase of the cloud server and related technologies. |
2. The team learned the lessons of those alpha phase in the beta stage?
In the alpha stage, the demand for functional analysis not careful enough, not well understand the real needs of users. Beta phase combined with the needs of students around, adding the user's manual functions, but also for page layout has been further optimized.
Principles of agile development 3.12, the team doing the best and worst of each enumeration 2:00.
The best two points:
(1) meet the needs of students is an important measure of software.
We very much agree with this measure and well applied this standard in the actual project implementation. Since the collection of the needs of many students in the beta stage, it is also a page for mobile phones and functions were further optimized.
(2) blog sprint and team meetings to promote the project process
We started some time of their own learning, learning progress is uneven, and later at the request of the teacher Jianmin, to conduct daily summary of progress, and team meetings, so that we can timely communication and exchange, to further promote the project from to a crucial role, but face to face, better and timely response cases, this method of project development of great help.
The worst two points:
(1) Agile processes put sustainable development speed. Sponsors, developers, and users should be able to maintain a long-term, constant development speed.
Beta phase due to objective reasons could not be done to develop a constant speed, there have been overtime phenomenon.
(2) Our highest priority is to make the customer through early and continuous delivery of valuable software satisfaction
Face the problem of feedback after the beta release installed inconvenient, we got a lesson: It should be as soon as possible to allow customers to use our software to understand where they are most in need of improvement. Software engineering is not just writing code, which also involves a lot of people doing things we need to understand the truth.
4. Control The Cathedral and the Bazaar (Cathedral and the Bazaar), your team is what kind of development model, the advantages / disadvantages of where?
Our team development model in the alpha phase are more likely to make an initial closure of the church, and then slowly transition to a market way in the actual development process, we are more inclined to believe bazaar mode.
With this model, we have the advantage to be more close to the user's needs, always listen to the user's ideas, including aspects of function points and the overall software experience and so on.
The disadvantage is that we do not have much time to think about the project skeleton, do the following two points mentioned in "The Cathedral and the Bazaar" The article is not good enough:
a) a robust design is more important than sophisticated. In other words, the structure is the first function is secondary.
b) maintaining the simplicity of the project. Designed to achieve the perfect time to add things not impossible, but things can not be further reduced.
In future projects, or as soon as possible to consider a number of issues regarding the structure, agile response to changes in demand.