Wireframe Prototypes #26
Description
Multiple studios have been working on prototypes to try our different technical solutions and workflows. Now that @oavramenko has collected a good chunk of user stories, it would be good to start applying those to prototypes to create a common wireframe to use to plan work and our spec doc. First we should have those interested present their wireframes/prototypes and explain how they match the user stories. Next, we should pick one and make any changes needed to it based on a feedback cycle. This is part of the development process outlined here:
https://github.com/AcademySoftwareFoundation/dna/wiki/Proposed-Project-Planning-Cycle
User-stories: https://github.com/AcademySoftwareFoundation/dna/wiki/User-Stories
Steps:
- Check user stories and compare to current prototypes
- Update prototypes to cover user stories
- Prepare presentation to the group and gather any internal feedback
- Pick a single prototype to act as a wireframe
- Update this prototype to take the best aspects of all those presented
- Continue feedback cycle for a few weeks to ensure best wireframe for the current stage.
Note: Wireframes act as a guide. As we build and alpha product, ideas and designs will shift. This is to give us a general direction and allow for the creation of tickets and scoping of work.
Acceptance criteria:
A single wireframe to act as a guide to allow creation of spec doc and tickets