Learn how to write user stories that do not belong to any use case.
Learn how to write user stories based on the use cases identified with stakeholder.
Each user story can be in one of the six statuses. These statuses are common to most scrum projects. In this article we will show you how to use and configure user story statuses.
Perform accurate estimation on user stories to achieve the continuous delivery of workable features. This article will show you how to perform estimation on user stories.
Besides writing description and documenting the confirmation items for user stories, you may want to categorize them in further. In this page you will see how to add tags to user stories.
Filter off the non-interested user stories, based on the use cases they belong to, their statuses and the added tags.
Learn how to order user stories based on their business value.
By using the link feature to locate user story, you can provide teammates with accurate link of a specific user story. In this page, you will know how to work with the link feature.
Identify stakeholders' problems and the solutions they expect through discussion, and record the conversation in Conversation Items tab of UeXceler.
Write down the cases that need to be tested in system development. Strictly speaking, a user story can only be confirmed until all of its confirmation items are fulfilled.
A user story scenario specifies the interaction between the end user and the system in completing the goal represented by the story. This article shows you how to use user story scenario.
By performing scenario-based wireframing, you can present your scenarios to your customer visually to obtain consent to the requirements easier. This page teaches you how to do this.
Showing a screen flow of the system to your customer guarantees your customer knows what will be delivered by the end of the project. In this page you will learn how to show wireframes to your customers.
Storyboard is a useful technique in system analysis and design in that it represents the screens and screen flow under different scenarios and situations. You will learn how to add storyboard to user story in this page.
You can optionally add sub-diagrams or reference material, including supplementary files that help to design the system. This page will talk about this in detail.
Whenever a major change is made to a user story, a log is written automatically. In this article we will show you how to access the logs of a user story.
Besides writing user stories in UeXceler, you can also write user stories on any diagrams, like BPD. This article will show you how it works.
|Chapter 1. User Story Map||Table of Contents||1. Writing general user stories|