mediumConceptScenarioMidSeniorLead
What goes in a BRD versus an FRD versus a user story, and how do you decide which to produce?
A BRD explains the business objective and sponsor decision, an FRD describes required system behavior, and a user story is a small testable slice with acceptance criteria. Choose the artifact by audience, governance need and delivery granularity.
5 min readUpdated 2026-08-15
Answer
Short answer
A BRD states why the business wants the change and what outcome is needed. An FRD states what the system must do. A user story is a small delivery slice with acceptance criteria. In agile teams, BRD/FRD intent often becomes product goals, epics and acceptance criteria rather than large documents.
Was this answer helpful?
Likely follow-ups
- Where do non-functional requirements live in your process, and who reviews them?
- How would you reconstruct traceability for an audit if all you have is a Jira backlog?
- A fixed-price supplier contract references an FRD. Does that change how you work in sprints?
- How do you keep a product goal from becoming a slogan nobody uses for prioritisation?
Related questions
- The business insists on a requirement that nobody can test — "the system must be intuitive". What do you write instead?mediumAlso on non-functional-requirements and requirements4 min
- Two stakeholders give you directly contradictory requirements. How do you resolve it?mediumAlso on requirements and traceability3 min
- Six months into the build, your requirements documents no longer describe the system. What do you do about it?mediumAlso on traceability6 min
- Explain batch and serial genealogy, how it supports a recall, and what statistical process control gives you that a threshold alarm does not.mediumAlso on traceability6 min