CMM is outdated, and agility is the king

First of all,AgilityIt has nothing to do with documentation. I am just a waste of the CMM documents.

Look at those documents and look at those processes. Think about the great software works, which was developed with CMM?

AsTestAre you uncomfortable with CMM process management for engineers and programmers? Do you like to write a bunch of documents? Do you like to read the pile of documents? Do you like your boss's fingers all day without actually helping? Do you like to see that the demand is constantly changing but the plan remains unchanged? The result is to compress the test time or release delays? Of course, the answer is no. Nobody liked it.

Software DevelopmentIs a process of creation. Engineers are not machines. A development model that conforms to human nature is a good development model.

Core issues of Software Development: communication barriers, demand changes, and product quality. It is not well solved in CMM mode. Agility provides a new way of thinking. The core idea of agility is people-oriented and continuous improvement.

The reply shoes seem to be very interested in document issues, so I will talk about agile attitudes towards documents.
First, agility is not without documentation. Agility only ignores unnecessary documents.
Secondly, all the documents required for a commercial software release are available in Agile development. For example, release note and help.

The role of a document is to communicate, communicate, and transmit information. However, the text itself is not a perfect carrier. Language can always express thoughts more clearly than words. Therefore, in Agile development, such items as test plans, solutions, task assignment, and briefing can be omitted. I can spend three minutes explaining what I want to do. Why do I need ten minutes to write and the recipient needs ten minutes to read it. This is not a waste of 17 minutes.

When you join a new team, do you want to see a lot of product instructions, or do you like to guide you with personal hands? I think most people like the latter.

All knowledge in an agile team is shared. So there is no need to worry at all, because the lack of a member leads to a knowledge fault. Similarly, documents generated due to such concerns can be omitted. By the way, although I don't know why, the agile team has a very low turnover rate. The testers in our company did not leave the company for several years after agile implementation.

CMM is outdated, and agility is the king