[BB-3754] Sprints v2 UI/UX
Story
"As OpenCraft, we want to plan the rework of the Sprints UI/UX."
Full description
This is a follow-up to the discovery from #1 (closed). The UI/UX discovery is needed to commence working on the development of the project.
Completion criteria
- Evaluate the brief, help to refine the scope/requirements, define a suggested approach & plan for the UX work that will be necessary to get to the finalized mockups, and an estimate of the monthly UX time commitment needed to complete the UX work being planned.
- As much as possible, the UX work should be planned in stages, to allow the development to happen iteratively:
- Each UX task should target preparing work sized to a single sprint of the developers (basic proof of concept at first, designing and implementing a small portion of a feature each time, etc.);
- Plan to schedule further UX tasks iteratively - while developers work on the outcome of the first UX task, work on the second UX task to prepare the developers’ next sprint, and so on.
- Developers (& Xavier Antoviaque) are reviewers on UX tasks, and Ali/Cassie are 2nd reviewers on developer tasks - this way developers can provide feedback on what can be achieved during their next sprint. Ali/Cassie write the stories for the developers as part of sprint planning, and the epic owner refine/split them as needed to take into account technical constraints.
- UX time requirement estimates are determined (as hours/month), and availability from Ali/Cassie is checked, and discussed as part of the epic planning management. When sprint planning managers prepare their cell availability, they also check with Ali Hugo the amount of UX hours the cell will need to progress on its epics. during the initial discovery of each epic.
Documentation updates & improvements criteria
- Discovery.
Review Timeline
- Ready for review by the end of the sprint.
Edited by Piotr Surowiec