From 1c3632c6877dea54780e34321469d74f6b81ff28 Mon Sep 17 00:00:00 2001 From: Anthony Arendt Date: Tue, 6 Aug 2024 17:28:15 -0700 Subject: [PATCH] tidy up the titles Co-authored-by: Jessica Scheick --- docs/training/projects/project-during.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/training/projects/project-during.md b/docs/training/projects/project-during.md index 5f13488..d8cb2b9 100644 --- a/docs/training/projects/project-during.md +++ b/docs/training/projects/project-during.md @@ -77,7 +77,7 @@ It's common for teams to dive into the project work too early. Do you know the n * All team members check back in at the end of the day, review progress towards tasks, anything preventing progress, and planned next steps * Project leaders may also want to share with the whole hackweek group: How the project is coming along, what are the objectives and tasks identified by the team today, and what other skills might your team need to be successful? -## Daily Team Standups +## Days 1-5: Standups A "standup" meeting model may be useful for your team to check in at the beginning and end of each day of the hackweek. During these short meetings, each team member is given a minute or so to briefly share 1) progress they have made on their tasks, 2) anything preventing progress, and 3) what they plan on working on next.