Agile Requirements and the Art of Communicating

Posted June 30, 2006 | |

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.

About The Author
Kert Peterson
As founder and President of Enterprise Agile Group of Austin, Texas, USA, Kert Peterson helps companies achieve business results by applying agile methods to their projects and across their organizations. His pioneering approach has transformed the way IT workforces -- from large and small companies -- perform and create value for their internal and external customers. Mr. Peterson has provided business and technical consulting services to a… Read More
Matt Smith
Matt Smith is a legendary improviser and solo performance artist who has taught thousands of people to become more effective by applying the principles of improvisation to their lives and work. His passion is to help groups discover and apply a powerful approach to the collaborative process that keeps them on the path of productivity. Mr. Smith has studied Scrum with Ken Schwaber and has led workshops of his own designed for agile practitioners… Read More
Don’t have a login? Make one! It’s free and gives you access to all Cutter research.