By way of the [Nyquist-Shannon sampling theorem](https://en.wikipedia.org/wiki/Nyquist%E2%80%93Shannon_sampling_theorem), which described minimum necessary sampling frequency for a given type of signal, you should **meet twice as frequent as you expect the team to be able to course-correct**. The theorem states: > The minimum sampling frequency of a signal that it will not distort its underlying information, should be double the frequency of its highest frequency component. Just think of a sinusoidal wave: In the worst case, sampling exactly at the frequency of the wave would give you the impression of a monotonic, constant signal. For example, if the stakeholder or decision maker meets the product team only once per week, the team effectively can only raise and then implement important changes over the course of two weeks. If your meetings are on Monday, and an issue occurs during the week, it will take until the next week to meet the stakeholder. And then it will take another week to review the outcome with the stakeholder again, for two weeks in total. Your meeting frequency therefore should be a function of **uncertainty**. In very urgent cases you might have a standup in the morning and a show-and-tell session in the afternoon for maximum agility. While in stable, long-running projects you might go several weeks between meetings. Ref: http://195.134.76.37/applets/AppletNyquist/Appl_Nyquist2.html