This is a good question! Most user stories have some kind of dependency and if dependencies are not handled right, they lead to blockers. The PBI is a great tool for user stories and acceptance criteria. Good user stories must try to follow INVEST and more so if your organization is scaling in some form. Some of the dependencies can be categorized into Inter Team, Inter stories, inter products or inter releases or external dependencies, depending on your individual situation. Fortunately, Scrum has a built-in feature for dependency management. Weekly Scrum of Scrums to track dependencies, Kanban boards for visualization by using dependency threads in a PI planning session and PBI prioritization using MoSCOW. If the dependencies are more complex, we can try to structure the teams from feature-level than the component team level and try to consider sharing team members for those specific sprints in advance. Dependencies are a part of the functional flow and it is imperative to identify them strategically in a timely manner or it may lead to a delayed feedback loop creating to an almost like waterfall scenario!