CAPM Practice: Determine how project methodologies influence business analysis processes

Sprint planning is tactical — selecting backlog items for one iteration, defining the sprint goal. Requirements workshops are analytical — eliciting, exploring, and documenting requirements across a broader scope. Both require facilitation skills but serve different purposes.

**Why not A:** Sprint planning and requirements workshops serve different purposes and are not identical. Sprint planning focuses on selecting and decomposing backlog items for the upcoming sprint iteration, estimating effort, and creating a sprint goal. Requirements workshops are broader sessions aimed at eliciting, elaborating, and validating requirements from stakeholders. While both involve collaboration, their scope, participants, and outcomes differ significantly.

**Why not C:** Sprint planning is typically shorter and more focused than a requirements workshop, not longer or more formal. Sprint planning is a time-boxed ceremony (usually a few hours for a two-week sprint) with a specific focus on the immediate iteration. Requirements workshops can span multiple hours or even days and involve broader stakeholder participation with a wider scope of discovery and analysis.

**Why not D:** Business analysts can and do facilitate sprint planning sessions, particularly in organizations that integrate BA and agile practices. The BA brings valuable skills in clarifying requirements, resolving ambiguities, and ensuring the team has a shared understanding of backlog items. While the Scrum Master often leads the ceremony, the BA's facilitation skills are a valuable contribution to productive sprint planning discussions.