The Backlog and Team Backlog modules enable you to create the items you need for product development, prioritize these items, and then plan development cycles for your application, including:
Create product epics and features
Create stories for items to develop
Plan development cycles/sprints
Add tests of your features and stories
Track release and sprint development progress
A backlog is a list of work items that need to be handled during product development. The following diagram illustrates how the backlog is organized:
The backlog is organized on a number of different levels:
|Releases||Individual instances where you distribute a completed version of the application. The release provides the framework around which you organize the backlog items.|
|Epics||The top-level objectives your product must meet, or the product's high-level functional areas. Epics can be and are implemented across releases.|
|Features||A deliverable unit of the application which is utilized by users. These areas are typically implemented within the scope of a release.|
The functional parts of a feature. Stories include user stories, quality stories, and defects and are assigned first to a team and then to an individual developer.
In ALM Octane, the Backlog module displays all of your backlog items (epics, features, user stories, defects) and their tests. The Backlog is displayed as a tree containing a hierarchy of your epics and features. The tree displays only features that are assigned to the selected release, and epics that contain such features:
The main Backlog page displays epics, features, stories, or tests, according to the epic or feature selected in the tree:
Select an image to navigate directly to the topic about this phase and learn more.
As you work in the Backlog in ALM Octane, there are distinct phases of work:
|Build the product backlog||
You add all the epics, features, and stories - regardless of when you plan to develop or release them. After adding the list (a continual process), you can then rank them.
|Plan a release||
From the full list of backlog items, you assign specific items to releases. You then further assign them to a sprint or development cycle and a team within the release.
|Manage the team backlog||
With all items assigned to teams, you then designate specific users to perform the development work.
|Work on your stories||
Once a story has been assigned to you, you can mark the progress of the stories, including the phase of the story, as well as add tasks to show the different aspects needed to complete the story's development.
|Create and run tests||
After (or in parallel with) working on your stories, add tests to ensure that your improvements work properly in your application's build.
In parallel with working on stories and creating/running tests, you view the progress and quality of your development using the various graphs and widgets available.
|Assign items to application modules||
In addition, you can assign each story to an application module, enabling you to gain a more comprehensive view of the application's development and quality.