Internet product R & D Management-sop in software R & D

We all know what is going on in the traditional industry. In order to reduce labor costs, enterprises have to do everything they can to speed up product factory time and productivity, in order to achieve this goal, many enterprises use a mechanical flow operation, and the SOP adopted in this flow operation is a standard operation, which standardizes and unifies the operations of employees in each link, improve production efficiency through simple and repetitive operation standards.

In fact, the software industry can also adopt this method to improve the quality and production efficiency of software. As we all know, in the software quality management system, there are indicators such as CMM, cmme, and ISO, these identifiers are used to improve the capabilities of software enterprises and assess the maturity of software. These processes are heavy-duty. Many enterprises have been to these levels to take tickets, in the end, you can imagine what it is like.
Let's talk about the SOP in our R & D process. Let's first look at why we should adopt SOP. In the process of team software development, there are several important processes that must be followed, no matter what development method you adopt, traditional or agile.
1. Software Requirement Process
The process of software requirements can also be standardized. Although the acquisition layers of software requirements can be diversified, the entire process of software requirements is consistent, some details of the work can be different or can be omitted but the requirements of the product, user requirements documentation and software requirements documentation is an indispensable part.
All projects and products come from the demand. if the demand is wrong, you can imagine that the following work is all wrong, no matter what kind of software development method you have, in addition, demand changes also need to be managed. Project or product upgrade and modification are all lazy in the Change document. If no change is recorded, the product will be out of touch. The software requirement document is actually an SOP manual, which tells relevant developers how to write the software to meet the needs of projects and software. This document has nothing to do with people, I am afraid that another person will also share the same document description. This is a standardized document that cannot contain multiple forms of Requirement documents, so that it does not use unified identification requirements and reading.
2. Configuration Management for software development
When developing teams, you will often encounter lazy work. When you group your work, you must consider lazy work, how to solve the lazy work in the software development process is also mentioned in CMM, that is, software configuration. You can configure a unified development and management environment, such as using the software version controller VSS and SVN, unified Bug Management and test environment all belong to the software configuration layer. The purpose of unified configuration is to solve the need for coordination and lazy work. It is like a unified production line for every product in a pipeline operation.
3. Architecture Design of Software Systems
The architecture of a software system must be unified for a project or product. Of course, there are also some large applications. For example, an Internet product may have applications of multiple different system architectures or platforms, however, the software architecture in the same application or system must be unified.
The unified architecture is conducive to system expansion and management. The unified architecture is conducive to improving the production efficiency of the R & D team. Many applications can be encapsulated in the specific implementation of the system architecture layer, it is a unified platform for development. Under a unified platform, it facilitates development management and system expansion and external application integration.
4. Release of software products.
The unification of software product release is conducive to the stability of product release. The establishment of a standard and unified release process can improve the efficiency of product release and reduce errors during software product release or upgrade, especially for applications like Internet products, the lazy nature of its functional modules will be relatively large. Once something goes wrong, related applications may encounter errors.

Although the software industry does not have the extensive and mature SOP application of traditional enterprises, it does not need to learn from the practices of traditional enterprises. For Internet products, there is no need for quality assurance of heavy processes such as cmme, more agility is needed to meet the needs of market changes and user needs. However, SOP can be implemented for these key processes to reduce software risks and improve software production efficiency.

For more software R & D blog posts, refer to this blog.