I listened to a class on agile development for a day today and found it very interesting. I have paid attention to agile before, and I think pair programming is very good. But there is a problem, that is, even in an era without the concept of agile development, there will be small version iterations.
A few years ago, our design and development activities were a bit like waterfall, that is, planning -> requirements -> design -> development -> testing in this order, but we also did not plan one at a time according to the characteristics of the project or product Very large version, but arrange features in different small versions, in different versions, review the new changes in requirements, new requirements of customers. It doesn't look that much different from agile either.
So, agile is not a new concept that fell from the sky, but evolved from the good practices of the original waterfall model, and it is not incompatible with the waterfall process. In my understanding, compared to the original, there are not many new things.
I hate that the field of software engineering is always filled with a bunch of new terms, such as agile, Scrum, sprint, DDD, TDD, FDD. It sounds confusing. In fact, if you ask carefully, it turns out to be a word. What is behind it? Neither (extremely speaking, it's not that there is nothing, it's the original things or those people behind it. It's just a haircut), and he smiled.
Concepts and nouns are the most intimidating. They are really good for book writers and some so-called innovators; but for some people who do things, I think they should be pragmatic and don't always talk about bells and whistles. .