A business analyst in organization Y is assigned to elicit requirements in a project within a defined timeline.
The business analyst has identified and invited key stakeholders to a requirements workshop.
However, the stakeholders are not giving clear and concise requirements; their opinions about requirements are changing and conflicting with each other in the meeting. In the end. the business analyst could not elicit and define the requirements and therefore adjourned the meeting.
Which tool or technique could have been used by business analyst to avoid this situation?
Requirements for a project have already been approved and finalized when a stakeholder approaches the project team with a change to one of their requirements. Which method of document control should the business analyst use to document changes in requirement(s) versioning?
A project team delivers a solution based on the approved requirements and is confident that it meets the defined acceptance criteria. What should the business analyst do to obtain signoff?
A new project is in the planning phase. The business owner believes that, since the timeline is aggressive, requirements elicitation should begin as soon as possible.
Which activity should the business analyst initiate before beginning requirements elicitation?
After analyzing a set of requirements documents, it is determined that the requirements are not yet ready for peer review. This was most likely caused by:
