The first step in the development process is building and prioritizing the product backlog. Use the Backlog module to perform this work.
You can create a backlog in ALM Octane either by entering items in the ALM Octane UI, or by importing items from an Excel spreadsheet.
Note: We use Optimistic Locking to prevent data loss when users make changes to the same entity concurrently.
If an item changed on the server before you saved your changes, you are prompted to refresh the entity from the server and make your changes again. The refresh and restore button now reloads the entity from the server instead of just undoing your changes.
Follow the procedure below to enter backlog items in the ALM Octane UI, or see Import backlog items to import your backlog from an Excel file.
To enter backlog items in the ALM Octane UI:
- Open the Backlog module, and select either the Epics, Features, or Backlog Items tab.
With the Add button select the item you want to create: epic, feature, user story or quality story.
Fill in the fields.
Tip: Click the Customize fields button to add or remove fields from the form. For more details, see Customize forms.
Stories and features that you do not associate with a feature or epic are children of the root Backlog node. To view these in the grid, select the root Backlog node, and open the User Stories or Features grid.
- Optional. Use the Autofill feature to populate new backlog items with sets of predefined values. For details see Fill in fields automatically.
Optional. Create tasks for a user story in the Tasks to generate field.
You can change a backlog item's parent: Either drag the item to a different node in the tree, or edit the item's Feature or Epic field.
You can create autofill templates that help you fill in new items with predefined field values.
Example: In a data set for a user story, you can include a list of tasks in the Tasks to generate field. Those tasks will be automatically created in every story that you create using this data set.
To save an autofill template:
- Fill in an Add <item> form with the field values that you want to repeat.
- At the top of the form, click Save as template.
- Choose a name for the template, and select whether you want to share the template with other users.
To apply an autofill template:
While creating a new item, select the autofill template that you want to use. The fields are automatically populated with the saved values.
Backlog items in ALM Octane do not have a fixed rank number. Instead, in any given grid, items are listed by order of their relative ranking, and numbers them from 1 to [no. of items in the grid].
New items are added to the backlog with the lowest rank.
To rank backlog items:
Click the Rank column header to sort the grid by rank.
Use these methods to change rankings:
Drag one or more items up or down the Grid View or Smart List View.
Click the rank number and type in a new value.
Right-click an item and select Rank Highest or Rank Lowest.
Note: ALM Octane does not support ranking for grouped items.
After you set ranks, ALM Octane preserves the ranking even after you sort the grid by another field. When you sort again by rank, ALM Octane restores the ranking.
Dependencies are the relationships between activities that determine the order in which the activities need to be performed.
There are different types of dependencies. In ALM Octane, we employ the Finish-to-Finish dependency type, meaning that activity A (predecessor) must finish before activity B (successor) can finish. This is not determined by dates, but rather using sprints or releases. The predecessor must be in a previous release/sprint or in the same release/sprint as the successor.
You can create dependencies between features, user stories, and defects.
You can see dependencies in the:
- Relations tab. Create and view dependencies between features, user stories, and defects.
- Planning board. View dependencies between features and identify problematic dependencies. For details, View dependencies and identify problematic dependencies.
To create a dependency:
- Open the Relations tab in the successor item.
- Click Add Relation > Preceded By.
- In the Add features, user stories, defects dialog box, add the predecessor item or items.
The WSJF formula is a well-established method for determining epic and feature priorities. It uses parameters and a calculated measurement to determine an WSJF score for an item.
In the feature or epic details, set the value of WSJF-specific fields:
|Business Value||The item's value to customers or the business. For example, how the epic or feature affects revenue.|
|Time Criticality||The urgency to deliver the epic or feature.|
|RR | OE||The epic or feature's value in eliminating risks or creating new opportunities.|
|Cost of delay||
The difference between an epic or a feature being available now or later. The Cost of Delay is the sum of the above components:
Cost of Delay = Business Value + Time Criticality + RR | OE
|Job size||The estimated length of time need to finish the epic or feature. You measure this using your own unit (hours, story points, and so forth).|
The ratio of the cost of delay and the job size. The higher the WSJF score, the higher the priority of the epic or feature.
WSJF Score = Cost of Delay / Job Size OR
For the WSJF fields (Business Value, Time Criticality, and RR | OE), select a value from the list. For the Job Size measurement, enter any integer value.
When working in the Backlog module, you may want to update a common attribute of many items.
To update multiple backlog items:
In the Grid View or Smart List View, select up to 200 items.
Right-click and select Bulk Update.
In the Bulk Update dialog box, select up to 5 fields
Click Update to apply the changes.
Some fields cannot be updated with Bulk Update, including user-defined fields.