Oschina: Q: How does a small workshop implement so-called software engineering?

I used to give oschina an award-winning Q & A related to "software engineering practice" (the prize was for the questioner, haha). Now, many questions are still readable, therefore, you can organize the text to enjoy the crowd.

Original posted here: http://www.oschina.net/question/12_78459

The question in this article: How does a small workshop implement the so-called software engineering?

A:

It is not the reason for not doing software engineering, for example, a small company or a demand that changes too frequently. Often, when we talk about engineering, it is "very big", "very academic", or it seems like we are talking about all kinds of "agile", but it becomes a rule in practice. Everyone needs to know that most of the "Projects" mentioned in practice are engineering methods.

It is both a method and a matter of action and a person. No matter what kind of project method is like, what kind of beautiful words are like, what kind of data is shown to you, and what kind of data falls into the category of your "specific project", it must be adjusted. Specifically, we should first look at people, first train the overall consistency of engineering understanding, and then plan things to form a more concise and applicable process method, as well as a verification mechanism. With these two points as the foundation, the project can go from 0 to 1 and go through the stage of "no project.

A team always needs to grow from small to large. If there is no engineering quality in small scale, it is also very painful to make up for it on a large scale. Similarly, individual developers do not need to be professional. It is also very painful to change the company to the team. Therefore, on this issue, I think personal training is as important as team training. I know under what circumstances I want to do, what I should do, and how much I should do, there is a basic and engineering understanding of some problems.ProgramThe proper quality of members. If your team cannot reach this point, train them. I suggest that you do training by yourself. This is both a clear understanding of yourself and a process of understanding everyone.

Finally, let's talk about the details, that is, how to do it. In this regard, I have made public materials a long time ago. Please visit the following address:

Http://126.am/uP5wo0

Download Chapter2, which has two parts. This practical process involves a team of two people, a complete project process, and the whole process of engineering. I am not saying that this example is very good and perfect. I only suggest that you pay attention to this practice: we should come here for reasons (that is, for projects and teams) to "customize" Our engineering methods.