Monday: Set the Foundation

1. By 9 a.m. (latest 12 p.m.), update the tracker with all tasks for the sprint.
2. Share the sheet with the team and announce:
3. “This week’s tasks have been added to the sheet. Please update your task status if you’ve already started or if you have any questions.”
4. From 12 p.m. until close of business, focus on:
   1. Answering team questions.
   2. Getting feedback.
   3. Identifying which tasks will likely roll over into the next sprint.
   4. Spotting which tasks are realistic to complete this week.
   5. Updating the information on the tracker.
   6. Answering questions about the assigned tasks.

Tuesday: Push for Progress

1. Expect to see some tasks moved to In Progress.
2. At least one or two should already be marked Dev Done, ready for testing.
3. If no updates, remind the group and call out high-priority tasks directly.
4. Begin having short check-ins with owners of high-priority tasks:
   1. “You were assigned [this] yesterday – have you started? Any blockers? Do you need a call? Have you had time to look at it?”

Wednesday: Test Early Work

1. By midweek, you should have at least 1–2 tasks ready for testing.
2. When you begin testing, update the Test Status to In Progress.
3. Once testing is done:
   1. If the task passes, mark the status as Tested.
   2. If it fails, mark the status to ‘Kickback‘
      1. change the developer’s status to Pending
      2. and leaving a clear kickback comment.
   3. If blocked,
      1. log the blocker in the ‘blocker comment‘ and
      2. notify the responsible developer.
      3. Change the status of the task to ‘Pending‘.

Thursday: Prepare for Deployment & Next Sprint

1. Follow up with the team on all tasks still marked ‘In Progress‘.
2. Continue testing tasks that are now in ‘Dev Done‘.
3. Ensure a good batch of tasks are ready for production deployment.
4. Start preparing for the next sprint:
   1. Review the backlog.
   2. Collate potential tasks for next week.
   3. Check with whoever is responsible for assigning new tasks.

Friday: Deploy & Close the Loop

1. Give goahead to deploy all tested and confirmed tasks into the production environment for actual users.
2. Move deployed tasks into the “Completed” sheet to keep the active tracker uncluttered from the ‘weekly tracker‘.
3. Encourage the team to:
   1. Wrap up tasks still In Progress.
   2. Flag anything that must roll into next week’s sprint.
4. Celebrate progress and close out the week with clarity.

Why This Flow Works

1. Monday: Clear starting point for everyone.
2. Tuesday: Pressure to move from “assigned” to “in motion.”
3. Wednesday: Midweek testing ensures feedback arrives before it’s too late.
4. Thursday: Both closes the current loop and prepares the next sprint.
5. Friday: Ship work, archive it, and reset for the new week.