Several questions about Agile Methods

I understand XP and RUP. CMM are two extremes (both of which are good), and experience is how to balance points based on projects, development groups, and other situations in these two extremes,

1. Agile Methods emphasize minimal documentation, and even think that "good code is all the documents you need ". Is that true?

Yes. If a function cannot be described in one sentence, the function is decomposed until it is described in one sentence. At this time, the function name indicates everything. (Of course, it is not possible to use far away, or to write documents. In particular, it is difficult for Chinese people to use function names in simple English)

2. Agile Methods try to reduce the communication between the most extensive users. For example, they want to communicate with other users through "official user" as a bridge. Is that true?

Wrong. The agile method focuses on users most. We hope that dedicated users can follow the development team from the beginning to solve the problem at any time.

3. Agile Methods emphasize desalination processes and tools. Is that true?

Agility is a new method. Of course, the original processes and tools cannot be used, but now pair and refactoring tools are under development and there will be a new set of tools, if you use the old tool in the new method, isn't it ...! @ # $ % ^ &

4. The core of Agile Methods lies in refactoring. We hope that all changes can be solved through refactoring. Is that true?

It's not just refactoring, but refactoring is not just about change. We recommend that you read the refactoring book and then read the design pattern again.