how_do_we_write_good_pi_objectives
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| how_do_we_write_good_pi_objectives [2022/03/07 17:23] – 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. | * 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? | * 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 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? | * Are the objectives SMART? | ||
| * Specific: The PI Objective should be clear about the outcome. | * 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 | * 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 | + | * Achievable (if much is outside of the team’s control, make it a uncommitted |
| * Realistic (avoid only thinking about the happy path) | * Realistic (avoid only thinking about the happy path) | ||
| * Time-based (will be done within the PI) | * Time-based (will be done within the PI) | ||
| Line 62: | Line 62: | ||
| ====== Want to Know More? ====== | ====== 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:// | * [[https:// | ||
| * [[what_is_the_mapping_between_features_and_pi_objectives|What is the Mapping Between Features and 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_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> | {{tag> | ||
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/how_do_we_write_good_pi_objectives.1646702608.txt.gz · Last modified: by hans