user stories
User Stories Are Not Requirements
The common wisdom is that Agile register requirements using the user stories format: “”As a , I want <goal/desire> so that “. In this article, Earl Beede explains why user stories are not requirements.
Read More
Describe User Interaction with Scenarios and Storyboards
A user story is a tool to describe the product functionality, but it is less useful suited to describe in detail the user interaction. Agile scenarios and storyboards are tools you need to describe the interaction steps. In his post, Roman Pichler what scenarios and storyboards are, how they can be used effectively in an […]
Read More
Creating a User Story Map
A user story map is a technique created by Jeff Patton where you arranges you user stories into a useful model to help understand the functionality of the system. In this blog post, Steve Rogalsky explains how to create a user story map.
Read More
User Stories That Are Too Big
In this blog post, Jeffrey Davidson discusses the fact that a common issue for Scrum teams is that their user stories are too big. He explains that many teams ask for larger stories because they don’t know how to slice the work into smaller pieces. Writing smaller user stories will make your team happier and […]
Read More
Can Requirements and Agile Work Together
This software testing podcast discusses why requirements are still needed in many projects, and how to work with both requirements and user stories to deliver on the promise of Agile.
Read More
Lightweight User Story Mapping
User story mapping might look like the heavy weight mapping of the past, but it is not. However, if you can’t map your stories back to business value, then why do they make or save the company money? Learn how to improve your business analysis with Agile story mapping.
Read More