detect-dependency-risk

Sprint dependency risks are identified by analyzing issue links across sprint tickets to surface cross-team and external blockers early. This process classifies risks by blocker status, days remaining, and story points at stake to prevent delivery derailment.

Cross-team dependency risk analysis is the process of detecting blockers by examining linked issues across sprint tickets that cross team boundaries. It helps teams identify cascading dependencies and mitigate delivery impacts before sprint deadlines are missed.

Scanning sprint tickets for dependency risks requires providing sprint_tickets and sprint_context data to generate a dependency risk report. This outputs a structured analysis of linked issues, blocker status, and mitigation suggestions for mid-sprint reviews.

Sprint dependency risk detection can be applied during PI planning and cross-team reviews to surface blockers early. It accepts optional team_name parameters and outputs a concise executive summary alongside structured dependency risks.

Agile sprint dependency risks are ranked by analyzing blocker status, days remaining in the sprint, story points at stake, and whether dependencies cross team boundaries. This classification helps prioritize mitigation actions for critical blockers.

To generate a dependency risk report, you need to provide sprint_tickets and sprint_context data containing linked_issues information. An optional team_name can be included to focus on specific cross-team dependencies during the analysis.