loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Agile Requirements: Opportunity or Oxymoron?
May/June 2004 (vol. 21 no. 3)
pp. 71-73
ASCII Text
x 
 
Ken Orr, "Agile Requirements: Opportunity or Oxymoron?," IEEE Software, vol. 21, no. 3, pp. 71-73, May/June, 2004.
 
 
BibTex
x
 
@article{ 10.1109/MS.2004.1293075,
author = {Ken Orr},
title = {Agile Requirements: Opportunity or Oxymoron?},
journal ={IEEE Software},
volume = {21},
number = {3},
issn = {0740-7459},
year = {2004},
pages = {71-73},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2004.1293075},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Agile Requirements: Opportunity or Oxymoron?
IS - 3
SN - 0740-7459
SP71
EP73
EPD - 71-73
A1 - Ken Orr,
PY - 2004
KW - requirements
KW - agile development
KW - primary outputs
VL - 21
JA - IEEE Software
ER -
 
Although some agile development advocates suggest that requirements aren't really necessary in an agile environment, the department this issue discusses how every system of consequence needs good requirements. Additionally, it attempts to clarify what "doing requirements" really means.
Index Terms:
requirements, agile development, primary outputs
Citation:
Ken Orr, "Agile Requirements: Opportunity or Oxymoron?," IEEE Software, vol. 21, no. 3, pp. 71-73, May/June 2004, doi:10.1109/MS.2004.1293075
Usage of this product signifies your acceptance of the Terms of Use.