Kendis serves as the centralised workspace for visualising and prioritising work items (Features, Epics, Stories) synchronised from an Agile Lifecycle Management (ALM) tool (e.g., Jira, Azure DevOps). Effective backlog management in Kendis relies on three primary methods: Hierarchical Scope Control, Structured Prioritisation, and Integrated Flow Control. This technical guide outlines the procedures for optimising these backlog management methods.

Before any backlog analysis can begin, the scope of work visible in Kendis must be defined and synchronised via saved ALM queries (Filters).

From your Program Board, go to Settings > Manage Jira/ADO Filters.

Enter your scope-defining query in the primary filter field. This JQL typically targets issues assigned to a specific Program Increment (PI), spanning multiple Projects/Teams, and matching the high-level work item type (e.g., “Feature”).

Here is an example of a JQL query: (project in (ART_A, ART_B) AND issuetype = Feature AND "PI Target" = "PI 2025.Q3") ORDER BY priority DESC

Validate the query to ensure it returns the expected items. Saving the board settings immediately triggers the initial import.

To update the data set, click the "Resync" button next to a filter. This allows Kendis to pull the latest set of work items that match the defined ALM query.

The backlog view must be set to the appropriate level of work (e.g., Features for PI Planning).

Find the hierarchy selector dropdown (e.g., Portfolio Epic, Epic, or User Story) near the top right of the backlog list.

Select the level you want to prioritise. Epic (or Feature) is the standard selection for PI Planning.

Nested Stories: Ensure that the immediate child work items (e.g., Story or Task) are configured to be loaded when the parent Feature card is expanded.

When a Feature card is expanded, Kendis loads its connected Stories, categorising them as Planned, Unplanned Open, and Unplanned Done.

The list view allows for large-scale data manipulation through advanced grouping and column configuration.

Columns control data visibility, crucial for performance and focused analysis.

Click the “Columns” dropdown.

Select essential fields like Status, Children Count, Estimate (SP), and the WSJF component fields.

Grouping organises the list by shared attributes for hierarchical review and targeted analysis.

Click the "No Group" dropdown and select a field (e.g., Teams, Parent, PI Boards, Sprints, or Batches).

For a multi-level backlog management, click "+ Multi Group".

Define nested tiers of grouping (e.g., Group by Portfolio Epic, then by Teams) to provide a complete breakdown of work distribution across the hierarchy.

The Filters menu allows users to optimise the visible data set for focused sessions.

Click the "Filters" button (next to the search bar).

Apply criteria based on status, custom fields, or team assignment to isolate the items that require immediate attention.

Kendis enforces Weighted Shortest Job First (WSJF) as the primary prioritisation model.

Ensure the four WSJF component columns (User/Business Value, Time Criticality, RR/OE, Job Size) are visible. Enter numerical scores directly into the Feature card rows' cells.

The Job Size score must be greater than zero.

Click the "WSJF" column header.

The backlog instantly sorts in descending order, ranking features by their calculated economic priority.

WSJF Calculation

The Backlog Kanban view manages the Feature maturation process and enforces the Definition of Ready (DoR).

Switch View: Toggle the backlog display from "List" to Kanban.

WIP Limits: Within Board Settings, define columns (e.g., Analysis, Ready for PI) and apply WIP (Work in Progress) Limits to prevent bottlenecks.

Action: Drag and drop Features between columns. Only Features in the final "Ready" state should be considered eligible for the upcoming PI.

Transition to PI Planning

Navigate to the Program Boards option. Drag and drop the prioritised, ready Features from the Backlog onto the specific Program Increment (PI) column on the board.

Open the transferred Feature card and create child User Stories/Tasks. These items are automatically linked and synchronised to the correct Sprint/Iteration in the integrated ALM tool.

Data Export

Exporting the backlog provides documentation for stakeholders and external reporting.

Click the Download icon near the Settings.

Select either Export CSV or Export Excel.

The export file will contain data for all features currently visible in the lists, based on the applied filters, grouping, and selected columns.