Build Reviews and Iteration Cycles
==================================

Formalizing design reviews and iteration cycles ensures that a team learns from every build and avoids repeating mistakes. Structured reviews turn subjective opinions into actionable insights, provide clear direction for the next iteration, and maintain a culture of continuous improvement. By committing to a disciplined review process, teams maximize learning and build more reliable robots.

Review Cadence
--------------

- Weekly or biweekly design reviews  
  Regular check-ins keep progress visible, catch emerging problems early, and allow small improvements before issues compound.

- Pre-milestone reviews  
  Conduct reviews before major deadlines such as the first competition, key prototype completion, or final subsystem integration. Ensure all subsystems are aligned and ready for testing.

- Post-competition retrospectives  
  After competition or major tests, reflect on what worked, what didn’t, and document lessons learned for future cycles.

Review Structure
----------------

- What was built  
  Clearly document the completed features, subsystems, and changes since the last review.

- What worked, what didn’t  
  Evaluate performance objectively. Identify strengths and weaknesses using data and test results.

- Lessons learned  
  Capture insights, design decisions, and recurring issues. This ensures mistakes aren’t repeated and successes are reinforced.

- Next iteration plan  
  Define actionable steps for the next cycle. Prioritize improvements, assign responsibilities, and set measurable goals.