Requires the following solution to be installed:
- Key Result Enablement (7781ee48-4a6f-4c47-8d38-04efcb8b986d)
- Years, Quarters, Months, Weeks and Days (4fb0e9dd-40e7-4dd2-ba10-548b86ecebeb)
Can be extended with the following solutions
- SAFe OKR: Connection to Custom Period (b704c35d-899a-4a81-9b5a-4d361c48468f)
- SAFe OKR: Connection to Value Stream (983a667f-5d18-4b74-8afd-1b7e5097ffa3)
- SAFe OKR: Connection to Solution Train (569f02f0-7fa3-41f0-83d3-fa75f24e82a2)
- SAFe OKR: Connection to Agile Release Train (ART) (7d9c728b-90c4-4ed3-8285-a54acb4cda6b)
- SAFe OKR: Connection to Team (015e0dd5-126c-49f1-a607-5d9632e77cee)
- SAFe OKR: Connection to Product (f72cd41d-3cb2-474a-b0ee-6c66ad02cfd6)
-----------------------------------------------------------------------------------------------------------------------------------
Solution Overview
Objectives and Key Results (OKRs) is a collaborative framework for establishing clear goals and measurable outcomes. When used within SAFe, OKRs can help to support the Core Values of transparency and alignment between the Enterprise and Portfolio strategy and the work of the Agile Release Trains and Agile Teams to deliver on this strategy. Additionally, OKRs can be applied to measure organizational improvement activities, including the desired outcomes for the SAFe transformation.
The simplicity of OKRs goes a long way toward explaining their popularity. The Objective defines the business outcome you strive to achieve. The Key Results are the measurable success criteria used to track progress toward the objective. For each Objective, there are typically between two to five Key Results.
The application of OKRs within SAFe falls into three main use cases:
- Enhancing strategic alignment across a SAFe Portfolio
- Defining Business Outcomes for Portfolio Epics and Lean Business Cases
- Setting improvement goals for the SAFe transformation
The solution enables Objectives and Key Results for Portfolio and Portfolio Epics by default, while can be extended with additional solutions and enable connections to Value Streams, Solution Trains, Agile Release Trains, Teams and Products, so that you can define Objectives or Business Outcomes for each of them.
So now after the installing the solution you can create Objectives and define Key Results for them on any of the mentioned items view:
When creating an Objective, you’ll define what Portfolio, which Period and which entity it should be connected to if needed:
- For Periods – it can be Year, Quarter, Month or Period (if Custom Period Enablement solution is installed). The Objective will inherit Planned Start Date and Planned End Date from the connected Period.
- For entity types – Portfolio Epic (by default), Products, Value Streams, Solution Trains, Agile Release Trains (ARTs) or Teams, if enabled by the additional solutions.
Note: Please define only one Period for your Objectives, so later you could track their progress based on Period Planned Start/End Dates.
As soon as Objectives and Key Results are defined you can also connect Work Items, such as Capabilities (Epics), Features, User Stories and Bugs to it.
Work Items can be connected to more than one Objective.
Objective Hierarchy
As the Objectives can be defined on different organization levels, it's possible to have a hierarchy of objectives.
So let's say you cerated an Objective for a Portfolio, you can now create a child Objective for Portfolio Epics, or for Value Stream/Solution Train/ART/Team or a Product. This will allow to trace the Objectives connections.
You can also see the hierarchy of Objectives on Objective Hierarchy view:
Note: If connections to Value Stream/Solution Train/ART/Team or a Product is enabled, the filters on those views need to be adjusted to show Portfolio Objectives (Objectives which are created just within a Portfolio and not connected to any entity) correctly.
© Scaled Agile
------------
Version 1.0
Still have a question?
We're here to help! Just contact our friendly support team