User stories serve a similar purpose as Use-Cases but are differ in several important respects. For example, User Stories are used to create time estimates and set priorities during a Release Planning meeting. They are also used instead of a large requirements document. User Stories are written from the point of view of the customers or end-users. User Stories should describe the things that the system needs to do for end-users. They are similar to Use-Case Scenarios, except that they are not limited to describing a user interface. They are in the format of about three sentences of text written by the customer in the customers terminology without techno-syntax.
Stories on this page describe activities around Acquisitions.
Acquisition Stories - All
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| maxResults | 99 |
|---|
| sort | title |
|---|
| label | +user_story, +us_acquisition,-us_duplicate |
|---|
| showSpace | false |
|---|
| space | @self |
|---|
|
Acquisition Stories - Complete
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| maxResults | 99 |
|---|
| sort | title |
|---|
| label | +user_story, +us_acquisition,+us_completed |
|---|
| showSpace | false |
|---|
| space | @self | cql | label = "user_story" and label = "us_acquisition" and space = currentSpace ( ) |
|---|
|
Acquisition Stories - Duplicates
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| maxResults | 99 |
|---|
| sort | title |
|---|
| label | +user_story, +us_acquisition,+us_duplicate |
|---|
| showSpace | false |
|---|
| space | @self |
|---|
|