The following is some of my feelings after I read the article of "Programmer" magazine on the "Programmer" magazine about the agile method. Because it is "first knowledge", there may be a mistake in the ideological grasp and understanding. Please give me your point.
Agile Alliance was founded in February 2001, its values are: Individials and interactions over processes and tools Working software over comprehensive documentation Custonmer collaboration over contract negotiation Responding to change over following a plan
For the content elaborated by Agile, I agree, and I think that the specific methodology is thrown, and these insights should be very easy to accept and understand. This is especially true in such a realistic environment in this day. Practice has developed to a certain stage, and new theories and ideas naturally become.
With my understanding, if you want to correct the previous mistake, we need to truly admit the following facts, this is the primary, and it is also reflected in these four values: the importance of recognition; the existence of changes;
On the one hand, in a concrete software development scenario, there are a lot of people, and different people play different roles and play their respective functions. Programmers, designers, analysts, managers, and customers, they collect one or more tasks by communicating and communicating with each other.
On the other hand, there is no time in all. The changes in demand, changes in design, changes in technical means, and changes in people, inserting each other, such variables, greatly affecting software development.
Acknowledging that the above two are the beginning of everything.
I think the value of Agile is the inevitable conclusion after the above two points, or the core of its values is the above two points.
Software and architecture are indeed different, which also destined the defect of the Monumental method (but not completely wrong). Prayer structure, lengthy documents, cumbersome processes, long cycles, which have become a failure or inefficient root.
People have their own specialties. As an emotional animal, it has the ability to withstand labor intensity, as well as the deviation between interpretation and expression of each other, and people often underestimate emotions, using scalability, and neglect the deviation. This is the background of the first value.
The changes in the documentation and the change of the software must be synchronized, otherwise some of the significance is lost. In addition, due to human factors, the fuzzy and secondary meaning of document expressions are difficult to avoid. Documentation despite its absolute necessity, it is an auxiliary tool. The software itself is the primary, it is the real intention of the code to reflect the designer and realist, and the final run is also the code itself. This is the reason for the presence of the second values.
Or the result of the common role of the two factors due to people and changes, resulting in the emergence of third values. Maintain dynamics and open attitude, bringing customers to Team, rather than rejection, avoiding and perfunctory, which is very dangerous.
As mentioned earlier, because too much variables, the meaning of the fourth value is self-evident.
In addition, if the theory is just theory, it is a pity that it is very important to practice and return to practice. As far as China's current situation is concerned, I think that Agile's thoughts seem to be very suitable and is more suitable for those small software development groups.
