Fact or Fiction? It is important to gather reporting requirements after the initial build stage...

Forum|Forum|4 years ago
August 2, 2022
11 replies
0 views

It is important to gather reporting requirements after the initial build stage of the project.

Question Credit: Becca Speese

Is this statement fact or fiction?

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

Fact or Fiction Trivia

Best answer by agoralewski

You were all right!

FICTION!

Gathering your client’s requirements and formatting needs at the start of the project are an important contribution to reporting success.

M

MarcR

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

C

CarmenBrower

Fiction. Requirement gathering should be done first.

L

lindseygerding

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

K

khlkkjgiliu

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

M

Mike_Sabourin

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

A

AJorgensen

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.

J

JenH

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

A

AndyR

Fiction: For all the reasons mentioned.

M

mtarrence

Fiction. Requirements are crucial before any build.

W

wtrendel

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