Tyner Blain is writing about a subject of intense interest to product teams:
A classic debate. It comes up often. Unfortunately, it's a source of confusion that causes many teams to shy away from staffing, creating, or managing any formal requirements processes. There's a discussion on Seilevel's forum where this has been brought up again, and it's shaping up to be a fine grudge match here in Austin. Thanks to Cauvin for calling it to our attention. We can't let the other folks have all the fun, so we'll chime in too.
We've described the software development process before as being like an onion-- having multiple layers of abstraction within which you describe the problem and solution. In this post we will translate that perspective into "what is a requirement" and "what is design".
Read the details in Requirements vs design.
