In software feature development (and many other creative problem-solving endeavors), it's wise to trade scope for **quality** while fixing time—ideally to no longer than six weeks per project since software has no natural boundaries. This keeps the scope variable, which may seem counterintuitive. **Time** budgets, while seemingly arbitrary, act as creative constraints that force focused thinking within defined limits.
Projects without time constraints tend to succumb to entropy, growing ever more complex while draining team energy. Since human **energy/inspiration** is finite, preserving motivation becomes crucial. A fair and fixed timeline for “some version” of a thing helps in two ways: it makes decisions feel less permanent (since another project cycle is always approaching), and it encourages trading scope for quality. Teams become more likely to launch successfully because the excitement of starting something **new** outweighs the temptation to extend the current project indefinitely.
Image courtesy of Ryan Singer.
2. Appetites, not Estimates