About the choice of software team

March 19, 2015

Today, we have a panel discussion, mainly to discuss which type of group organization is suitable for the development of Appendix A "Chocolate Lovers Anonymous" product.

The group's five "golden Flowers" have been hotly debated for the type of software group to be developed by our group, and the group's comments have focused on the two types of software groups in the Group of democracies and agile processes.

Members of the Select Democracy group say that the basic concept of a democracy group is that it is not my programming, that programmers can democratically write code that they like, and that the Group of Democracies works for a common cause, without individual leadership, with a focus on group characteristics and mutual respect, so that productivity can be high, The quality of the code is also very high.

The team member of the Agile Process Group indicated that this approach could improve the group ownership of the code and was not a positive feature of my group. At the same time, because programmers do not test their own code, it is better to find out the error of the program, if a team member has some urgent things to leave will not cause serious loss.

The members of both sides expressed their opinions, and ultimately our group decided on the way to use the Democratic group. The reasons for this are as follows: Members of the pro-democracy group said they didn't really want to be tested by others, and that their code wanted to be able to test themselves, and because everyone had a different style of code, they wanted to be able to write the parts they liked and test their code. The members of the other party listened to their views, and eventually the panellists unified their views and decided on the method of using the Democratic group.

There are also a few reasons why you didn't choose another type of software group at the beginning. Both types of groups are not very practical for the traditional master programmer group and the modified master Programmer's team, and there is no master programmer inside our team. For the modern grading programming group, we do not have the role of group manager or group leader. Synchronization-The stability team needs a lot of developers for very large projects, and each developer needs to have a tester, which is obviously not a realistic situation. For the open source group, it is clear that we do not have the intention to open source.

These are some of the records of our panel discussion, and we finally decided unanimously that our group would be developed in a Democratic group.

About the choice of software team