Sprint 4: Final Build & Integration

Session Timeline

Learning Objectives

• Prioritize features under time constraints
• Apply MoSCoW prioritization method
• Make strategic trade-offs between features and stability
• Conduct thorough integration testing
• Identify and fix critical bugs before presentation
• Freeze features at appropriate time
• Complete end-to-end system testing
• Prepare system for final demonstration

The Reality of Final Sprints

Common Situation:

• 10 features you'd LOVE to build
• 5 days until presentation
• Some bugs still exist
• Documentation needs updates
• Demo needs practice

MoSCoW Prioritization Method

Categories:

• Must Have: Critical for MVP, demo fails without it
  Example: User login, core booking functionality
• Should Have: Important but not critical, adds significant value
  Example: Email notifications, search filters
• Could Have: Nice to have, adds polish
  Example: User profile pictures, dark mode
• Won't Have: Explicitly out of scope for now
  Example: Mobile app, AI recommendations

How to Prioritize Features

For Each Feature, Ask:

1. Does demo work without it?
   • No → Must have
2. Does it significantly improve user value?
   • Yes → Should have
3. How long will it take?
   • > 4 hours → Probably cut it
4. How risky is it?
   • High risk of bugs → Probably skip

Feature Freeze

Why Feature Freeze?

• New features introduce new bugs
• Need time to stabilize system
• Focus on polishing what exists
• Ensure demo readiness

Bug Triage: Which Bugs to Fix?

Severity Levels:

• Critical (P0): System crashes, demo fails
  Fix immediately!
• High (P1): Major features broken, bad user experience
  Fix before presentation
• Medium (P2): Minor issues, workarounds exist
  Fix if time permits
• Low (P3): Cosmetic issues, typos
  Document as "known issues"

Regression Testing

Why It Happens:

• Changed shared code
• Modified database schema
• Updated dependencies
• Merged conflicting branches

Prevention:

• ✓ Run full test suite after changes
• ✓ Manual smoke test of core features
• ✓ Demo walk-through after each merge
• ✓ Keep changes small and isolated

Integration Testing

What to Test:

• Frontend ↔ Backend: Do API calls work?
• Backend ↔ Database: Does data persist correctly?
• Authentication Flow: Login → Protected Routes
• External Services: Payment, email, maps API
• End-to-End User Flows: Complete user journeys

Part B: Final Feature Build

Today's Goals:

• Implement 1-2 final features OR fix critical bugs
• Run comprehensive integration tests
• Verify demo flow works end-to-end
• Document any remaining issues as "known issues"
• System ready for presentation

End-to-End Testing Checklist

Manual Testing:

• ✓ Complete user registration flow
• ✓ Login with valid and invalid credentials
• ✓ Navigate all main pages/features
• ✓ Create/Read/Update/Delete operations
• ✓ Test form validation (empty fields, invalid data)
• ✓ Test error messages display correctly
• ✓ Logout and verify session cleared
• ✓ Test on multiple browsers (Chrome, Firefox)
• ✓ Test responsive design (mobile, tablet, desktop)

Demo Rehearsal as Testing

Rehearsal Testing Process:

1. Follow Demo Script Exactly:
   • Do EXACTLY what you'll do in presentation
   • Use same data, same clicks, same flow
2. Note Any Issues:
   • Features not working as expected
   • Slow loading times
   • Confusing UI elements
3. Fix Critical Issues:
   • Anything that would ruin demo
4. Repeat Until Smooth:
   • Demo should run flawlessly 3 times in a row

Documenting Known Issues

# Known Issues

## P2 - Medium Priority

### Issue: Search results slow with > 1000 records
**Impact:** Search takes 3-5 seconds with large datasets
**Workaround:** Currently testing with < 100 records
**Future Fix:** Add database indexing and pagination

### Issue: Email notifications occasionally delayed
**Impact:** Booking confirmation emails take 1-2 minutes
**Workaround:** Users can see confirmation on-screen immediately
**Future Fix:** Implement message queue (e.g., Bull, RabbitMQ)

## P3 - Low Priority

### Issue: Dark mode has some contrast issues
**Future Fix:** Comprehensive accessibility audit

Performance Considerations

Quick Performance Checks:

• Page Load Time: Should be < 3 seconds
  • Check Chrome DevTools Network tab
  • Optimize large images
• API Response Time: Should be < 1 second
  • Check browser console network timing
  • Add loading spinners if > 1 second
• Database Queries: Avoid N+1 queries
  • Use database query logging
  • Optimize with indexes if needed

Final Code Review Checklist

Before Feature Freeze:

• ✓ All console.log() debug statements removed
• ✓ No commented-out code blocks
• ✓ No hardcoded passwords or API keys
• ✓ All TODO comments addressed or documented
• ✓ Code follows team conventions
• ✓ Error messages are user-friendly (not technical stack traces)
• ✓ All tests passing
• ✓ No merge conflicts in main branch

Ensuring Deployment Works

Pre-Presentation Deployment Check:

• Deploy to Production/Staging:
  • Don't demo from localhost if possible
  • Verifies deployment process works
• Test Deployed Version:
  • Environment variables set correctly?
  • Database migrations ran?
  • All features work in prod?
• Seed Production Data:
  • Create realistic demo data
  • Test accounts with good passwords (not "password123")

Before Next Lecture (Final Session!)

1. Implement Feature Freeze:
   • Complete final features TODAY
   • After today: bug fixes only!
2. Final Testing:
   • Run demo 5+ times
   • Ensure zero critical bugs
   • Test on presentation computer if possible
3. Complete Slides:
   • Finalize presentation slides
   • Get screenshots of working features
   • Prepare backup plan (video/screenshots)
4. Team Practice:
   • Full run-through as team (15 min + Q&A)
   • Time each section
   • Smooth transitions between speakers
5. Prepare for Assessment:
   • Review assessment criteria (next lecture)
   • Ensure all deliverables ready