Requirements are these wet pieces of bath soap you can’t get a strong hold on.
“The replacement activities of creating hypotheses, conducting research, creating scenarios, and running critiques will take more time. A lot more time. How do we do that when our schedules are already full? We have to put it into context with the rest of the project. How much time will we save by getting closer to a great design faster? How much time will we get back because everyone is on the same page about why we’re doing what we’re doing? We spread these activities evenly throughout the project, instead of a small box upfront. They make practically every other box in the project chart better and faster. In a weird twist of project physics, we end up saving time by spending time. Most importantly, we end up with a design that uses real requirements to create a great experience. That’s what we were brought in to do in the first place.”
(Jared Spool ~ User Interface Engineering)