Differences

This shows you the differences between two versions of the page.

--- how_do_we_write_good_pi_objectives [2022/03/07 17:19] – Readability hans
+++ how_do_we_write_good_pi_objectives [2025/07/29 12:37] (current) – [Want to Know More?] hans
@@ Line 20: / Line 20: @@
   * Are the between 3 and 7 PI Objectives for the Team? In particular, more than 7 is too long a list to keep in your head.
   * Do PI Objectives have with verbs which helps to clearly articulate what’s being done?
-  * Are there PI Objectives related to base, production support, or other work that is remedial rather than adding new value? Most of the time we want PI Objectives aimed at items that new value.
+  * Are there PI Objectives related to base, production support, or other work that is remedial rather than adding new value? Most of the time we want PI Objectives aimed at items that add new value rather than simply documenting business-as-usual.
   * Are there PI Objectives related to the architectural runway, or to reduce technical debt? Again, in most cases these will help in delivering better faster, and cheaper, which is of interest to the business.
   * Are the objectives SMART?
     * Specific: The PI Objective should be clear about the outcome.
     * Measurable: how do we know whether the PI Objective as done or not done. The PI Objective should
-    * Achievable (if much is outside of the team’s control, make it a stretch objective)
+    * Achievable (if much is outside of the team’s control, make it a uncommitted objective)
     * Realistic (avoid only thinking about the happy path)
     * Time-based (will be done within the PI)
@@ Line 48: / Line 48: @@
 ====== What Tips and Tricks Do You Have for Writing Great PI Objectives? ======
-===== Remember Your Audience =====
+  * Remember Your Audience: The audience for PI Objectives is the Business Owners of the ART in the first instance and then all other stakeholders the the ART. This means we cannot assume that the audience will understand the technology or technical jargon. PI Objective are written in the language of the business.  In particular, be clear about intent; what will the usable outcome be? What will the organization will be able to do (or not do) as a result of the work within the PI?
+  * Relationship to Features:There is no a 1:1 relationship between Features and PI Objectives although often teams will write Objectives so they are reflected as a Feature. A single PI Objective could refer to a single Feature, or multiple Features. Some Features may not be covered by a PI Objective at all (e.g. KTLO type Features). And some PI Objectives may not be the result of a Feature (e.g. a really significant improvement item identified as a result of the retrospective.). See [[what_is_the_mapping_between_features_and_pi_objectives|What is the Mapping Between Features and PI Objectives?]]
-The audience for PI Objectives is the Business Owners of the ART in the first instance and then all other stakeholders the the ART. This means we cannot assume that the audience will understand the technology or technical jargon. PI Objective are written in the language of the business.
-In particular, be clear about intent; what will the usable outcome be? What will the organization will be able to do (or not do) as a result of the work within the PI?
-===== Relationship to Features =====
-There is no a 1:1 relationship between Features and PI Objectives although often teams will write Objectives so they are reflected as a Feature.
-A single PI Objective could refer to a single Feature, or multiple Features.
-Some Features may not be covered by a PI Objective at all (e.g. KTLO type Features).
-And some PI Objectives may not be the result of a Feature (e.g. a really significant improvement item identified as a result of the retrospective.)
 ===== Perhaps Start with a Template =====
@@ Line 68: / Line 55: @@
 To help teams develop great PI Objectives it sometimes is useful to use a template to think through the parts:
-BY <the timeframe, e.g. the end of PI 5>
+> BY <the timeframe, e.g. the end of PI 5>
-WE WILL <do something, start the statement with a verb (“enable”, etc.)>
+> WE WILL <do something, start the statement with a verb (“enable”, etc.)>
-SO THAT <something good happens, provides business benefit>
+> SO THAT <something good happens, provides business benefit>
-AS MEASURED BY <how we will know>
+> AS MEASURED BY <how we will know>
 ====== Want to Know More? ======
+  * [[how_do_we_improve_how_we_write_requirements_and_goals|How Do We Improve How We Write Requirements and Goals?]]
   * [[https://www.scaledagileframework.com/pi-objectives/|SAFe's View of PI Objectives]]
+  * [[what_is_the_mapping_between_features_and_pi_objectives|What is the Mapping Between Features and PI Objectives?]]
+  * [[how_do_we_assign_business_value_to_pi_objectives|How Do We Assign Business Value to PI Objectives?]]
+  * [[how_do_we_determine_if_an_pi_objective_is_committed_or_uncommitted|How do we determine if an PI Objective is Committed or Uncommitted?]]
 {{tag>Consultant SAFe FAQ PIObjectives}}