CBAP · Question #267
You are the business analyst for your organization. On your current project you'll be using the change-driven approach for defining requirements and gathering feedback. Which of the following…
The correct answer is D. The change-driven approach favors defining requirements through team interaction. The change-driven approach, associated with agile methodologies, centers on continuous team interaction and collaboration to define and refine requirements iteratively rather than specifying them fully upfront.
Question
You are the business analyst for your organization. On your current project you'll be using the change-driven approach for defining requirements and gathering feedback. Which of the following statements best describes the change-driven approach?
Options
- AThe change-driven approach favors defining requirements through experimentation.
- BThe change-driven approach does not define the requirements until after a solution for the
- CThe change-driven approach favors defining requirements standardized templates.
- DThe change-driven approach favors defining requirements through team interaction.
How the community answered
(45 responses)- A2% (1)
- B11% (5)
- C7% (3)
- D80% (36)
Why each option
The change-driven approach, associated with agile methodologies, centers on continuous team interaction and collaboration to define and refine requirements iteratively rather than specifying them fully upfront.
Experimentation as a primary vehicle for defining requirements is more characteristic of lean startup or hypothesis-driven development, not the defining trait of the change-driven approach.
Deferring all requirements definition until after a solution is built describes reverse engineering or a post-hoc documentation approach, which is not the change-driven methodology.
Relying on standardized templates is a hallmark of plan-driven or waterfall approaches that emphasize upfront documentation and formal processes.
Agile and change-driven methods prioritize individuals and interactions, with requirements emerging through ongoing dialogue among cross-functional team members, product owners, and stakeholders. This iterative collaboration allows requirements to evolve as the team gains understanding through working increments and feedback.
Concept tested: Change-driven agile approach to requirements definition
Source: https://www.pmi.org/learning/library/agile-business-analysis-requirements-6025
Topics
Community Discussion
No community discussion yet for this question.