Decomposing the reports and requirements
Epics, stories, or requirements need to be easy to read, understandable, and concise.
Epics are generally large stories which are too vague to implement for reasons such as complexity, having many unknowns, and high levels of risk or size. You will need to decompose epics or requirements into actionable and implementable stories and requirements.
Getting ready
Go back to your Requirements Traceability Matrix, and extract your numbering scheme. This is a good template to start gathering requirements, and ensuring that you are capturing the correct information.
How to do it...
The standard numbering scheme and standard business requirement format ensures that information is collected consistently and concisely ...
Get Business Intelligence Cookbook: A Project Lifecycle Approach Using Oracle Technology now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
