Step 7: 📝 Create a Low-fidelity wireframe

[jdmedlock]

Objective

Establish a common understanding across the team of what information is in each screen and the actions that may be invoked from each screen.

How

• Using the features you added to the the Feature Planning template in step 4 identify the screens you’ll need and the information on each one.
• Map the actions users will be able to perform from each screen and the navigation from screen-to-screen
• Create a low-fidelity wireframe using a tool like [Figma](https://www.figma.com/) or even pencil and paper.

Resources

How To Wireframe A Website in 3 Easy Steps
Create a low fidelity wireframe (Chingu Handbook)

Member of Epic: #16

[d0uble0deven]

Here's a really easy tool to mock layouts, maybe too low fidelity but I find it very useful: https://excalidraw.com/

[digable1]

Ok. This brings up an underlying point: We need to determine what goes in each screen so we can lay it out.

1. What actions ara available from the screen
2. What form attributes go into the screen
3. What is persisted from modifications made to the attributes (affects the schema, which is a current task for definition - @Pavubrar)

We don't have complete user stories for the above - something I do ahead of next planning meeting, or we use the planning meeting to define.

[digable1]

Note: This is a duplicate of #18 - need to merge them into one task.

[d0uble0deven]

What application are we building? Did yall decided that in the kickoff meeting?

[digable1]

@d0uble0deven: Yes, we are doing the Menu Scheduler. There was strong consensus to leverage the requirements already given to us by Chingu - avoiding the extra time needed in filling these provided gaps. We only have 6 sprints, so time management was a compelling driver.