Exam CBAP topic 1 question 78 discussion

Meeting agendas and minutes are typically not categorized as work products because they are more focused on the logistics of meetings rather than the analysis itself

Meeting agenda and minutes are administrative document that document the discussions during the meetings. While they may be shared with stakeholders to provide transparency and updates on project activities, they are not direct outputs of the requirements development process and do not specifically relate to documenting or analyzing requirements. BABOK v3 defines work product as a document or collection of notes or diagrams used by the business analyst during the requirements development process. So, all of the other options can be used directly by BA to develop requirements. Although requirements documentation is an output of the requirements development process, it is still a work product as it encompasses the collection of documents, specifications, user stories, use cases, and other artifacts that the business analyst uses and develops throughout the requirements development process.

as below

C. Meeting agendas and minutes. Meeting agendas and minutes are artifacts related to the management of meetings and the documentation of discussions, decisions, and action items. While they may involve inputs from the business analyst and could contain information related to requirements discussions, they are not direct outputs of the requirements development process. Instead, they facilitate communication and coordination among stakeholders during meetings. Therefore, meeting agendas and minutes are not considered typical work products of the requirements development process. v3 - pg 445: deliverable: Any unique and verifiable work product or service that a party has agreed to deliver. pg 455: work product (business analysis): A document or collection of notes or diagrams used by the business analyst during the requirements development process.

Option 1 Babok v2 page 74 Requirements documentation would be a deliverable and not work product

Work product (business analysis): A document or collection of notes or diagrams used by the business analyst during the requirements development process.(page 456 babok3). Requirements documentation is not a document use during requirements development process. It's an output, It can't be an input. Answer is A

the answer is correct, when you look at the definition of what a work product is as defined by BABOK

Sorry meant to say A

Interviews are a part of elicitation which is a work product. Incorrect answer is B

Ans: A B refers to Surveys

B seems to be the only option that is NOT relevant