- Playful mechanisms for iterative design over anticipating hard problems and learning how to schedule and plan
- Working software today (for some value of working) over maintainable and full-featured software tomorrow
- Redefining minimum requirements for acceptance over identifying and responding to feature creep
- Constant renogotiation of goals over satisfying existing ones
That is, while there is value in the items on both sides of each equation, we value the ones on the left more because they are easier to achieve through their combination of flexibility and their inherent lack of definition.
Those who do not learn from history can appear to do so by redefining it.
