MEETING MINUTES OVERVIEW Context: Sprint retrospective, 2026-07-06, attendees Vel, Sarah, Jake, Lena, Tom. Goal: review sprint 14 outcomes and blockers. Summary: The onboarding flow shipped Tuesday and cut signup errors by 12%. Jake will fix the API rate limit bug before Friday. A marketing demo is planned for next Thursday with Lena preparing slides. QA backlog growth prompted a contractor discussion, with Tom drafting a budget proposal. Moving standup to 9:30 stayed unresolved. DECISIONS - Marketing demo confirmed for next Thursday. - Next retrospective scheduled for the same time in two weeks. ACTION ITEMS Jake - Fix the API rate limit bug - Friday Lena - Prepare demo slides for marketing - Wednesday Tom - Draft budget proposal for QA contractor - No deadline OPEN QUESTIONS - Should standup move to 9:30? No agreement reached. - Should a QA contractor be hired to reduce the backlog? NEXT MEETING Same time in two weeks (next retrospective). EMAIL RECAP Subject: Recap: Sprint 14 retrospective - decisions and actions Hi all, quick recap of Monday's retrospective. The onboarding flow shipped and cut signup errors by 12%. Jake is fixing the API rate limit bug before Friday, Lena is preparing slides for next Thursday's marketing demo, and Tom will draft a budget proposal for a possible QA contractor. The standup time change to 9:30 remains open. Next retrospective is in two weeks, same time. Thanks! VERIFIED - Summary words: 52 (max 60) - Decisions: 2 (max 5) - Action items: 3 (max 8) - Open questions: 2 (max 4) - Subject characters: 54 (max 60) - Email body words: 65 (max 120)