The "Next Wave" of domestic software industry themes should be: development process, project management (PM) and quality assurance (QA)

In the last wave, we had a tough market. To put it bluntly, we earned money in the name of software, but didn't leave decent software. At that time, everyone held high the "Informatization" flag, showed their respective magical powers, exhausted their connections, and incited them to do software with a three-inch power. They were so embarrassed not to buy it. People who have bought it all know that they have bought a bad thing.

Now it's different, people are all smart, and no one will be as kind of "software" as before. This is called the mature consumer market and the growth of software consumers. Therefore, it is time to take a break from the evil market.

Companies that survive in the last wave of software development must have won survival opportunities for themselves in the market (it is hard to say about product quality ). The next wave has arrived, and some will be eliminated. What are the rules for this elimination? It should be software quality. The improvement of software quality is inseparable from the development process, project management and quality assurance. So I think the "next wave" of the domestic software industry should beDevelopment Process,Project ManagementAndQuality assurance.

 

• About the development process

Software development is an immature industry. Every company has its own practice. Without an authoritative and standard software development process, it can be applied to all companies. However, the development process is the basic facility that standardizes the production process, standardizes management, and improves product quality. In short, it is "rule", and no rule is not a square. If there are no rules, you will not be able to build a program. At present, many companies have begun to focus on developing their own development processes. This is really good!

At present, the most popular development processes are RUP and XP. I personally think that the original version of RUP is better than that of the original version. However, it is not universally applicable to the use of RUP. It is the most effective way to apply the ideas and methods of RUP to your project. It may not be effective to fully follow the RUP, just as it is ridiculous to take "apply all 23 design patterns to the project" as the project goal.

 

• About Project Management

Project management is to apply knowledge, technology, skills and tools to project activities to achieve project objectives.

In the previous software development team, "Project Manager" is almost equivalent to "the most technically qualified person ". The result is that the development team focuses too much on technology and ignores project management. For project success, technology is only a part, not even the most important part. The biggest benefit of a project manager is to act as an integrator (PMI said so). He strives to coordinate various factors to facilitate the development of the project's success. The project manager is the key to the success of the project team and the interface layer of the Management and Development Team. It ensures the management of the development team, at the same time, it improves the efficiency of development management by the management layer (when there is no project manager, the functional manager is basically responsible for the project manager ).

Project managers must first possess systematic project management knowledge and have professional technical experience. At the same time, project management is a very practical thing. I learned a bunch of things but never used them. Therefore, experience in project planning and project control is critical.

 

• About Quality Assurance

QA is the supervision department, and QA is not the test department. No one has any questions about this issue, right? Previously, many companies may have test departments or test groups (if they haven't even dared to say that the software company is a bit too much to say), but few have QA departments. With the process and specification, With the development team that implements these process specifications, who will ensure their true implementation? Is QA. Without QA, the process specifications may be ineffective. The idea is simple: to ensure that appropriate people can produce ideal products through standard processes. If law does not comply with law, law enforcement is lax, and the law does not investigate, it will not be long before the law will be "illegal", and our software development will return to the beginning of this century ...... Hoho ......

This idea is a bit unacceptable for leaders who are accustomed to thinking that "developing software is to find a few people to program. Because quality improvement requires cost, that is, quality cost. Of course, we need to make an "investment/benefit analysis" to see if I can make a decision. Call ...... If the result is that you cannot invest a little quality cost, close the door directly.

 

Call ...... Well, you may not care about the mess mentioned above. What I really want to say is that it is time to focus on software quality. Please do not look at this wave!