08-02-2022 11:47 AM - last edited on 09-22-2023 10:56 AM by akloepfer
Question Credit: Becca Speese
Comment your best guess below! Answers will be revealed in one week.
* This question is applicable to Platform 7.3.0 and may not be relevant to future releases
Solved! Go to Solution.
08-09-2022 11:40 AM
You were all right!
Gathering your client’s requirements and formatting needs at the start of the project are an important contribution to reporting success.
08-03-2022 02:04 AM
Fiction. Reporting requirements are one of the fist to gather and definitely before the start of the build.
08-03-2022 09:26 AM
Fiction. Requirement gathering should be done first.
08-03-2022 11:39 AM
Fiction. Sequence should be: Requirements > Design > Build > Test > Deploy.
08-04-2022 12:51 PM
Fiction. You'd want to have reporting requirements before your initial build.
08-04-2022 12:55 PM
Fiction. You should get the requirements before building. A lot of times, those reporting requirements can determine build elements
08-04-2022 02:24 PM
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.
08-04-2022 03:19 PM
Fiction. Requirements should be gathered in the initial stage, including reporting requirements. These requirements dictate the design and build.
08-05-2022 10:50 AM
Fiction: For all the reasons mentioned.
08-08-2022 12:51 PM
Fiction. Requirements are crucial before any build.
08-09-2022 08:22 AM
Fiction. Reporting Requirements are gathered in the Analyze Phase and are considered as part of Design.
08-09-2022 11:40 AM
You were all right!
Gathering your client’s requirements and formatting needs at the start of the project are an important contribution to reporting success.