My understanding of Agility: the prerequisite for agile implementation

Let's take a look. Who proposed agile? First of all, a group of technical experts, who do not want their talents to be constrained by various constraints and constraints, made a promise. Second, they are a group of people with high character. They can strictly abide by their commitments and do their best to fulfill their commitments. Therefore, agile implementation is essential. That is, the premise of agile implementation: 1. pass through technical skills 2. pass through agile character, meaning to submit value to users in stages. OK. What are the values of users? Can the user clarify? If the user is confused, the developer must make it clear. Next, we need to submit it in stages. There is not enough good architecture design, and how can we do this. Of course, there must be a spirit of continuous reconstruction. Is each person brave enough to reconstruct his/her own Code. Especially those codes that have been proven to be of high quality. These understandings and grasp of requirements and high requirements on the architecture require developers to be sufficient talents. Then let's talk about character. It takes two weeks for most people to complete a task. This is a typical "college students' psychology", which poses a great risk. Quality, and so on. Whether the standards are met depends on the individual's character. Without a noble character, the agile implementation would have to be stopped. Agile is proposed to advocate freedom, oppose control (process), and stimulate developers' maximum creativity and efficiency. Without these two prerequisites, everything will go into a quagmire. Agility is not about organizations, but about individuals. Therefore, the agility initiated by the company organization, or the agility with a large number of process constraints, is not truly agile. Whether or not we can implement agility depends on our developers themselves.