Run a project standup

Use this guide for a short project operating review. It works for daily standups, triage, launch reviews, and lightweight delivery check-ins.

Prepare the view

1. Open the project picker.
2. Select the project.
3. Open Tickets.
4. Select the saved board for the meeting, such as Standup, Triage, QA, or Leadership.
5. Check hidden-status warnings.
6. Switch to List view if you need to find tickets hidden by the board.

If the project does not have a useful board yet, create one before making the meeting dependent on it.

Start from Today

1. Open Today in the same project scope.
2. Review focus items, proposed work, drift, and blockers.
3. Note Inbox counts and queued Agent Runs.
4. Refresh Today if the team made major changes since the last review.

Today gives the operating signal. The board gives the ticket-level execution state.

Review active tickets

1. Move across the board from left to right.
2. For each active ticket, ask:
   • Is the status accurate?
   • Is there a next owner?
   • Is due date or priority wrong?
   • Is the ticket blocked?
   • Does it need a comment, link, or parent?
3. Move cards only when the workflow state truly changed.
4. Fill required fields before moving through restricted transitions.
5. Open the ticket when the card does not contain enough context.

Keep the meeting focused on changing state, surfacing blockers, and clarifying ownership.

Process AI review items

1. Open Inbox in the same project scope.
2. Review memory diffs and operating proposals relevant to the project.
3. Accept only accurate and useful proposals.
4. Reject stale, speculative, duplicated, or wrong-scope proposals.
5. Return to the board and confirm accepted proposals changed the expected items.

Do not accept AI proposals just to clear the queue.

Capture updates with Check-In

1. Confirm the project Check-In cadence and questions in project settings.
2. When the Check-In dialog is due, enter the current focus, blockers, wins, and changes.
3. Refer to issue keys when an update belongs to an existing ticket.
4. Submit the Check-In.
5. Wait for Agent running if you expect proposals or memory diffs.

Good update:

APP-42 is blocked by missing SSO test credentials. Sarah owns the next step. We should not create a new ticket.

Weak update:

Still blocked on login stuff.

Specific issue keys help TOW update the right work instead of creating ambiguous proposals.

End with decisions

1. Confirm each active blocker has an owner.
2. Update due dates that no longer match reality.
3. Create tickets for concrete follow-up.
4. Create decisions or risks for durable judgment calls.
5. Archive or resolve stale tickets.
6. Note what should be reviewed in the next standup.

After the meeting

1. Wait for Agent Runs to finish.
2. Reopen Today and Inbox.
3. Review any new proposals from the check-in.
4. Confirm the board still reflects the team's actual work.

Related guides: Create a project board, Create and update tickets, Review AI proposals.