Fiction. Reporting requirements are one of the fist to gather and definitely before the start of the build.

Fiction. Requirement gathering should be done first. 

Fiction. Sequence should be: Requirements > Design > Build > Test > Deploy.

Fiction. You'd want to have reporting requirements before your initial build.

Fiction. You should get the requirements before building. A lot of times, those reporting requirements can determine build elements

Fiction - You should gather reporting requirements initially while scoping the project.

Fact - You should often re-confirm some of the more complex reporting requirements after the initial build, as the user can now better visualize what OneStream can deliver. Some things might be applicable to Quickview that were previously thought - or vice versa.

Fiction. Requirements should be gathered in the initial stage, including reporting requirements. These requirements dictate the design and build.

Fiction: For all the reasons mentioned.

Fiction.  Requirements are crucial before any build.

Fiction.  Reporting Requirements are gathered in the Analyze Phase and are considered as part of Design.