HKSM

After the Scrum Team commits to a Sprint's User Stories, they identify and record all dependencies, including people availability and technical constraints. Properly documenting these links guides the sequence of tasks needed to build the Sprint Deliverables. Dependencies make visible how work items relate and interact within the team and across other Scrum Teams.

Key Points

• Performed right after selecting User Stories for the Sprint and revisited throughout the Sprint.
• Covers people/resource availability, technical or integration needs, internal vs. external, and cross-team links.
• Document using tools like dependency boards, backlog links, or task relationships to drive sequencing.
• Helps expose risks and blockers early, coordinate handoffs, and plan realistic Sprint execution.

Example

During Sprint Planning, a team selects a checkout story. They note dependencies on the security team to enable tokenization and on DevOps to provide test certificates. By documenting these, they schedule tasks so environment setup and security changes occur before integration and testing, and they sync with the other teams' timelines.

PMP Example Question

After choosing User Stories for a Sprint, what should a Scrum Team do to create a workable plan for producing the Sprint Deliverables?

1. Estimate velocity by averaging the last three Sprints.
2. Identify and document people and technical dependencies, then sequence tasks accordingly.
3. Split every User Story into equal-sized tasks for balanced workload.
4. Increase WIP limits to reduce the impact of waiting times.

Correct Answer: B — Identify and document dependencies to sequence work

Explanation: Recognizing and recording dependencies after story selection enables proper task ordering and coordination, ensuring the Sprint plan is feasible.