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.

Video producer: http://geecon.org/

One thought on “Agile Requirements by Example”

Comments are closed.

Videos

Design Thinking Activities

This video explains that the six stages of the design thinking process can be supported by a very wide range of UX methods and activities. Don’t limit yourself to the most commonly mentioned methods.

Read More
Videos

Wardley Maps: Business Analysis, Experimentation & Evolution

This presentation explains how Wardley Maps were used to inform the always evolving strategy for the modernization of Ticketmaster’s core ticketing platform not only in terms of technical capabilities and architecture but also process maturity, organizational design, and more.

Read More
Videos

Analytics vs. Quantitative Usability Testing

Analytics and Quantitative Usability Testing UX research techniques help you gain quantitative insight into user behavior. However, each method provides different types of information and can answer different kinds of research questions.

Read More

Copyright © 2009-2021 Martinig & Associates