# Edge of Chaos and Hyper Productive Software Development Teams

DevFeed: [Edge of Chaos and Hyper Productive Software Development Teams](<https://devfeed.tech/articles/edge-of-chaos-and-hyper-productive-software-development-teams-30321.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/edge-of-chaos-hyper-productive-teams/>)

Published: 2008-12-02T15:41:57Z

Content type: article

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [software-development](<https://devfeed.tech/topics/software-development.md>), [Self-organizing Team](<https://devfeed.tech/topics/self-organizing-team.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [development-process](<https://devfeed.tech/topics/development-process.md>)

Tags: [adaptive](<https://devfeed.tech/tags/adaptive.md>), [am](<https://devfeed.tech/tags/am.md>), [apply](<https://devfeed.tech/tags/apply.md>), [base](<https://devfeed.tech/tags/base.md>), [but](<https://devfeed.tech/tags/but.md>), [call](<https://devfeed.tech/tags/call.md>), [can](<https://devfeed.tech/tags/can.md>), [cas](<https://devfeed.tech/tags/cas.md>), [cellular](<https://devfeed.tech/tags/cellular.md>), [cellular-automata](<https://devfeed.tech/tags/cellular-automata.md>), [changes](<https://devfeed.tech/tags/changes.md>), [chaos](<https://devfeed.tech/tags/chaos.md>), [complete](<https://devfeed.tech/tags/complete.md>), [complex](<https://devfeed.tech/tags/complex.md>), [creative](<https://devfeed.tech/tags/creative.md>), [development](<https://devfeed.tech/tags/development.md>), [edge](<https://devfeed.tech/tags/edge.md>), [software](<https://devfeed.tech/tags/software.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [teams](<https://devfeed.tech/tags/teams.md>)

## AI overview

The excerpt argues that software teams may be most productive between rigid order and unchecked chaos: heavy processes can suppress creativity, while having no rules can leave teams stuck in "hack & fix." It connects this balance to agile practices such as feedback, information exchange, adaptability, and self-organization, and relates those qualities to Clinton Keith's conditions of independence, leadership, core competency, and cooperation. The author says hyper-productivity is difficult to define, presents these properties as ones that may help achieve it, and suggests that CTOs, CIOs, project managers, and Scrum Masters should remove obstacles that impede teams. The excerpt does not provide a detailed method for measuring or reliably producing hyper-productivity.

## Source excerpt

Many researchers tend to think that CAS may work efficiently at the edge of chaos. A system with a very high order can't solve complex creative tasks, as well as a pure chaotic system. It seems the system should balance between chaos and order to survive and adapt. The "edge of chaos" term was emerged during self-reproductive cellular automata researches in 1990. It appeared that at a particular noise level the system can reproduce its state, while at a low noise levels states are random. This edge value was mathematically analyzed and it was shown that in such a state the system has a maximum of information. The "Edge of Chaos" term spread and applied to complex adaptive systems. For example, we may suggest that evolution drives systems to the edge of chaos, and it is one of the reasons of life origin. Life is a very interesting and complex thing in itself. Most likely it could not appear neither in order state and in chaos state. Life exists if there is a stable base, but with possibilities of changes. Edge of Chaos and Software Development How can we apply the edge of chaos concept to software development? Obviously, edge of chaos is a state where the development team works with maximum efficiency. Complex processes and explicit rules impede creativity. The team becomes too ordered to think :). On the other hand, no processes and no rules lead to chaos. The development team can't complete anything useful, and that is something we call hack & fix process. As a software development folks, we are particularly interested in two questions: How can we drive the team to the edge of chaos? How we will ensure that the team is at the edge of chaos? The human who knows the answers to these questions most certainly will be rich and famous. However I am not sure whether you can find such a man. It is obvious that edge of chaos = hyper productivity. This term often used in Scrum. However it is quite hard to define hyper productivity. Hyper-productive teams are hard to define.