Adaptive software development-from a leader to a leader <3 boom on the verge of chaos>

<Boom at the edge of chaos>
---------

The book uses the term "Chaos". I think it is a bit confusing, so it is changed to "Chaos ".

In today's software development, the Capability Maturity Model (CMM) developed by the Software Engineering Association is hailed as the Holy Grail and is widely used in today's world, the software development process is refined into five levels. The higher the level, the more detailed the process. This is to pursue a stable and controllable effect. And also achieved a rapid development result.

However, CMM, ISO9000, and BRP, which are described as "milestones" in the book, can only survive under a stable condition, that is, the requirement will not change during the development process. If you are in a complex and changing environment, such as the customer is not clear about the demand details, the external environment is not sure, this method will be difficult to survive. In addition, it is difficult for a team or company engaged in this model to enter another field and engage in another completely new software development.

What is stability? In the present era, the only stable thing is "change ". The long-term use of CMM and traditional software engineering development teams are very disgusted with changes, even though they are still ignored. They like a stable environment, and they like it once and for all. Stability always makes people feel safe, but stability has a tendency to breed rigidity and stop creativity. In a very fine process definition, we do not have to think too much, but only execute the process on the production line like a machine. Chaos will lead to a sense of crisis and a solution to cope with it, which will lead to explosive growth and a sense of innovation.

Of course, too much chaos will lead to a lot of pressure on people, and confusion, while stability will make people in a coma. "Stability and chaos are equally destructive."! Therefore, the real team should leave the familiar and stable status and move towards chaos, but cannot be lost. Success will only come to those who have a sense of anxiety, those who can adjust their self-contradictions and confusion, and those who are creative enough.

"Innovation, creativity, and unexpected results come into being on the verge of chaos "!

Isn't that true for personal development? Isn't a nation on the verge of chaos (such as Japan and South Korea) more creative? Isn't it a "Hero of chaos? The true stability is to adapt ourselves to changes, rather than staying in a warm greenhouse. Instead, we have to go out to receive new air. The real stability is that when the change comes, you will not be able to stand on your own.

Of course, the most important thing is to achieve "edge" and maintain a balance between stability and chaos. This is very difficult, but we have no choice. Personally, my creed on personal development is: "Always engage in challenging things, but do not be too challenging. It is best to engage in 70% skilled people, 30% is something that has never been touched by. "This includes placing yourself in a fast-growing company, rather than forming a stable Company, and giving yourself a" chaotic edge ". In terms of software engineering, it is to make the goal so uncertain, and let the team adjust itself.

So should we discard the original software engineering and CMM? No! The answer is no. We need them, but we don't need them. The old dogmas will no longer be the shackles of our thoughts and creativity, but will become a tool to control this balance. The balance between control stability and chaos is the key.

"Boom at the edge of chaosThis is the most fundamental idea in this book. All the chapters in this book are filled with this idea.

<-Previous Page->