Every company fails in some respect with at least rate limiting. The last thing you should do in software dev is introduce more meetings, but that's how manager

Every company fails in some respect with at least rate limiting. The last thing you should do in software dev is introduce more meetings, but that's how managers interpret agile. If I didn't get anything done, or only a trivial part of a bigger picture, the last hing I want to talk about or hear from anyone else for 30 minutes first thing in the morning is that. Likewise with only being able to the fastest things done in two weeks, or small parts of them if the sprint schedule isn't adapted to the team very well. In most circumstances, one or two updates a week would be fine, preferably followed by the rest of update meetings so more contiguous hours of problem solving can happen.