Audience: Hub Leads

Purpose: Provide a clear, repeatable, step-by-step procedure for running consistent, high-quality team reviews across all hubs.

Outcome: Every team demonstrates real progress, receives accurate feedback, and remains accountable to deadlines.

1. PURPOSE & EXPECTATIONS

Team reviews exist to ensure teams are making measurable weekly progress toward their final submission. Reviews are not brainstorming sessions or casual check-ins. The Hub Lead is responsible for:

• Verifying actual working progress through live demonstrations
• Identifying blockers early
• Ensuring technical quality through structured code walkthroughs
• Creating accountability through documented action items
• Feeding accurate data into the weekly report

Your job is to validate progress, surface issues, and guide teams forward.

2. BEFORE THE REVIEW: PREPARATION PHASE

Follow these steps before meeting any team:

2.1 Schedule Review Sessions

• Notify teams at least 24 hours in advance.
• Use the following review timetable to share a review schedule with the teams https://docs.google.com/spreadsheets/d/1K-4kZm_9M7FsjM_EzgBlLKeOmj9BZX5O1sM4i5BGZ2I/edit?usp=sharing
• Share the review timetable (15–20 minutes per team, depending on complexity).
• Inform them that:
  • A live MVP demo is mandatory
  • A code walkthrough will be required if John is present
  • All team members should join

<aside> 💡

If @Ndigirigi John is required for a technical review, he needs to be consulted first when preparing the schedule so it aligns with his timeline!

</aside>

Exact message to send: