PL-02
Cross-Team Pre-Release Blockage
Pipeline
Default severity: medium
ProcessOutputRisk
What it detects
The configured minimum number of teams simultaneously have issues stuck in the same pre-release stage beyond the configured threshold — shared downstream constraint.
Detection formula
IF COUNT(teams WITH any_issue.stuck_in_pre_release > config.pipeline.warning_days) >= config.pipeline.cross_team_min_count // default: 3 THEN FLAG cross_team_pipeline_blockage Identify common stage and likely shared constraintExamples in practice
- A team shows the configured minimum number of teams simultaneously have issues stuck in the same pre-release stage beyond the configured threshold while warning days is set to 3.
- Example signal: The configured minimum number of teams simultaneously have issues stuck in the same pre-release stage beyond the configured threshold — shared downstream constraint.
Suggested response
Unblock pre-release and carry-over items with clear ownership and planning labels.
Coaching playbook
Symptom
The configured minimum number of teams simultaneously have issues stuck in the same pre-release stage beyond the configured threshold — shared downstream constraint.
Why it matters
When "Cross-Team Pre-Release Blockage" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.
What you can achieve
Unblock pre-release and carry-over items with clear ownership and planning labels.
Facilitation questions
- What system change would stop "Cross-Team Pre-Release Blockage" from firing again?
- What do the cited issues have in common — same root cause or same workaround?
- Who owns the two-week experiment and how will we verify on the next import?
Run this rule against your own tracker data with Flow Analyzer.