The Kendis Risk Register is a central, dynamic tool designed for the proactive identification, tracking, mitigation, and analysis of organizational risks across one or multiple Program, Solution, or Collection Boards. It ensures visibility and facilitates a standardized approach to risk management, often using the R.O.A.M. (Resolved, Owned, Accepted, Mitigated) framework as the basis for Status management. The Risk Status is fully configurable by an Admin via the Risk Workflow, allowing organizations to align risk management to their specific process needs and compliance requirements.
Key Benefits of the Risk Register
Feature | Benefit and Impact |
Centralized Visibility | Provides a single, unified view of all risks, statuses, owners, and impacts from all linked Program/Solution Boards or even across multiple Boards. |
Automated Scoring | Calculates the Risk Level (e.g., High, Medium, Low) automatically based on the selected Risk Matrix and the user-defined Probability and Impact fields. |
Contextual Linking | Allows direct linking of a risk to the specific Features or Stories it impacts, ensuring teams understand the context and scope of mitigation efforts. |
Reporting Integration | Risks linked to specific sprints and teams are automatically surfaced in Sprint Reports and Scrum of Scrums (SoS) for real-time awareness during execution. |
Data-Driven Prioritization | The Analytics view provides visual charts (Risk Matrix, Risk Level Pie Chart) enabling quick identification and prioritization of the most severe or overdue risks. |
R.O.A.M. & Workflow | Supports the R.O.A.M. process by allowing flexible Status updates and tracking of mitigation actions and target resolution dates. |
Detailed Navigation and How-To Guide
The Risk Register can be accessed either from the main board view or via the dedicated Risk Register option on the left-hand navigation sidebar.
A. Accessing the Risk Register
From the Program Board: Navigate to your relevant Program Board.
Locate the "More" dropdown button in the top right corner of the board (next to the Board Settings).
Click "More", and from the dropdown menu, select the "Risks Register" icon (an orange square with a white hazard sign).
B. Creating and Editing a Risk
Risks are created and managed via a detailed modal pop-up, which automatically calculates severity based on your inputs.
1. Initial Risk Register Setup (If No Register Exists)
The first time you access the Risk Register for a board, you will be prompted to either link an existing register or create a new one.
Option 1: Link Existing Risk Register: Select the name of an existing Risk Register from the dropdown menu and click "Link Risk Register". This will connect the current Program Board to the selected register.
Option 2: Create Risk Register: Click the "Create Risk Register" button to start a new register.
2. Creating a New Risk Register
If you choose to create a new register, a setup modal will appear requiring the following mandatory administrative details:
Field Name | Description |
Prefix | A unique alphanumeric key (e.g., RRB, RSK) used to generate unique identifiers for risks (e.g., RRB-1). |
Register Name | A descriptive name for the register (e.g., WebStore Q2 2025 Risks). |
Risk Workflow | Select the desired status flow. This defines the available Status options for all risks in this register. |
Risk Matrix | Select the methodology for calculating risk level (Risk Matrix 1 (3 levels) or Risk Matrix 2 (5 levels)). Note: This choice is permanent and cannot be changed later. |
Custom Field Layout: To manage the fields that appear in the risk modal, click the eye icon next to "Custom Field Layout Association with Item Type". This opens a new tab where a Super Admin can add, reorder, or remove fields for this specific register.
Once all fields are complete, click "Save". The Risk Register list view will open.
3. Creating a New Risk Item (Initial Details)
When adding a new risk, the initial modal focuses on mandatory details. Interactive features like linking or conversations become available only after the risk is created.
In the main Risk Register view (after setup), click the green "+ Add Risk" button located in the top right corner.
A detailed modal view, titled "Create Risk," will open. Fill out the required core details (Title, Probability, Impact, Description, Mitigation Actions, Dates, Status, and Responsible). The Linked Items and Conversations/History tabs are not visible at this initial stage.
Click the green "Save" button. The risk is now created and assigned a unique Risk # (e.g., RRB#-2).
4. Editing an Existing Risk (Adding Links and Conversations)
Once the risk is saved, all collaboration and linking features become available by editing the item.
In the Risk Register list view, locate the risk you wish to modify.
Click the Risk # (a blue link, e.g., RRB#-2) at the start of the row. This opens the detailed modal view, now showing the full set of tabs and options.
5. Completing the Risk Details Fields (In Edit Mode)
The modal requires comprehensive inputs to properly define and score the risk:
Field Name | Description & Visual Cues |
Risk Title | A concise name for the risk. |
Probability & Impact | Use the two dropdown menus to define the likelihood and potential severity. The Risk Level is calculated immediately and displayed in a colored pill (e.g., MEDIUM in orange) based on the intersecting values in the Risk Matrix. |
Risk Description | Detailed explanation of the threat. |
Mitigation Actions | The plan required to address and reduce the risk. |
Raised On | Date the risk was identified. |
Target Resolution Date | The targeted deadline for resolving or mitigating the risk. |
Status | Select the risk status (e.g., Open, Accepted, Mitigated, Resolved). This often corresponds to the R.O.A.M. (Resolved, Owned, Accepted, Mitigated) framework. Note: The available statuses are determined by the Risk Workflow configured by a Super Admin. |
Responsible | Assign the user responsible for owning and driving the mitigation plan. |
Teams Impacted | Select the specific teams affected by this risk. |
Sprints Impacted | Select the sprints that are expected to encounter this risk. |
Linked Program Boards/Collections | Use these dropdowns to link the risk to other relevant boards or collections for visibility across organizational levels. |
6. Linking Risk to Work Items (Features/Stories)
This action is only available after the risk is initially saved. Scroll down within the risk modal to the Linked Items section:
Linking a risk to a Feature or Story is crucial for traceability and scoping. It ensures that teams clearly understand which specific pieces of work will be impacted if the risk materializes, allowing for better prioritization and planning of mitigation work.
Click the blue "+ Add Items" link.
A search modal will appear listing available Features and Stories from the board(s) linked to this Risk Register.
Select the check-box next to each work item the risk affects.
Linked items appear as blue links with their status (e.g., FEA-3 | Backend structure for digital bookstore | In Progress).
7. Managing External Links
This action is only available after the risk is initially saved. Below the Linked Items section, you can add links to external resources or ALM items:
Click the "+ External Link" button.
Enter the URL and a descriptive title for the link (e.g., a link to a Jira ticket or an external mitigation document).
8. Conversations and Collaboration
This section is only visible after the risk is initially saved. The bottom of the risk modal includes the Conversation, History, and Watched By sections:
Conversations: Use this field to engage other team members, provide updates, or discuss the risk. You can use the @ symbol to tag users, and they will receive a notification.
History: This tab provides an audit log of all changes made to the risk item, including status updates, date changes, and field modifications.
Notify Watchers: Use the "Notify Watchers" checkbox at the top of the modal (next to the Save button) to send an email notification about the changes or updates to users who are watching this specific risk item.
9. Saving and deleting
Click the green "Save" button at the top right of the modal to apply changes.
To delete, click the "Delete Risk" button in the bottom left of the modal.
C. Customizing the Risk Register List View
The main list view (the Risk Register) can be customized to focus on the most critical information and adjust prioritization.
Unlinking the Board: If the Risk Register is associated with only one board, you can remove the link by clicking the "Unlink" button located next to the Register title. This keeps the register but detaches it from the current board's context.
Hiding/Displaying Columns: Click the "Columns" button in the top right of the register. A dropdown appears allowing you to select or deselect standard and custom fields (e.g., Risk #, Risk Title, Linked Items, Risk Level). Click "Done" to apply.
Filtering: Use the dropdown filters at the top of the list (e.g., Risk Level, Status, Responsible, Teams) to refine the list view. Click the blue "Update Filter" button to apply your selections.
Sorting: Click on the title of any column (e.g., Risk Level, Impact, Raised Date) to sort the entire list view by that criteria in ascending or descending order. This allows users to adjust the priority of risks visually based on the desired metric.
Searching: Use the "Search" field in the top right corner to quickly locate risks by title or keyword.
Analyzing Risks with Analytics
The Analytics tab provides a visual, graphical overview of your risk landscape, helping you prioritize and identify trends.
Accessing Analytics: Click the "Analytics" button located next to the "+ Add Risk" button in the top right corner of the Risk Register screen.
Key Visual Components: The charts are interactive and the dashboard typically displays four main graphs:
Risk Matrix: This is the core visualization, a heat map that plots Probability (Y-axis) against Impact (X-axis). The cells are colored (e.g., green, amber, red) corresponding to the calculated Risk Level (Low, Medium, High, Severe).
Probability ↓ / Impact → | Low | Medium | High |
Low | Low | Low | Medium |
Medium | Low | Medium | High |
High | Medium | High | High |
|
|
|
|
Responsible-wise Risk Levels: A horizontal bar chart showing the distribution of risks by severity for each responsible individual.
Risk Level Pie Chart: A circular graph showing the percentage breakdown of all risks by their calculated Risk Level (e.g., 37.5% High, 25% Medium, 37.5% Low).
Risk Count by Responsible (Pie Chart): A circular graph showing the distribution of risks across assigned users, including those "Not assigned".
Drill-Down Capability: Clicking on a specific segment (e.g., a colored square on the Risk Matrix or a slice in the pie chart) will open a filtered modal view, showing only the list of risks corresponding to that segment (e.g., all risks with 'High' impact and 'Very High' probability).
Contextual and Administrative Information
ALM Integration: Kendis supports integrating the Risk Register with external Application Lifecycle Management (ALM) tools, such as Azure DevOps (ADO), allowing you to manage and track risks that originate in or impact your work items stored in the external system. You can learn more about this connection here: Connecting and Managing Risks from Azure DevOps in Kendis.
Risk Matrix Configuration: Kendis offers two default Risk Matrices. The specific Risk Matrix is chosen by the Admin when the Risk Register is first created and cannot be changed afterward.
Risk Matrix 1 (3 Levels): Supports Low, Medium, and High risk levels.
Risk Matrix 2 (5 Levels): Supports Very Low, Low, Medium, High, and Severe risk levels.
Risk Workflow: The available Status options (e.g., Open, Accepted, Mitigated, Resolved) in the Risk modal are defined in the Risk Workflow. This workflow can be edited or customized by a Super Admin in Global Settings.
Linked Components: A single Risk Register can track items from multiple Program Boards simultaneously, promoting alignment across trains. Conversely, a single risk item can be linked to multiple Features and Stories (Linked Items), creating explicit transparency about the impact. Critically, when a risk is linked to specific Teams Impacted and Sprints Impacted, this information is surfaced in the PI Sprint Reports and during the Scrum of Scrums (SoS) to ensure operational awareness of potential blockers.
Custom Fields: Super Admins can Enhance the Risk Register with Custom Fields to capture additional, organization-specific data points beyond the default fields.