Tracking external vendor dependencies on Stories/Epics - how do you handle it?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
We're trying to figure out the best way to track external vendor dependencies that block our Stories or Epics in the scrum board.
A few approaches we've been considering:
- Marking the Story as Blocked with vendor ticket info in the description
- Creating additional "proxy" Stories assigned to a dummy vendor group
- Something else entirely?
Our key requirements:
- Vendor ticket reference visible to internal SN employees (vendor uses external tool)
- Traceable to a sprint and/or scrum release for planning purposes
- Filterable from list view so we can quickly see all vendor-blocked items at a glance
- Minimal copy-paste overhead between systems
Curious how others have solved this - we can't be the only team dealing with external vendors that block internal work. What's worked for you?
0 REPLIES 0
