By Topic

Agile requirements: opportunity or oxymoron?

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)

We show that, in today's world, a requirement without agility is just as bad as agility without requirements. We have discovered a consensus that systems analysis and requirements definition, in particular, have fallen on hard times. Ten or 15 years ago we taught people structured analysis, information engineering, data modeling, and working with computer-aided software engineering tools to turn those requirements into running programs. Rather than understanding the user's business and information needs, some agile approaches attempt to give users what they say they want as quickly as possible. Every system of consequence needs good requirements. Without good requirements, the project risks increase dramatically. The better the requirements, the better people understand what they're trying to build (or acquire).

Published in:

IEEE Software  (Volume:21 ,  Issue: 3 )