Team Weekly

Team Weekly Meetings

Our primary gathering is held every Monday at 6:00 PM. The structure of the meeting alternates based on where we are in the two-week sprint cycle.

---

1. Weekly Updates (Every Monday)

We begin every meeting with essential updates from leadership to ensure alignment:

• Workflow or process changes
• Project announcements and status updates
• Management updates
• New tools or best practices

---

2. Week 1 Agenda: Sprint Planning & Task Assignment

A. Issue Overview

We review all backlog issues available for the new sprint on each repository’s Projects page. The TPM will share the relevant links in Slack before the meeting.

B. Task Sizing

PMs and Lead Engineers assign issue sizes (e.g., S/M/L) before Sprint Planning to streamline the process.

C. Issue Selection

Rules for selection:

• One person per issue, unless marked Medium+ (where pairing is allowed).
• Choose issues based on available time and skill comfort.

D. Q&A

Open floor for clarifying questions before selection is finalized.

---

3. Week 2 Agenda: Sprint Retrospective

This meeting is focused on learning and process improvement. The full process is detailed on the Retrospectives page.

A. Placement Period

Everyone gets 5 minutes to add thoughts or notes to the retrospective project board (What Went Well, What Didn't, etc.).

B. Review Discussion

We review all retrospective entries. Time spent depends on the depth of discussion required for action items.

---

4. Parking Lot (Post-Agenda)

This is a flexible, open space for the team, often used just before or during the Developer Meeting:

• Share research or present findings
• Raise new ideas or offer new tools/workflows

---

5. Developer Meeting (Post-Agenda)

This is one of the most important parts of the practicum for hands-on support.

• Open Q&A and team discussions
• Live troubleshooting, code challenges, or screen sharing
• Pairing or walkthroughs with Leads/PMs