2.2 KiB
Daily standup
Purpose: Provide a fast daily synchronization point for the product group and a quick triage of freshly reported bugs awaiting reproduction.
Cadence: Daily, 15 minutes, same time every working day during the sprint.
Participants: Full product group.
Ritual DRI: EM or assigned team member.
Format
- Share screen and open the team's GitHub Projects board.
- Call on each participant and filter the project board to that assignee.
- Participant answers the questions in the agenda below. If there are blockers, they are added to the parking lot and the standup continues.
- Call on the next participant until everyone, including the ritual DRI, has provided an update.
- Open GitHub pull requests filtered using the template below after being modified to include each product group member:
is:open is:pr archived:false org:fleetdm org:osquery draft:false sort:created-asc author:sgress454 author:lucasmrod - Call out verbally any PRs open for more than the time to merge KPI goal (24 hours).
- End the Daily Standup for everyone except those with parking lot issues.
- Go through each parking lot item with the relevant participants and define and assign TODOs to resolve the blocker.
You can find our time to merge and other detailed engineering metrics on the Grafana engineering metrics project.
To determine order of standup, some ideas are alphabetical order, wheel of names, or random. Ritual DRI should call on participants and not wait for volunteers.
Agenda
- What did you work on yesterday?
- What are you working on today?
- Do you have any blockers?
Blockers are parked for later discussion to keep the standup short and focused. If a blocker is reported, the name of the team member and the issue are added to the parking lot agenda at the bottom of the ritual document.
Notes
- See daily standup definition in the handbook.