AACE AI SW
👤ParticipantACE AI SW
DAY 08 · WEDNESDAY · MVP BUILD · PROJECT WEEK

MVP development &
integration check

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.

Deep, not wide. One flow working all the way is today's success — better than 5 features half done.
Today's Schedule References

Project Week · Day 8

Build in the morning · talks and discussion in the afternoon

Adjust times to fit your team. Run the afternoon talks with the timer in presentation mode below.

AM Morning · team project focus

10 minStand-upREQ IDs for today · agree on integration times
90 minBuild cycle 1Start screen → key action (Vertical Slice)
10 minIntegration #1Merge into main and run the whole flow
70 minBuild cycle 2Done · error · recovery states
10 minIntegration #2Rerun the flow · record defects

PM Afternoon · integration check demos and discussion

3 min per teamIntegration check demoShow the flow actually working
2 min per teamFeedbackBlockers · help · suggestions
10 minWhole-class discussionShare AI use and integration tips
60 min+Build cycle 3Fix defects · integration #3 · prepare POC

Briefing · 10 min

Today's short guide slides

Keep explanations under 10 minutes and move straight to team work. Move with ←/→; N key for lecture notes.

Day 8 mission

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.

ScreensAPIBusiness rulesData storageResult screenOne feature running from screen to DB = Vertical Slice
✗ Wide — screens onlyScreens · all builtAPI · not yetRules · not yetData · none yetClicking does nothing✓ Deep — one slice all the wayScreensAPIRuleDataThis, today!Tomorrow · next day
Split & integrate

Build in parts, merge often

The longer you delay integration, the bigger the conflicts and bugs.

mainfeat/REQ-004-optionfeat/REQ-007-cartfeat/REQ-009-soldoutIntegration 1 · end of morningIntegration 2 · after lunchIntegration 3 · before demo
Split by REQ IDOne person = one REQ (fewer file conflicts)
Feature branchfeat/REQ-004-option-select
Small commitOne feature = one commit
Integrate 3 times a dayEnd of morning · after lunch · before demo
Analogy · Jollof Rice

Stir often, taste often = integrate often

✗ Each cooks alone to the end → one pot at the endRiceTomato sauceMeat?!Even if it tastes wrong, you only find out at the end✓ Jollof rice: add → taste → add againSauceRiceMeatTaste oftenThe more often you stir and taste, the earlier you catch mistakes = integrate often
Build cycle

One REQ at a time, in the same order

Don't ask AI to "make an app"; send a request with locked scope.

One REQ↻ Next REQ1. Check doc IDs2. Lock scope for AI3. Build4. Check git diff5. Test · run6. Commit7. AI_WORK_LOG
Verify

After building, check with two pairs of eyes

The code view and the user view find different problems.

/review — the code's eyesdiff · security · rule breaks/qa-only — the user's eyesVerdicts on normal · empty · error input+CriticalCore flow stopsTodayHighMain feature errorBefore POCMediumInconvenientLogLowMinorLogDEF-### severity · when to fix
/reviewDefects · security · rule breaks in the diff (code view)
/qa-onlyExpected/actual verdict table for normal · empty · error input (user view)
DEF-###Severity Critical · High · Medium · Low + steps to reproduce
15-minute rule

Stuck for 15 min? Don't struggle alone

If AI keeps going the wrong way, you just lose time.

15 minAlone · with AI/investigateCause first · no fixesMark it on the team boardShare the blockerCall the instructorWith steps to reproduceAfter 15 min
0–15 minTry to solve it yourself + with AI
15 minFind the cause with /investigate (no fixes)
Tell the teamMark the blocker on the stand-up board
Call the instructorWith steps to reproduce
Integration demo · 3 min

The afternoon integration check demo is 3 min · real screens only

No slides; show the running service.

Demo · 1 min 30 secActually click through the core flowStatus · 1 minWhat works · what doesn't · defectsPlan · 30 secTo do before tomorrow's POC
1 min 30 sec · DemoActually click through the core flow
1 min · StatusWhat works / what doesn't / defects
30 sec · PlanTo do before tomorrow's POC
1 / 7
LECTURE NOTE

Done Criteria

Today's Done Check

Put this on the team screen and tick items one by one. Ticks are saved in this browser.

Presentation & Discussion

Presentation Mode Settings

Set the team order and times, then press Start presentation mode to open a full-screen stage and timer for the projector.

Presentation order

Enter one team per line in the format Team name | Project name.

Time settings (min)

Yellow 1 minute before the end · red with a chime at the end; overtime keeps showing with +.

  • SpaceStart / pause
  • →←Next / previous step (talk → Q&A → next team)
  • RRestart timer · +- adjust 30 sec
  • DWhole-class discussion · BBreak/waiting screen · FFull screen · EscClose

10-Day Course Navigation

Click the buttons above to go to the Day 1–10 learning pages.

Video Library

Day 8 reference videos

Pick only the topics you need during team work. Videos are public YouTube videos.

Related YouTube Videos
  • MVP development
  • 1. How to Build An MVPHow to keep an MVP smallEN
  • 2. Getting Started With Django REST FrameworkStart a back-end API fastEN
  • Git teamwork · integration
  • 3. GitHub Pull Request, Branching, Merging & Team WorkflowBranch · PR · mergeEN
  • 4. Git Feature Branch Workflow: A Beginner's Guide for TeamsTeam branch strategyEN
  • AI coding · debugging
  • 5. Harness engineering - getting Claude Code and Codex to work properly with gstackUsing gstack review · QAKR
  • 6. How I Use Claude Code and Codex on a Real FeatureBuilding a real feature, step by stepEN
  • 7. How to debug code with Claude - Full GuideDebugging with AIEN
  • 8. I Fixed Every Bug Claude Code Couldn't (Here's My Exact Process)What to do when AI can't fix itEN
  • 9. How to Make Claude Code Your AI Engineering TeamBetter quality by splitting rolesEN

If playback is restricted by the uploader, open it directly on YouTube.

Day 8 · Daily Feedback

Today's Course Satisfaction Survey

After Day 8 class, please answer a short survey. Your answers help us improve the next class and the course.

Open Day 8 SurveyJoin with the button or QR code
Day 8 Daily Feedback Survey QR codeSCAN TO OPENNigeria AI Training · Day 8