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

Why Learning Product Organizations Experiment Frequently

Many organizations are afraid of designing and running experiments for product development. Validation of the assumption approach has not been widely spread in the industry as a standard. Hypotheses are taken as facts and they are turned into requirements and features without verification. In contrast, other companies seem to be more customer value-oriented and validate […]

Read More
Videos

Designing a Scalable Product & Engineering Methodology

Are you bored by hearing about Spotify’s Model, Basecamp’s Shape Up, or Netflix’s “No Rules Rules”? All of them do have something in common. They tailored something unique to match both their ambition and their strengths, while honestly acknowledging their weaknesses.

Read More
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

Copyright © 2009-2022 Martinig & Associates