Relationship between implementation of secondary development and customer satisfaction

Some time ago, together with the product department, we communicated all the secondary development requirements of the progress system and discussed the value of each requirement, I have been thinking about the relationship between secondary development and customer satisfaction. I will review the secondary development scenarios in my own projects. From the perspective of secondary development sources, there are the following situations:

1. secondary development resulting from contractual agreements: such requirements are difficult to avoid during implementation. For example, when SS and a sign a contract, some project scopes are agreed through the appendix of the Contract, some scopes cannot be clearly defined in the sales phase, and the implementation phase is difficult to control, typical examples include ss contract templates, a real estate and construction company management.

2. secondary Development due to the differences between the customer's actual business and standard system implementation methods: during the implementation process, there are often differences between the customer's actual business processing methods and the system, this may make it difficult for the business to be applied in the system or reduce the business processing efficiency. For example, the material procurement management of project a is divided into many categories, which is more complex than the standard system, project B's output value and payment management are simpler than standard systems.

3. some special services of the customer require secondary development of the system during the implementation process: for example, the SS project adds many control points not in the original system in the cost management process, project A has raised some requirements based on its special management methods. Currently, such requirements can be completely avoided.

From the perspective of demand sources, how can we reduce these secondary development?

The first type of requirement: the company has started the contract review system. Although it can circumvent the requirements agreed in most contracts, it is difficult to completely eliminate the competition. in the implementation stage, it can only pass the Scheme Review, it is implemented in the simplest way by introducing expert resources to reduce the difficulty of secondary development.

The second and third types of requirements: depending on whether the application module is core or not, such requirements can be divided into four categories, with four quadrants. As follows:

 

 

 

The requirements in the first quadrant can be flexibly implemented. The requirements in the second quadrant need to be reviewed and implemented at a low cost. The requirements in the two quadrant can improve the customer's application viscosity, increase the effect of system applications (of course, it is the best way to directly avoid development through high-level intervention). The requirements of the third quadrant are generally raised by the operation layer, by using work und, the operation layer's satisfaction can be improved on a certain program, and the fourth quadrant requirement can be euphemistically rejected.

No matter which quadrant is required, if the company wants to develop a product that is under severe control of secondary development, it must follow two conditions:

1. approved;

2. The total amount of development is controlled by the project's secondary development volume.

 

In addition, we often encounter a type of secondary development requirement. The secondary development on Project A should also be carried out in Project B. For such requirements, it is necessary to consider whether they can be added to the standard system during product upgrade. Even if they cannot be added to the standard system, they should also consider whether they can be quickly implemented during development to avoid repeated work.

Dealing with secondary development should be a small part of the work, but it has a great impact on costs. The company director proposed at the semi-annual summary meeting to "focus on high-level requirements, "improving delivery efficiency" is the fundamental method to solve the problem of secondary development. It also requires a high degree of professionalism for the implementers. In the future implementation process, it is difficult to avoid secondary development, the above is just some of my thoughts on secondary development.