Determine how to conduct stakeholder communication.
Recommend the most appropriate communication channel/tool (e.g., reporting, presentation, etc.).
Demonstrate why communication is important for a business analyst between various teams (features, requirements, etc.).
Determine how to gather requirements.
Match tools to scenarios (e.g., user stories, use cases, etc.).
Identify the requirements gathering approach for a situation (e.g., conduct stakeholder interviews, surveys, workshops, lessons learned, etc.).
Explain a requirements traceability matrix/product backlog.
Demonstrate an understanding of product roadmaps.
Explain the application of a product roadmap.
Determine which components go to which releases.
Determine how project methodologies influence business analysis processes.
Determine the role of a business analyst in adaptive and/or predictive, plan-based approaches.
Validate requirements through product delivery.
Define acceptance criteria (the action of defining changes based on the situation).
Determine if a project/product is ready for delivery based on a requirements traceability matrix/product backlog.