The relationship between a Defect and an Objective determines the prioritization for the auto-scheduler in terms of the order of tasks created to fix the defect.
Prioritization is determined by the capability's numeric business weight, considering all business weights to which the entity belongs.
- Relationship is Optional: A defect may or may not be linked to an Objective.
Types of Relationships:
There are two types of relationships:
- Breaks:
- Critical Relationship: The detected defect breaks critically important functions/capabilities of the stream. For example, if a defect affects the ability to log in to the application, the relationship type for Defect to Objective would be "Breaks."
- Priority Calculation Logic: Adds +1 to the existing business weight of the Objective.
- Degrade:
- Minor Relationship: The detected defect affects the stream's functionality/capabilities, but these functions/capabilities are rarely used or seen; hence, fixing the defect is not critically necessary.
- Priority Calculation Logic: Subtracts -1 from the existing business weight of the Objective.
Impact of Changing Business Weights:
Changes in business weights affect the auto-scheduler's determination of the importance and order of task execution for fixing the defect.
Comments
0 comments
Article is closed for comments.