Henry is the business analyst for the UUH Organization. Currently Henry is working on several work products as part of the requirements development process.
He may need to share these work products with the stakeholders.
Which of the following is not an example of a work product?
Meeting agendas and minutes are primarily administrative documents that facilitate communication and coordination during meetings, rather than being directly involved in documenting or analyzing requirements. While they may involve inputs from the business analyst and can contain information related to requirements discussions, they are not considered typical work products of the requirements development process like requirements documentation, interview questions and notes, and presentation slides.
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
Its correct that requirements documentation is an output and not an input for requirements development process. But, 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.
Ans: A B refers to Surveys
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.
all options could be considered work products in a broad sense, "C. Meeting agendas and minutes" is the least directly related to the core activities of requirements development and analysis compared to the other options provided.
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
the answer is correct, when you look at the definition of what a work product is as defined by BABOK
Interviews are a part of elicitation which is a work product. Incorrect answer is B
Sorry meant to say A
B seems to be the only option that is NOT relevant