Which statement best describes the business analyst's role in a predictive (plan-driven/waterfall) project life cycle?
The business analyst postpones writing formal requirements until prototypes are delivered so stakeholders can react to tangible models.
The business analyst focuses mainly on backlog grooming and writing brief user stories instead of producing comprehensive requirement documents.
The business analyst gathers and documents detailed requirements at the start of the project, establishing a baseline; later changes are handled through formal change control.
The business analyst works iteratively with the team to refine requirements every sprint, welcoming frequent change without formal approval.
In predictive life cycles, a business analyst performs extensive requirements elicitation and documentation early in the project. Once the requirements baseline is approved, further changes must pass through a formal change-control process. This up-front definition supports the linear sequencing of work and protects the project's scope, schedule, and cost baselines. By contrast, adaptive or agile approaches expect the business analyst to refine requirements iteratively, write lightweight user stories, and embrace ongoing change throughout development.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are predictive methodologies in project management?
Open an interactive chat with Bash
What is the role of a business analyst in a predictive methodology?
Open an interactive chat with Bash
Why are changes minimized during the execution phase in predictive methodologies?
Open an interactive chat with Bash
CAPM
Business Analysis Frameworks
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
Project Management Package Join Premium for Full Access