Footprint: 2nd days of private ticket Diary

I have made a private ticket with several friends and encountered some problems at the beginning. So I want to sort out my ideas and accumulate some experience for future cooperation.

Currently, the project lacks coordinators. The relationship between a few people is quite special. Four people, I and A, B, and C. I am familiar with A, A and B, and B and A and C. I expect B to assume PM's responsibility, but it has not been confirmed by everyone and time. The Coordination person is responsible for the division of labor. Everyone develops independently based on their own modules and discusses the issues together. This is the collaboration method I have come up. In the next few days, you will also search for other collaboration methods. No matter which collaboration method you choose, the goal is to improve the efficiency of the team, but the focus is to make everyone accept this method from the heart.

Communication
Our communication methods are completed through QQ group and project forum. At present, some initial draft documents are shared in the QQ group, but these documents may be constantly modified. If you can add the documents to version control, it may be better. For example, Google Docs provides collaborative editing and version record functions.
In addition, you may not be able to share the same time when you work in different places. Therefore, the forum will be more effective when you discuss issues that need to be considered and discussed for a long time. Google's online forum is actually a forum-covered email list, which allows you to get new information in a timely manner through email.

In the past two days, A is responsible for the outline design; B is mainly responsible for contacting the customer to meet the requirements; C is responsible for tackling some difficulties. I have done some messy work over the past two days, such as choosing the source code management service, establishing a project discussion group, preparing some materials for you, understanding your needs, and initially analyzing a large module ......, The most important task is to get familiar with everyone as soon as possible, so it took a lot of time to discuss with everyone. However, the effect of the discussion is not good enough, mainly because the time for several people to work is inconsistent, and the use of the project forum has not really started.

Your own Positioning
WriteArticleThere is no clear positioning yet. from the work of the past two days, I have already participated in various roles and have no clear key points. From the original intention, I don't expect to earn money from this list, but I just want to find something meaningful to do. During the six-year project ice-age period, my hands itch and I don't want to waste myself. I am also worried that the lack of new project experience will be detrimental to future job hunting. In addition, we hope to have more web development experience and take a long-term development path. In addition to these two points, the experience accumulated by loose cooperative development will also benefit the future.

The project development cycle is short, and there is uncertainty in the available time of everyone. Therefore, I personally prefer to hurry up from the very beginning, but it is difficult to look optimistic about the current status of everyone.

P.s. subversion has not been used yet, so it is also a concern. I am not familiar with myself, so there is still a little pressure to promote in the team. The promotion of new tools in the team must be a step-by-step process, so I have been secretly reminding myself not to worry about it.