CAPM Practice: Determine how to prepare and execute task management steps

External dependencies are a key sprint planning risk factor. If the team selects a story knowing the dependency won't be resolved until next sprint, the story is likely incomplete at sprint end. Best practice: resolve dependencies before sprint planning (through inter-team coordination), or if unavoidable, acknowledge the risk explicitly and plan for the possibility of carryover. The Scrum Master should actively work to resolve cross-team dependencies.

**Why not A:** Waiting for all dependencies to be fully resolved before selecting any related stories is overly conservative and may result in the team not having enough work for the sprint. Some dependency risk can be managed through contingency planning rather than total avoidance.

**Why not C:** Selecting the story and working on "everything except" the dependency often results in incomplete work that cannot meet the Definition of Done. If the dependent component is missing, the story likely cannot be demonstrated or delivered as a complete increment at sprint end.

**Why not D:** Pressuring another team to change their delivery schedule creates cross-team friction and is not a sustainable collaboration practice. Dependencies should be resolved through coordination and joint planning, not pressure tactics that undermine trust between teams.