User Tools

Site Tools


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

Both sides previous revisionPrevious revision
Next revision
Previous revision
what_is_the_mapping_between_features_and_pi_objectives [2021/04/23 09:46] – Removed want to know more hanswhat_is_the_mapping_between_features_and_pi_objectives [2021/08/17 12:50] (current) – Edited for readability and completeness hans
Line 12: Line 12:
   * 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)
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'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)
Line 36: Line 36:
  
   * 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
  
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/what_is_the_mapping_between_features_and_pi_objectives.1619196375.txt.gz · Last modified: 2021/04/23 09:46 by hans