Business needs change, the competitive landscape changes, so system requirements must also be able to change if we want to deliver software that satisfies our customers. That's agile development in a nutshell, right? But what if we're so focused on the rapid development of working software "trees" that we don't see the "forest" of business requirements? In this issue we debate whether agilists really get requirements -- and what to do about it if they don't.