Plan to throw one away; you will, anyhow.

E173640

"Plan to throw one away; you will, anyhow." is a famous software engineering adage from Fred Brooks emphasizing that the first version of a system is inevitably flawed and should be expected to be discarded.

All labels observed (1)

Label Occurrences
Plan to throw one away; you will, anyhow. canonical 1

How this entity was disambiguated

Statements (48)

Predicate Object
instanceOf software design principle ⓘ
software development maxim ⓘ
software engineering adage ⓘ
appliesTo complex information systems ⓘ
large software systems ⓘ
long-lived software products ⓘ
author Fred Brooks ⓘ
category Brooks's laws and principles ⓘ
linked to: Brooks's law

software engineering aphorisms ⓘ
contrastsWith assumption that the first design can be final ⓘ
one-shot, big-design-up-front approaches ⓘ
coreIdea initial implementations are inevitably flawed ⓘ
learning from the first system informs the real system ⓘ
planning must include time and budget for a throwaway version ⓘ
teams should anticipate building at least one throwaway version ⓘ
the first version of a system will likely be discarded ⓘ
field software design ⓘ
software engineering ⓘ
software project management ⓘ
goal align design with real user needs discovered through experience ⓘ
improve the quality of the eventual production system ⓘ
reduce risk in large software projects ⓘ
hasPart assumption that requirements are not fully known at the start ⓘ
recommendation to treat the first system as a learning tool ⓘ
warning against over-investing in the first implementation ⓘ
influenced iterative software lifecycle models ⓘ
modern agile practices ⓘ
prototyping methodologies ⓘ
language English ⓘ
mainSubject design iteration ⓘ
iterative development ⓘ
prototyping ⓘ
requirements discovery ⓘ
software project planning ⓘ
software system versioning ⓘ
quotationText Plan to throw one away; you will, anyhow. ⓘ
relatedConcept iterative and incremental development ⓘ
learning curve in software projects ⓘ
proof of concept ⓘ
prototype ⓘ
software evolution ⓘ
technical debt ⓘ
waterfall model critique ⓘ
statedIn The Mythical Man-Month ⓘ
timePeriod 1970s ⓘ
usedBy project managers ⓘ
software architects ⓘ
software engineers ⓘ

How these facts were elicited

Referenced by (1)

Full triples — surface form annotated when it differs from this entity's canonical label.

The Mythical Man-Month → hasQuote → Plan to throw one away; you will, anyhow. ⓘ