Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace: • what_are_the_steps_to_establish_a_development_manager • how_do_we_use_story_point_estimates_to_forecast • why_do_we_assign_business_values_to_pi_objectives • what_is_session_based_testing • what_is_the_mapping_between_features_and_pi_objectives
what_is_the_mapping_between_features_and_pi_objectives

Differences

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

Link to this comparison view

Next revision		Previous revision
what_is_the_mapping_between_features_and_pi_objectives [2021/04/23 09:31] – created hanswhat_is_the_mapping_between_features_and_pi_objectives [2021/08/17 12:50] (current) – Edited for readability and completeness hans
Line 3: Line 3:
 It often seems that when we go through a PI Planning event, that there is confusion as a result of developing PI Objectives and, in particular, how resultant PI Objectives relate to incoming Features. There are a number of standard patterns that you will see:  It often seems that when we go through a PI Planning event, that there is confusion as a result of developing PI Objectives and, in particular, how resultant PI Objectives relate to incoming Features. There are a number of standard patterns that you will see: 
  
-====== One Features to One PI Objective (Normal) ======+===== One Features to One PI Objective (Normal) =====
  
 {{::feature_piobjective_one_to_one.png?400|}} {{::feature_piobjective_one_to_one.png?400|}}
Line 9: Line 9:
 Characteristics: Characteristics:
  
-✅ A PI Objective is directly the result of a Feature +  * A PI Objective is directly the result of a Feature 
-✅ Feature complete means associated PI Objective is complete +  * Feature complete means associated PI Objective is complete 
-✅ PI Objective wording is strongly related to the Feature Business Hypothesis and Acceptance Criteria +  * PI Objective wording is strongly related to the Feature Business Hypothesis and Acceptance Criteria 
-✅ It’s OK to achieve the PI Objective with completing the related Feature, especially if it means a better way of addressing the business need +  * It’s OK to achieve the PI Objective **without** completing the related Feature, especially if it means a better way of addressing the business need 
-✅ Recommend: PI Objective lists the Feature ID in the text e.g. (ID 2) +  * Recommend: PI Objective lists the Feature ID in the text e.g. (ID 2) 
-✅ Recommend: Feature description lists the PI Objective in the text e.g. (PI Objective 1)+  * Recommend: Feature description lists the PI Objective in the text e.g. (PI Objective 1)
  
-====== Many Features to One PI Objective (Normal) ======+===== Many Features to One PI Objective (Normal) =====
  
 {{::feature_piobjective_many_to_one.png?400|}} {{::feature_piobjective_many_to_one.png?400|}}
Line 22: Line 22:
 Characteristics: Characteristics:
  
-✅ A PI Objective is the result of a multiple Feature +  * A PI Objective is the result of a multiple Features 
-✅ All Features expected to be complete for the PI Objective to be complete +  * All Features are expected to be complete for the PI Objective to be complete 
-✅ PI Objective wording is a summary of the related to the Features Business Hypothesis and Acceptance Criteria +  * PI Objective wording is a summary of the related to the Feature's Business Hypothesis and Acceptance Criteria 
-✅ It’s OK to achieve the PI Objective with completing the related Features, especially if it means a better way of addressing the business need +  * It’s OK to achieve the PI Objective **without** completing the related Features, especially if it means a better way of addressing the business need 
-✅ Recommend: PI Objective lists the Feature ID in the text e.g. (ID 1, 3, N-1) +  * Recommend: PI Objective lists the Feature ID in the text e.g. (ID 1, 3, N-1) 
-✅ Recommend: Feature description lists the PI Objective in the text e.g. (PI Objective 2)+  * Recommend: Feature description lists the PI Objective in the text e.g. (PI Objective 2)
  
-====== Feature Doesn't Map to PI Objective (Normal) ======+===== Feature Doesn't Map to PI Objective (Normal) =====
  
 {{::feature_piobjective_no_to_one.png?400|}} {{::feature_piobjective_no_to_one.png?400|}}
Line 35: Line 35:
 Characteristics: Characteristics:
  
-✅ Some Features won’t be part of the PI Objectives for the Team +  * Some Features won’t be part of the PI Objectives for the Team 
-✅ Features are still expected to be completed, but this Feature is not differentiating  +  * Features are still expected to be completed, but the Feature is not differentiating in terms of the overall work of the Team 
-✅ Situation is normal because Features often represent KTLO, support, and other activities+  * Situation is normal because Features often represent KTLO, support, and other activities
  
-====== PI Objective is not the Result of a Feature (Normal) ======+===== PI Objective is not the Result of a Feature (Normal) =====
  
 {{::feature_piobjective_just_objective.png?400|}} {{::feature_piobjective_just_objective.png?400|}}
Line 45: Line 45:
 Characteristics: Characteristics:
  
-✅ Some PI Objectives won’t be the result of a Feature for the Team +  * Some PI Objectives won’t be the result of a Feature for the Team 
-✅ PI Objective is still expected to be completed  +  * PI Objective wording helps people not only understand what is to be done (the "what") but also why it is important (the "so what") 
-✅ Situation is normal because some PI Objectives are internal to the Team such as Team improvement items+  * PI Objective is still expected to be completed  
 +  * Situation is normal because some PI Objectives are internal to the Team such as Team improvement items
  
-====== Feature Results in Multiple PI Objectives (Rare) ======+===== Feature Results in Multiple PI Objectives (Rare) =====
  
 {{::feature_piobjective_one_to_many.png?400|}} {{::feature_piobjective_one_to_many.png?400|}}
Line 55: Line 56:
 Characteristics: Characteristics:
  
-✅ A single Feature results in multiple PI Objectives +  * A single Feature results in multiple PI Objectives 
-✅ Feature complete means associated PI Objectives are complete +  * Feature complete means associated PI Objectives are complete 
-✅ PI Objective wording is typically related to parts of the Feature Acceptance Criteria +  * PI Objective wording is typically related to parts of the Feature Acceptance Criteria 
-✅ Situation is rare because usual practice is to split the Feature and do 1 to 1 relationship between Feature and PI Objective +  * Situation is rare because usual practice is to split the Feature and do 1 to 1 relationship between Feature and PI Objective 
-✅ Recommend: PI Objective lists the Feature ID in the text e.g. (ID 1) +  * Recommend: PI Objective lists the Feature ID in the text e.g. (ID 1) 
-✅ Recommend: Feature description lists the PI Objective in the text e.g. (PI Objective 2, PI Objective 3, PI Objective 4) +  * Recommend: Feature description lists the PI Objective in the text e.g. (PI Objective 2, PI Objective 3, PI Objective 4)
- +
- +
-====== Want to Know More? ====== +
- +
-  * [[how_do_we_assign_business_value_to_pi_objectives|How Do We Assign Business Value to PI Objectives?]] +
-  * [[why_do_we_assign_business_values_to_pi_objectives|Why Do We Assign Business Values to PI Objectives?]] +
-  * [[what_do_we_mean_by_smart_goals_or_objectives|What Do We Mean By SMART Goals or Objectives?]]+
  
 {{tag>FAQ DIY Agile Coaching Goals Objectives Features SAFe}} {{tag>FAQ DIY Agile Coaching Goals Objectives Features SAFe}}
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/what_is_the_mapping_between_features_and_pi_objectives.1619195499.txt.gz · Last modified: 2021/04/23 09:31 by hans