Alpha2 Sprint
What went well:
- Planning, allowed to know where we stood, and adapt to deliver on time (even though it was a rush)
- Whitebox became a product during alpha2, the streaming in particular is a useful new function that works
- Software reliable to complete & record a flight despite issues & bugs (eg switch from tablet to phone)
- Almost all the tickets done on time for the flight
To improve:
- Milos not to try to complete many tickets at once
- We need to finish future releases without a rush or having to cut stuff
- In particular, we need to have the release candidate to test earlier => 1 ticket for testing the release candidate 2 weeks before the release itself, to have time to fix issues before the flight
LLM summary:
Positive outcomes from Alpha 2 planning and platform development (48:53)
- Avinash praised the detailed planning that enhanced focus and efficiency, calling it a personal breakthrough.
- Miloш noted how White Box evolved from a toy to a useful product, motivating the team with real-world interest from flight schools.
- Xavier emphasized the platform’s emerging reliability, with successful streaming on mobile despite rough edges.
- The team acknowledged that most issues were manageable without huge refactors, validating the architecture’s soundness.
Recognition of milestone delivery and schedule adherence (55:56)
- Xavier highlighted that most Alpha 2 tickets were completed on time, a notable improvement over previous cycles.
- Avinash shared that Alpha 3 planning intentionally schedules heavier refactoring tasks early to avoid last-minute rushes.
- The team agreed this approach helps maintain steady progress and reduces end-of-cycle pressure.
Identified workflow improvements for Alpha 3 (57:23)
- Miloш recognized the need to avoid juggling too many tickets simultaneously and return to isolated, focused commits.
- Xavier encouraged embracing small, continuous workflow improvements for sustained progress.
- Miloш felt this change would bring peace and better compatibility with Alpha 3’s planned work style.
Testing timeline improvements and release candidate strategy (58:38)
- Xavier stressed the need to have a stable release candidate ready two sprints before flight tests for early validation.
- Miloш agreed that earlier testing would reduce anxiety and improve issue detection but noted differing workflows.
- Xavier requested a ticket to formalize early testing and emphasized preparing a useful, stable version for meaningful feedback.
- The team concurred that the last two sprints should focus on polishing and testing, minimizing new feature development.