Agile Requirements by Example

System-building projects which fail (which is many of them) do so more often because they build the wrong thing, not because they do a bad job of building the right thing. The Agile community has developed a range of techniques for making sense of system requirements and capturing them in artifacts that are familiar and understandable by business, useful to developers and informative to managers.

The central concept is that of a “checked example”. This video illustrates some of these techniques and artifacts by example and discusses the impact that they can have on users, developers and managers.

[vimeo 45626752 480 270]

Video producer: http://geecon.org/