Sprint structure

From now through nearly the end of the term, we're going to maintain a weekly sprint schedule. Each new sprint will begin during class on a Monday.

Because our sprints our short and we have just one project manager for eight teams, we're going to go with a very light-weight process.

Here's what we'll do each Monday.

• Push. Before class, your team will push completed work to your GitHub repository.
• Status report on Slack. Before class, your team will make a short post to the Slack #sprints channel. Your post will summarize briefly (like 1-3 short paragraphs or a handful of short bullet points) the work you completed during the previous week. Feel free to include any essential info you want to share (e.g., "we got stuck on X because of Y"). In any case, this written status report shouldn't take longer to read than 30-45 seconds.
• Team meeting. During class, you'll meet with your team to set the agenda for the coming week. I will go around the room to meet briefly with each team and talk with you about your plans.
• Sprint plan on Slack. After you have gotten a chance to talk with me about your upcoming week, you'll write a short description/list of things you plan to do during this sprint. Annotate your plans with the team member who is responsible for each task.

If you have suggestions about how the structure could be improved, don't hesitate to make suggestions in person or on #general.