Internet product iteration is everywhere

Iteration is a process in numerical analysis by looking for a series of approximate solutions from an initial estimate (generally by equations or equations). The methods used to achieve this process are collectively referred to as iteration methods. .
As Program Clerk, I think everyone is familiar with the concept of RUP or has also implemented it in projects or products.
What I can feel in the existing product cluster architecture work is that iteration is everywhere.
Whether it is the concept of a product or the design, architecture, and development of a product.
The entire lifecycle of any new function release requires iteration.
Compared with traditional software products, interconnection products have a short function life cycle and require constant innovation and exploration, in addition, it is possible to verify the product success or failure in the Internet market only when the product is released at the fastest speed. Traditional software services target traditional enterprises, organizations, and industry standard companies. Because organizations, regardless of their organizational structure, business specifications, and business models, are slower than Internet-based products. This does not mean that traditional software does not require iteration, however, there will be great differences in the time of iteration. The Internet is more represented in the word "fast", from product concepts to prototypes, design, cutting, and development reality, the entire process, such as testing and launch, needs to be fast. Sometimes this cycle only takes one week, especially for online games.
The same is true for my products. The Operations Department collects user requirements and submits them to the product department, the product department needs to submit the final product new function requirements generated after a quick PK to the product diagram of the design department. This time will generally not exceed one week. These two processes also require a small iteration. After the design is finished, HTML will be cut out by the page engineer and then sent to the developer.
Similarly, there will be iterations between designers and developers, and adjustments will be made to the difficulty of implementation and the "value orientation" of products. Sometimes the design is good, however, from the overall perspective of the product, it may not be necessary, as the performance and user experience of the product sometimes seem to be in conflict. After the programmer implements the function, he or she will iterate with the test team.
In the whole process, it seems that there is nothing about the architecture! Otherwise, the architecture needs to be introduced from the proposal of product requirements throughout the cycle. It would be sad to put the architecture into the implementation stage, architects do not know who to do it? I don't know what it will look like, I don't know what it will look like in the future, let alone what extensions it will look like. But in fact many companies will do this.
Architects need to understand everything like general practitioners, more importantly, each "medication" should be considered from all aspects, and then make a relatively reliable choice without harming the root.
Therefore, the ability of an architect is not awkward. It is necessary to sharpen the experience, and it is still barefoot on the road.
Ten skills required by architects