Differences

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

--- why_do_we_assign_business_values_to_pi_objectives [2018/05/15 13:38] – [Why Do We Assign Business Values to PI Objectives?] hpsamios
+++ why_do_we_assign_business_values_to_pi_objectives [2020/12/16 11:03] (current) – ↷ Links adapted because of a move operation hans
@@ Line 1: / Line 1: @@
 ====== Why Do We Assign Business Values to PI Objectives? ======
-When people start with SAFe there is a lot of confusion around the need to assign a Business Value to the PI Objective. The thinking goes "we already understand the business value because we have the features - why not just use that?" In many ways this is the same kind of thinking process as "why do we establish sprint goals when we have users stories?" The problem with this type of thinking is that if you are not careful features and stories become a way of specifying fixed scope, do not allow learning as we go along, and set us up for blame game when things don't quite work out as expected (Business: "But the features says it has to do this!"; Team: "We thought it meant that and this is how we got there.") To rectify this, we treat the features or story as a "wish" and the PI Objectives (and sprint goals) become a feedback loop to that the team provides to ensure there is common understanding. (See What is the purpose of sprint or interaction goals? for more information)
+When people start with SAFe there is a lot of confusion around the need to assign a Business Value to the PI Objective. The thinking goes "we already understand the business value because we have the features - why not just use that?" In many ways this is the same kind of thinking process as "why do we establish sprint goals when we have users stories?" The problem with this type of thinking is that if you are not careful features and stories become a way of specifying fixed scope, do not allow learning as we go along, and set us up for blame game when things don't quite work out as expected (Business: "But the features says it has to do this!"; Team: "We thought it meant that and this is how we got there.") To rectify this, we treat the features or story as a "wish" and the PI Objectives (and sprint goals) become a feedback loop to that the team provides to ensure there is common understanding. (See [[what_is_the_purpose_of_iteration_or_sprint_goals|What is the Purpose of Sprint or Iteration Goals?]] for more information)
 Having established the PI Objectives, we need to close the loop on communication, and we do this by having the business owner review the PI Objective, discuss their understanding of the PI Objective with the team, and assign a Business Value to that PI Objective based on that understanding. This process creates a “handshake” between the business and the team, with the PI Objectives in the team’s own words and the Business Value is the agreement from the business that the Plan makes sense to them.
@@ Line 10: / Line 10: @@
   - The commitment to deliver value is based on the PI Objectives. We can therefore use the Business Value to understand a team's ability to make and meet their commitments. The more a team is able to make and meet their commitments, the more likely stakeholders will trust the team, and so improve how they (team and stakeholders) collaborate over time. The Business Value can be used to create a metric which shows this ability.
->> Why assign business value? To enable local decision making and to understand whether we are making an meeting commitments.
+>> In summary, "Why do we assign a Business Value?" To enable local decision making and to understand whether we are making and meeting commitments.
 {{tag>Consultant Tools PIPlanning Program PIObjectives SAFe FAQ}}