Daily Scrum

- A shared goal (optional) — set it in the settings (e.g. "Working first version this week"). It keeps the updates pointed at the same target.

- The three questions: what I did since last time, what I'll do now, what's blocking me.

- Team size and time per person — set in the settings (default 4 people × 60 sec). Keep it short on purpose.

- Progression: manual (you click to the next person) or automatic. And the agreement that obstacles are named here but solved afterward.

- Standing or sitting: standing keeps it short; sitting works if standing isn't practical, but watch the time.

- Parking lot: note obstacles on a board ("parking lot") and tackle them right after, with only the people involved.

- Shorter or longer per person: 30 sec for a quick pulse, more for younger students still learning to be concise.

- Visual board: combine with a task board (to do / doing / done) so updates point at real items.

- As a closing instead of an opening: run it at the end of a lesson to recap and set up the next step.

- Project groups (any subject): daily coordination during a project week.

- Technology / research: keeping a build or investigation on track across sessions.

- Team / department: a quick teacher-team check-in during a busy period.

- Mentoring: students reporting progress on a personal goal.

- Final project: structuring long-term group work with short check-ins.

The Daily Scrum comes from Agile / Scrum, the framework by Jeff Sutherland and Ken Schwaber for teamwork in short cycles. The idea: a fixed, short moment where everyone shares their progress and obstacles keeps a team aligned without long meetings. It develops concise communication, ownership of one's own work, and making blockers visible in time.