[cateye]

I hate the term "requirements" with passion. It is almost always used by people without any vision or passion.

Why is it so unimaginable to create something without being able to articulate it beforehand? Or why wouldn't it be possible to start with something and letting it evolve by discovering new insights while building it?

How many successful things are really built by first writing down requirements?

Sometimes it is just an personal itch or curiosity. Other times it is actually total epiphany that brings success...

[aryehof]

Let's get 50 people to all start writing a complex payroll system, or critical embedded medical device software, on the basis of their "personal itch" or "epiphany".

When a project or task is individual or trivial, then who cares. When not, a "hack it 'till it (hopefully) works" approach doesn't cut it.

Edit: grammar

[bsg75]

If its a "personal itch or curiosity", sure.

If its a business process, lack of any form of requirements is how technical debt is guaranteed from the start.