Differences

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

--- how_do_we_write_good_pi_objectives [2022/03/07 17:18] – created hans
+++ how_do_we_write_good_pi_objectives [2022/03/07 17:23] (current) – Readability hans
@@ Line 5: / Line 5: @@
 Program Increment (PI) Objectives are an output of the PI Planning event. PI Objectives summarize in business terms what each Team intends to deliver in the upcoming PI. They are therefore used to:
-  * Validate understanding of intent
+  * Validate understanding of intent: PI Objectives provides a quick validation of both the Business Owner’s ability to articulate desired outcomes and the Teams’ grasp of those desired outcomes.  In short, we give the teams the following challenge:
-  * Focus on outcomes rather than the process
-  * Summarize data into steerable information
-===== Validate Understanding of Intent =====
+> Can you deliver the essence of the value sought by implementing this set of features?
-PI Objectives provides a quick validation of both the Business Owner’s ability to articulate desired outcomes and the Teams’ grasp of those desired outcomes.  In short, we give the teams the following challenge:
+  * Focus on outcomes rather than the process: PI Objectives help the Team shift focus off the Feature language and onto the desired business outcomes. Is our goal to complete the listed Features, or is our goal to provide the outcomes desired by those Features? In other words, if we could provide the same value with half the amount of work, and without building all of the Features, would this be acceptable?
+  * Summarize data into steerable information: We expect teams will fully and transparently share the Features they intend to complete, and their progress against them. However given that no large group will reliably read every item in a list if that list exceeds 3-7 items it is also valuable to summarize the 3-7 key Objectives per Team (and the ART) and report on progress against those.
-**Can you deliver the essence of the value sought by implementing this set of features?**
-If a Team cannot do this in a clear way by the end of planning, are we comfortable investing to pursue these goals over the Program Increment?
-===== Focus on Outcomes Rather than the Process =====
-PI Objectives help the Team shift focus off the Feature language and onto the desired business outcomes.
-Is our goal to complete the listed Features, or is our goal to provide the outcomes desired by those Features? In other words, if we could provide the same value with half the amount of work, and without building all of the Features, would this be acceptable?
-===== Summarize Data into Steerable Information =====
-We expect teams will fully and transparently share the Features they intend to complete, and their progress against them. However given that no large group will reliably read every item in a list if that list exceeds 3-7 items it is also valuable to summarize the 3-7 key Objectives per Team (and the ART) and report on progress against those.
 ====== What are the Characteristics of Good PI Objectives? ======
@@ Line 63: / 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 83: / 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? ======
   * [[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?]]
 {{tag>Consultant SAFe FAQ PIObjectives}}