Day 8 mission
Not wide but deep:
Not wide but deep:
one flow that works all the way
By the end of today, someone must be able to click through from start to finish.
Using the design fixed yesterday, make the core flow work from start to finish. Build in units of requirement IDs and merge often; in the afternoon, share progress and blockers in an integration check demo.
Project Week · Day 8
Adjust times to fit your team. Run the afternoon talks with the timer in presentation mode below.
Done Criteria
Put this on the team screen and tick items one by one. Ticks are saved in this browser.
References
Course materials (blue) and outside official resources (purple).
Use only the approved docs (screen specs · DATA/API · LAYER_MAP · BACKEND_RULES) as your basis. This time the scope is just [REQ-___]. Before writing code, first report 1) related doc paths 2) files to change 3) anything unclear. Build after approval, and at the end summarize the changed files · how to run · results for each acceptance criterion (only what you actually ran). Don't touch other REQs or do refactoring I didn't ask for.
/qa-only Test the core user flow from start to finish. - Normal input / empty input / wrong input / repeated clicks / refresh / mobile width - Write it as a table (test item / expected result / actual result / verdict / steps to reproduce) - Draft FAIL items as DEF-### and suggest a severity Don't change any code.
Presentation & Discussion
Set the team order and times, then press Start presentation mode to open a full-screen stage and timer for the projector.
Enter one team per line in the format Team name | Project name.
Yellow 1 minute before the end · red with a chime at the end; overtime keeps showing with +.
Video Library
Pick only the topics you need during team work. Videos are public YouTube videos.
If playback is restricted by the uploader, open it directly on YouTube.
Day 8 · Daily Feedback
After Day 8 class, please answer a short survey. Your answers help us improve the next class and the course.