Architectural manifesto, Adopting agile development, Part 4

Using user stories to define project requirements

From the developerWorks archives

Mikko Kontio

Date archived: December 15, 2016 | First published: July 01, 2008

In Part 4 of this series, learn about how to define requirements in an agile environment. In all software development projects, everything is based on requirements. Because agile development emphasizes spoken communication over written documents and welcomes changes late in development, traditional methods of writing requirements might not be adequate. In this article, learn about agile requirements and how user stories can help describe them.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.

ArticleTitle=Architectural manifesto: Adopting agile development, Part 4