What is the correct sequence of steps to understand a problem while designing the Redwood Reference Application?
A.
Gather feedback from product management and other stakeholders, write user goals, describe the shape of data of your use case, understand the problem, and iterate until you achieve clarity
B.
Describe the shape of data of your use case, gather feedback from product management and other stakeholders, write user goals, understand the problem, and iterate until you achieve clarity
C.
Understand the problem, write user goals, describe the shape of data of your use case, gather feedback from product management and other stakeholders, and iterate until you achieve clarity
D.
Write user goals, describe the shape of data of your use case, understand the problem, gather feedback from product management and other stakeholders, and iterate until you achieve clarity
Redwood’s design process starts with understanding the problem (C), followed by defining goals, data, feedback, and iteration. Other sequences (A, B, D) misalign with this logical flow.
[References: Oracle Redwood Pattern Book – "Design Process" (https://www.oracle.com/redwood/)., ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit