loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Managing Agile Project Requirements with Storytest-Driven Development
January/February 2008 (vol. 25 no. 1)
pp. 68-75
ASCII Text
x 
 
Rick Mugridge, "Managing Agile Project Requirements with Storytest-Driven Development," IEEE Software, vol. 25, no. 1, pp. 68-75, January/February, 2008.
 
 
BibTex
x
 
@article{ 10.1109/MS.2008.11,
author = {Rick Mugridge},
title = {Managing Agile Project Requirements with Storytest-Driven Development},
journal ={IEEE Software},
volume = {25},
number = {1},
issn = {0740-7459},
year = {2008},
pages = {68-75},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2008.11},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Managing Agile Project Requirements with Storytest-Driven Development
IS - 1
SN - 0740-7459
SP68
EP75
EPD - 68-75
A1 - Rick Mugridge,
PY - 2008
KW - requirements
KW - requirements specification
KW - design
KW - storytest
KW - agile development
KW - test-driven development
VL - 25
JA - IEEE Software
ER -
 
Rick Mugridge, Rimu Research
Agile project teams aim to include both business and development personnel, emphasizing direct communication over written requirements documents. Rather than trying to understand all of a system?s detailed requirements before development, they carry out high-level release planning and then drive small development increments in cycles of one or two weeks. Doing so avoids many of the potential problems in traditional, phased software development approaches and accepts that changes are inevitable. Storytest-driven development brings requirements and automated testing ideas and practices together to support this agile process. The author describes this development approach and how its concrete examples can clarify and communicate business rules, aid agile team discussions, and facilitate team members? understanding of the concepts at the heart of the business needs. Such examples are executable, serving a secondary role as automated tests.

1. D.G. Reinertsen, Managing the Design Factory, The Free Press, 1997.
2. K. Beck, eXtreme Programming Explained, 2nd ed., Addison-Wesley, 2004.
3. J. Kerievsky, "Coined Storytest and Storytest Driven Development," Industrial XP, www.industrialxp.orgstoryTdd.html.
4. R. Mugridge and W. Cunningham, Fit for Developing Software, Prentice Hall, 2005.
5. K. Beck, Test Driven Development: By Example, Addison-Wesley, 2002.
6. E. Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software, Addison-Wesley, 2003.
1. U. Koch and M. Boxall, "Testing Mobile Handsets with FitNesse," 2006, http://video.google.co.ukvideoplay?docid=582823406455567909(video) .
2. P. Gandhi et al., "Creating a Living Specification Using Fit Documents," Agile 2005 Conf. (Agile 05), IEEE CS Press, 2005, pp. 253–258.
3. R. Bohnet and G. Meszaros, "Test-Driven Porting," Agile 2005 Conf. (Agile 05), IEEE CS Press, 2005, pp. 259–266.
4. G. Melnik and F. Maurer, "Multiple Perspectives on Executable Acceptance Test-Driven Development," Proc. 8th Int'l Conf. Agile Processes in Software Eng. and Extreme Programming (XP 07), LNCS 4536, Springer, 2007, pp. 245–249.

Index Terms:
requirements, requirements specification, design, storytest, agile development, test-driven development
Citation:
Rick Mugridge, "Managing Agile Project Requirements with Storytest-Driven Development," IEEE Software, vol. 25, no. 1, pp. 68-75, Jan./Feb. 2008, doi:10.1109/MS.2008.11
Usage of this product signifies your acceptance of the Terms of Use.