The Community for Technology Leaders
RSS Icon
Issue No.01 - January/February (2008 vol.25)
pp: 68-75
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.
requirements, requirements specification, design, storytest, agile development, test-driven development
Rick Mugridge, "Managing Agile Project Requirements with Storytest-Driven Development", IEEE Software, vol.25, no. 1, pp. 68-75, January/February 2008, doi:10.1109/MS.2008.11
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.
3 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool