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 | |
About The Author
Rachel Davies
Rachel Davies specializes in coaching teams in agile software development and has experience in managing teams, requirements analysis, and programming in several languages. Rachel is a frequent presenter at, and organizer of, industry conferences and she also serves on the board of the AgileAlliance. She is coauthor of the book Agile Coaching.
Rachel has provided guidance to a number of companies to assess their agility level and… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.