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?
Early and Often: Elaborating Agile Requirements
Posted June 30, 2006 | |
![](/sites/default/files/styles/square_thumbnail_180x180_/public/itjournal/fulltext/2006/07/itj0607a/itj0607afig01.gif?itok=SATgslF8)
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.