Brief summary of this article:
User Story is a piece of work that helps to implement some business requirement and deliver value. It should try to capture a single functionality, enhancement, use case, scenario or role.
User Stories in Agile Approach to Software Development
User stories are part of an agile approach that helps shift the focus from writing about requirements to talking about them. All agile user stories include a written sentence or two and, more importantly, a series of conversations about the desired functionality.
User stories are short, simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. They typically follow a simple template:
As a < type of user >, I want < some goal > so that < some reason >.
More information: User Stories and User Story Examples by Mike Cohn.
User Stories in Targetprocess
User Story in Targetprocess is one of the key entity types in the data model.
A User Story can be split to smaller Tasks, and can be part of some larger Feature and Epic.
User Stories are denoted by light blue color.
Terms
The following custom terms and aliases are frequently used for User Story entity:
- Story, Work Item, Deliverable, Item, Job, Issue, Ticket, Portfolio Item, Component
- Initiative, Activity, Action
- Requirement, Objective, Goal, Use Case
- Newcomer, Candidate - in human resources management workflows
- Article - in publishing workflows
More on custom process terms: Rename Terms (Entity Types).
Parent Entities
User Story always belongs to a single Project. It is listed in Project field in Info panel. Parent Program of the Project is automatically inherited by a User Story.
User Story may belong to single Feature. It is listed in Feature field in Info panel. Project of the parent Feature may differ from Project of its User Story.
Parent Epic of the Feature is automatically inherited by a User Story. User Stories cannot belong to Epics directly. You have to assign User Stories to intermediate Features that belong to an Epic.
User Story may belong to single Release. It is listed in Release field in Info panel.
User Story may belong to single Iteration. It is listed in Iteration field in Info panel. Parent Release of the Iteration is automatically inherited by a User Story.
User Story may belong to single Team Iteration. It is listed in Team Iteration field in Info panel.
Nested Entities
User Story may have multiple nested Tasks. They are listed on Tasks tab. A Task always belongs to a single User Story.
User Story may have multiple related Bugs. They are listed on Bugs tab. A Bug may be related only to a single User Story.
Effort and Progress Calculation
In processes using Ideal Hours as Effort estimation unit total Effort of a User Story always includes total Effort of its Tasks. Effort of nested Bugs is not included.
Total time spent of a User Story always includes total time spent on its Tasks. Time spent on nested Bugs is not included.
Time tab in a detailed view of a User Story shows Time entries posted to the User Story itself and the ones posted to all its nested Tasks.
More information
Still have a question?
We're here to help! Just contact our friendly support team.
Find out more about our APIs, Automation Rules, Mashups and custom extensions.