Project path-agile development for cainiao

A month has passed, and at the management end, my mind is how to arrange the mess in order so that the team can continuously produce. Although there is basically no need to think about code, I feel a little tired when I participate in three projects at the same time. This is a marathon, either passing through the end to get angry or getting angry.

After about a month of preparation, a formal entrepreneurial project was finalized in February and entered the development stage.

Although the project is not technically difficult and belongs to vertical products, there are still great challenges.

Our advantages:

The offline operation team has been in practice for two years, and has a customer volume of tens of thousands. The leading brother also has a strong market pushing capability.

There are two technical members who are familiar with the business and one designer with an international vision.

Our challenges:

We are a student team. The technology is not strong enough, and external recruitment is unrealistic.

Solution:

I came forward to look for more competent students to participate in, and finally the project members had 7 members; one person design, one person app interface implementation, one person app integration, one person app interaction, one person Web Front-end, one-person Java backend, and I am doing Architecture & project management.

OK. The simple preliminary preparations are here. Next we will go to the topic of this article and follow the path of Agile Development Declaration.

Agile Development Declaration:

Individuals and interactions are far more difficult than process and tool teams. Is agile development suitable for our team that is immediately started from outside? You need to know that the most important thing for agile development is the tacit understanding of the team, the second is the overall personal ability, and the last is the expertise. At this point, there is a mature routine, that is, a few minutes of standing meetings every day. Let's talk about what we did yesterday, what we want to do today, what problems we encounter, and how we can solve them. But we cannot use this routine because we are too free to work (not a company system ). At the beginning, I told you how we work in the data center every afternoon? Other times are free of charge. But only three people said they could do this. The reason is not enough. No problem. Sometimes it is necessary to assemble and come together. In Agile development, team collaboration tools are for communication and interaction. Our technology department has set up a QQ group, which can be released in a timely manner for testing and communication. I have added all other people, and I will send a group of text messages to you if I need to integrate them. Then I used worktile, assign work.
Currently, the main individual interaction points are as follows: Design & App interface implementation; app Integration & App interaction; Web Front-end & JAVA backend; I & everyone; but there is no element of extreme programming.

Software that can work is better than comprehensive documents

We only have simple versions of documents. We use the word table to draw the interface, marking the associated database table.

I only made a simple conceptual architecture diagram through processon.com, and explained each module clearly. The specific design and implementation will be handed over to the relevant persons in charge (of course, it is not lost ~)

Facts have proved that our needs are still being changed during the development process, sometimes subtraction or improvement. Due to limited capabilities, we cannot come up with the best solution in advance.

The software that can work is not necessarily integrated. The modules made by different people at different times are "software that can work". When the software comes out, the thinking points will be clear immediately. Of course, the weekly task delivery is not that easy to implement. The first iteration task I designed cannot be completed. So now, we are in the chaos stage. After the integration work is put, enhance communication to prevent scattered battlefields.

Customer cooperation is better than contract negotiation

We developed it for ourselves, and of course there are customers, because the project is not dominated by our technical team, but by our marketing staff. But even internal personnel cannot work together. They often need to run and we don't want to come up with dormitory. Developers generally do not like meetings. Therefore, I will meet the customer twice a week to discuss the progress and various situations, and may adjust the download work plan when I come back.

Responding to changes is better than following the plan

Although this is a benefit of agile development, who would like to hear the word "change? Who makes the mistake that requires "change?

A complete development is a war, a battle, and then let go again!

Therefore, the response to changes can only appear in my session. Before development, the main systems should be independent. During the first iteration, the content of the second iteration should be determined with the customer. Of course, the customer does not understand the content of the design iteration, so let me arrange the priority. The most uncertain and most likely to change will not be done first. (Generally, it is the most important and simple task to do first, but I will consider it more to see if it is easy to change ).

Conclusion agile development is the first suggestion. The team should sit together and have a whiteboard sticker next to it ...... This is the first small step, and we have not done it yet, but the development progress can still be promoted. Although it is not fast, I do not know it is not agile, but it is still smooth, there are no major bugs. We plan to complete the initial work of the project in September 15 and release it in September 25 ......

Project path-agile development for cainiao