What is a standard, normative development process

After the training of several companies, I also summed up the general company’s development process, as well as the development process that I think is more standard. The standard development process enables us to ensure the quality of project delivery.

• A simple feasibility review of the product (with the participation of the product and the project leader)

• For demand analysis, the product will communicate with the customer, refine the demand points, analyze how to achieve more reasonable, and make simple interaction with the customer in the form of prototype drawings to confirm whether the demand is met.

• Requirements review (all participants of the project, product presentation, development, testing, designer questions, to determine whether it can be implemented, as early as possible to nip problems in the cradle)

• The detailed design

  • Interactive prototyping (Designer prototyping)
  • Front drawing page
  • Backend design database

• Design review

• Code, tune, self test

• Code Review

• To measure

• Product acceptance

• Change the Bug

• Regression testing

• Gray released

• Official release (Going Live)

Conclusion:

Personally, I feel that requirements review is the most important part. Often, we can get twice the result with half the effort if we can clarify the requirements as soon as possible. Moreover, we can put forward our own ideas and pool our ideas to make the best products. After all, everyone is a product manager, lol.