A BA artifact is valuable only if it helps someone understand, decide, build, test, operate, or govern. The goal is not maximum documentation; it is sufficient shared understanding for the risk and context.
Choose artifacts that reduce ambiguity, support decisions, and remain traceable through delivery.
Executives need outcomes, options, and risks; users need journeys and prototypes; engineers need behavior, rules, data, and quality constraints; QA needs observable acceptance conditions.
Traceability keeps every delivery detail connected to an intended business outcome.
A regulated service needs faster refunds with auditable approval controls.
Capture business outcome, policy constraints, roles, and scope boundary.
Model the refund process and decision rules.
Write stories, exception scenarios, and Gherkin acceptance criteria.
Trace policy rules to implementation stories and test evidence.
Different audiences receive the detail they need while one traceable chain connects policy to tested release behavior.
Open each answer, then practice saying it naturally in your own words.
Common examples include vision and scope, BRD/FRD/SRS, stories, use cases, acceptance criteria, models, meeting and decision records, and traceability. Choice depends on purpose and context.
A maintained work product that supports understanding or delivery.
Six qualities that support effective user stories.
Given–When–Then syntax for behavior examples.
Optional team-agreed criteria for work to enter delivery.
Answer all three questions. Score 2 out of 3 to pass this section and update your course progress.
Choose one answer for every question, then submit your quiz.