Embed Notice

@inthehands I guess my org uses “requirements” in a couple of different senses. The general case is “gathering requirements” and that’s what you are calling goals and constraints.

And the second sense is very narrow and tactical: we break each feature up into user stories and we say the story isn’t done unless the requirements are done. But there’s a big gap between the two, for the design department to turn requirements (hopes and goals and constraints) into concrete features