Version: 24.3

Managing Stories or Backlog Items

This article explains how to manage Stories or Backlog Items in Agility.

Overview

Stories (also called Backlog Items) are the primary Agile planning and tracking assets that are related to virtually all other system assets. Stories or Backlog Items represent discrete pieces of functionality that deliver business value. They can include requirements, additions or changes to existing functionality, or provide details about activities the project team must perform to deliver the product.

Stories or Backlog Items are managed in the backlog and can be comprised of:

Acceptance Tests (or Tests) to define acceptance criteria for the functionality
Tasks to define discrete work units for the team to complete to deliver the story

All stories belong to a project and can be scheduled for work in a sprint or iteration. Stories or Backlog Items are often derived from larger-grained features called portfolio items. In addition, stories or backlog items can be grouped into flexible backlog groups, which can form a hierarchy above stories, and backlog goals or objectives, which allow for a many-to-many mapping to stories or backlog items.

Rollup Category Status Values

Using Tasks to Breakdown Stories Backlog Items

Release Scheduling

Using Templates to Create Reusable Portfolio Items Stories Backlog Items or Defects

Portfolio Item Overview

Managing Ideas

Adding or Creating a Story

Closing Story

Deleting Story or Backlog Item

Editing Story

How do I fix broken image links in rich text fields

Moving Story or Backlog Item to Different Project