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

Improving User Experience with Human-Centered Design

This video explores the different phases of a human-centered design approach and understand how it can help your organization drive customer loyalty by enhancing your digital product. Learn how some of our past clients have made this approach their priority and dive deep into each of the five phases of a human-centered design approach.

Read More
Videos

The 4 Pegs of Software Requirements Engineering

Bad software requirements can jeopardize projects. There is a considerable literature on software requirements, but practice is far behind: what passes for requirements in industry usually consists of a few use cases or user stories, which are useful but not sufficient for a solution. Can we fix requirements engineering (known in other circles as business […]

Read More
Videos

Collaborating With Stakeholders

To make UX research and requirements gathering more efficient and effective, you have to get everyone in the software development team and the user representatives involved. When the teams understand user concerns and usability issues, they become better at preventing problems.

Read More

Copyright © 2009-2021 Martinig & Associates