Stories

A story is a brief statement of a product requirement or a business case.

A story should be small enough to be completed in one sprint. The estimated effort required to complete a story is measured in story points, with more points being assigned to stories requiring more effort. Story points are arbitrary measurements of the effort (not necessarily the time) required to complete a story, based on the estimates of scrum team members. The work required for a story can be broken down into discreet scrum tasks.
Note: An epic can have one or more stories, but a story can belong to only one epic at a time.
Users with the following roles can create and edit stories:
  • scrum_master
  • scrum_product_owner
  • scrum_sprint_planner
  • scrum_story_creator
  • scrum_team_member

After creating stories and tasks, manage and track them to completion through the story and scrum task progress boards. Access the progress board from the Related Links section of the Story form as well as from other forms.For tips and best practices on writing effective stories, see Well-Written Scrum Stories.

Create a story

There are several ways to create a story.

  1. Create a new story in one of these ways:
    OptionAction
    Navigate to SDLC (Scrum Process) > Stories > Create New
    In a product, release, or sprint form select the Stories related list and click New.
    Display the product backlog in the planning board click New.
    Scrum new story
  2. Complete the Story form.
    Table 1. Story form fields
    Field Description
    Product The product with which this story is associated. This field is required if using the SDLC Scrum Process application (SDLC Scrum Process Pack plugin).
    Project The project with which this story is associated. This field is required if using the project-based SDLC application (SDLC PPM Integration plugin). For more information, see Project Portfolio Suite.
    Configuration item Select the configuration item or service this story affects, if applicable.
    Theme Select the theme for this story from a list of themes associated with the selected Product. A story can belong to only one theme at a time.
    Product owner [Read-only] Displays the product owner for the selected Product.
    Release Select a release for this story from the releases associated with the selected Product.
    Sprint Select a sprint for this story from the sprints associated with the selected Release.
    Epic Select an epic for this story from the epics associated with the selected Product.
    Priority Select the priority for this story. A product owner can use priorities to rank stories in the planning board.
    Opened Set the date and time for creating the story. The default is the current date and time.
    Opened by Select the user who created the story The default is the logged in user.
    Type Select the type of story:
    • Development
    • Documentation
    • Spike (research activity)
    State Select the story state. The default for a new story is Draft.
    Points Enter a number of points to indicate the estimated effort required to complete the story. A larger point value indicates that a greater amount of effort is required.
    Assigned to Select the user who will be working on the story. Users on this list have appropriate scrum roles.
    Blocked Select this check box to indicate that issues are preventing the story from making progress. Clear the check box if there are no blocking issues.
    Classification Select Defect or Feature to indicate the type of development the story involves. The default is Feature. This field has no connection to the Defect and Enhancement fields in the Related Records section.
    Acceptance criteria Describe the functional criteria or testing results required to move this story to a state of Complete.
    Work notes Enter any notes about the work being performed for this story.
    Related Records
    Defect This is a reference field from the Defect [rm_defect] table. Click the magnifier icon in this field to display defect reports created by users with the feature_user role. This is the only location in the Scrum Process application where records from this table appear. For details about reporting defects with this feature, see Defect Reports in Scrum.
    Enhancement This is a reference field from the Enhancement [rm_enhancement] table. Click the magnifier icon in this field to display enhancement requests created by users with the feature_user role. This is the only location in the Scrum Process application where records from this table appear. For details about enhancement requests, see Enhancement Requests in Scrum.
  3. Click Submit.
    Saving the form displays the Scrum Tasks and Documentation Tasks related lists.
  4. Create the necessary scrum tasks for this story from these related lists.

Create a story from an enhancement

The scrum product owner reviews enhancement requests and decides which ones require stories.

  1. Navigate to SDLC (Scrum Process) > Stories > Create New.
  2. Complete the form using the procedure for creating stories in scrum.
  3. Select the Related Records tab.
  4. Click the magnifier icon in the Enhancement field and select the request for this story.
  5. Click Submit.
    Scrum enhancement in story

Assign a story to a project

If you have activated the SDLC Scrum PPM Integration plugin, you can assign a story to a project from the Stories list.

About this task

Use the examples in the following steps to add choice tables, notes, tables, figures, step results, and postrequisites to the task.

Procedure

  1. Navigate to SDLC (Scrum Process) > Stories > Open Stories.
  2. Select the check box to the left of the desired story.
  3. Select Move to project from the Actions choice list.
  4. Select an active project in the Project field and click OK.
    The story is assigned to the selected project. When a story is assigned to a project, the settings in the following fields are cleared:
    • Release
    • Product
    • Sprint
    • Team
    • Epic
    • Theme
    If the project is assigned to a team and has a development phase, the following fields are auto-populated:
    • Team
    • Project phase