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:
“To the indefinite, uncertain mind of the American radical the most contradictory ideas and methods are possible. The result is a sad chaos in the radical movement, a sort of intellectual hash, which has neither taste nor character.”
—Emma Goldman (1869–1940)
“That is the way of youth and life in general: that we do not understand the strategy until after the campaign is over.”
—Johann Wolfgang Von Goethe (1749–1832)