This feature is available in all editions.
During the planning process, you organize your backlog so that the work items are ranked in order of importance relative to each other, with the most valuable work items shown at the top. This allows the team to see exactly what they should work on first and what they can wait on. This article explains why ranking is important and gives you several ways to rank, sort, and prioritize your work in Lifecycle.
Prioritization (also called ranking by priority) and ranking are the primary activities Product Owners perform to determine when items make it into the development backlog. By looking at each work item's priority value, complexity, size, and other factors, they can fine tune which items to schedule in a sprint/iteration before others.
Ranking can occur on high-level portfolio items (e.g., epic or initiative) all the way down to individual stories and defects in a team's backlog. The ranked backlog can then be used as an input during release planning and sprint/iteration planning activities.
When moving backlog items into the backlog queue, you should optimize on both prioritization and ranking. However, some Agile methodologies such as DSDM, promote the practice of taking a mix of high, medium, and low priority items on within each sprint/iteration. That approach encourages the team to pay attention to both big and little things as they move through the release, spreads out the risk, and allows for easier decision making.
In VersionOne Lifecycle, there are several ways to rank work items:
In the Spring Release 2016 (16.1), the WSJF feature was added to Lifecycle. This feature is not available in prior releases.
SAFe® and Scaled Agile Framework® are registered trademarks of Scaled Agile, Inc.