liveBook · Manning

Standup meeting

As explained in Delivering Machine Learning Projects: From design to deployment

A stand-up meeting is a brief recurring team meeting in which members report work progress, plans, and impediments.

A stand-up meeting is a brief daily project check-in that keeps engineers connected to the work, surfaces progress and impediments, and supports shared responsibility. section 4.3.2

Use the meeting as one element of a controlled project cadence:

  • Hold one daily stand-up for the product owner, customer technical representative or troubleshooter, and engineering team. section 4.3.2
  • Avoid adding meetings until they reduce uncertainty; more than one project meeting per day can reduce productive setup time. section 4.3.2
  • Coordinate the stand-up with weekly reviews, sprint planning, sprint closure, and post-sprint reviews rather than using it as the only checkpoint. section 4.3.2

How Delivering Machine Learning Projects: From design to deployment covers it

How deep it goes
Defines the daily cadence and participants, but does not specify a speaking format, agenda, or time limit.
Examples
Uses engineers, a product owner, and a customer technical representative as participants in a daily project meeting.
What it assumes
Assumes a defined project team and optionally a sprint-based structure for coordinating work and related checkpoints.
What you can do after
Operate/configure a daily coordination checkpoint without allowing meeting overhead to crowd out engineering work.
How it connects
Connects sprint-based work with product ownership, project communication, sprint planning, risk reviews, and stakeholder governance.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Delivering Machine Learning Projects: From design to deployment. The section links point to the parts of the book it draws on.