Does anyone have experience with using the Dependency Feature on a large scale program on User Stories? Where there any negative implications with using this feature when stories were split or carried over? Was this hard to manage in Rally with a large number of dependencies?
- 1 person found this helpful
This question may be too broad for a useful answer. We have pretty large programs with several Scaled Agile Framework value streams and release trains and of course in a program that size you'll have dependencies between stories. I'm not sure what sort of "negative implication" you're concerned about- dependencies transfer reliably to split stories and the Release Tracking program board is pretty intelligent about providing warnings when a successor is scheduled into the same (or earlier) iteration and release as a predecessor. If there's something specific that you're after then feel free to elaborate but otherwise I'd suggest modeling a few use cases so that you can get comfortable with the functionality yourself. Hope that helps.
CA Agile Central Subscription Admins anyone used Dependencies on a large scale that can comment?