Chaos Strategy
The chaos strategy is a strategy of software development based on the chaos model. The main rule is always resolve the most important issue first.
- An issue is an incomplete programming task.
- The most important issue is a combination of big, urgent, and robust.
- Big issues provide value to users as working functionality.
- Urgent issues are timely in that they would otherwise hold up other work.
- Robust issues are trusted and tested. Developers can then safely focus their attention elsewhere.
- To resolve means to bring it to a point of stability.
The chaos strategy resembles the way that programmers work toward the end of a project, when they have a list of bugs to fix and features to create. Usually someone prioritizes the remaining tasks, and the programmers fix them one at a time. The chaos strategy states that this is the only valid way to do the work.
The chaos strategy was inspired by Go strategy.
Read more about this topic: Chaos Model
Famous quotes containing the words chaos and/or strategy:
“Unable to create a meaningful life for itself, the personality takes its own revenge: from the lower depths comes a regressive form of spontaneity: raw animality forms a counterpoise to the meaningless stimuli and the vicarious life to which the ordinary man is conditioned. Getting spiritual nourishment from this chaos of events, sensations, and devious interpretations is the equivalent of trying to pick through a garbage pile for food.”
—Lewis Mumford (1895–1990)
“To a first approximation, the intentional strategy consists of treating the object whose behavior you want to predict as a rational agent with beliefs and desires and other mental states exhibiting what Brentano and others call intentionality.”
—Daniel Clement Dennett (b. 1942)