The A.A.R.T. of Writing User Stories

Current user stories used to manage Agile requirements can be improved by clearly identifying, linking, and tracking Actors, Action, Results, and Tests. (A.A.R.T).

Writing user stories in the form of: Fred (Actor) drinks coffee (Action) to wake up. (Result) …is more clear than the traditional user story, and easier to understand and write for non-native users of English. Requiring at least one Test , written as user instruction for the Actor, increases the chances of detecting flawed requirements early.

Video producer: http://agileprague.com/

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