Software process and project management (fifth Zhou)

A brief talk on the problems of agile development process in our team

　At first, our team chose Agile development, is that our project is not particularly large and complex, our classmates communicate with each other to understand more, do not want to write a document occupy too much time, and finally feel it is a new type of software development method, want to try, and finally chose Agile development as our team's software development method. But two weeks down, I found that perhaps because of some negligence in my duties, so that people did not enter the state of agile development. The following is a summary of our reflection:

First, agile development emphasizes that individuals and interactions outweigh processes and tools, and that the most efficient and effective way to communicate in a development team is to talk face-to-head. At first, I think we are all classmates, usually have communication, every day class will meet, certainly without face to talk. But the actual situation is not so, the class when everyone sitting is very scattered, usually even if the meeting chat and seldom talk to the ongoing project. I said there are problems in the group to discuss, and very few people to respond, the result, the end of our project and not too much communication, but all just put their ideas into the corresponding documents assigned, although the writing of the document is the completion of the knot, but it is only two or three people exchange. My plan is to try to find time to invite you to open a meeting or something, if you do not want to walk, you can group voice resolution, so that everyone in advance to think of what the problem needs to be solved, and then the collective discussion to solve, so that everyone really into this big team, and not like a plate a blow scattered sand.

Secondly, agile development refers to overconfidence is a programming occupational disease, feedback is its prescription, every time, the team should summarize how to be more efficient, and then adjust their behavior accordingly. I feel that our team has not formed a good timely feedback of the atmosphere, each of the following groups alone silently do their own modules, I am not very clear about their progress to which step, it may be because the early stage is mainly learning and design, coding work progress is relatively slow, so there is not too much to feedback content. My idea is to set up a feedback mechanism, set a time each week for each group to send a representative to me for progress reporting and a phase summary, and then adjust the subsequent plan accordingly, so that all teams of a team can work together, will not open too much time gap, resulting in the integration of the final project postponed.

Finally, agile development advocates simplicity and the art of minimizing the amount of work is critical. We have also taken this issue into account in the design of the first product, and we have not designed some of the features that need to be implemented in the second edition that we do not need at the moment. Light, the model as simple as possible, it is also more convenient for future improvement and improvement.

I believe that as the project continues in-depth, as well as continuous exploration and learning, I will gradually understand the true meaning of agile development, and lead everyone gradually on the right track, feel the style and characteristics of agile development.

Software process and project management (fifth Zhou)