In the book, "Chaos" as a term, I think some mouth, so it is changed to "confusion".
In the current software development, the ability maturity model (CMM) developed by the Software Engineering Association is known as the Holy Cup, and in today's world, with the extent of software development, it is divided into five levels. The higher the higher level, the process is more and more. It is to pursue a stable, a controllable effect. It also has achieved a rapid development result.
However, CMM / ISO9000 / BRP is developed by the book as "milestone" in a book, can only survive under a stable condition, that is, demand will not change during development. If you are in a complex and variable-changing environment, if the customer doesn't know the details, the outside environment is uncertain. At this time, this method will be difficult to survive. And the team or company under this model is difficult to enter another area, engaged in another new software development.
What is stable? For the current era, the only stable is "change". The team used to develop CMM and traditional software engineering developed very disgusted, and they were afraid of life and death, they also told. They like a stable environment, they like one for all. Stability is always safe, but stabilizes the tendency of breeding dead plates and stifle creativity. In a very fine process definition, we have no excessive idea, but only perform a process on the production line like a machine. The chaos will make people feel the sense of crisis, they will find ways to respond, so they will make people explosive and innovative awareness.
Of course, too many chaos will enhance the pressure that the people are too large, and the mental disorder, and stability will make people in a coma. "Stable and chaos have the same destructive"! Therefore, the real team should leave the familiar and stable state, moving towards chaos, but it can't lose it. Success will only fall in people who maintain their sense of consciousness, those who can adjust their self-contradiction, confused mood, and those who keep enough creative.
"Innovation, creativity and sudden results come in the edge of chaotic"!
Isn't it like this for personal development of people? Isn't it more creative in a nation (such as Japan and South Korea) in "chaotic edge"? Not "chaos out of the hero"? Really stable is to make yourself adapted to change, not to stay under the warm greenhouse. Instead, you have to go out to receive new air, then he is afraid of the hurt. The real stability is that when the change comes, she still does not fall.
Of course, the most important thing is to achieve "edge", keep stability and chaos a balance, which is very difficult, but we have no choice. In a person concern, my creed for personal development is - "Always engage in challenge, but don't have a challenge, it is best to do 70% is skilled, and 30% have never been touched." Include companies put themselves in a high-speed company, rather than forming a robust company, but also gives yourself a "confusing edge." For software engineering, it is necessary to make the goal is so uncertain, and let the team adjust itself.
So, is we going to abandon the original thing of the software project, abandon CMM? Do not! the answer is negative. We need them, just over, the original dogma is no longer a shackle that binds our ideological creativity, and turns into tools that control this balance. Control stable and chaotic balance, this is the key.
"The prosperity of chaos", this is the most fundamental idea of this book, all of the chapters in the book are full of this idea.
<- Previous Next->
