I've been beating this drum as it's one of the more frequently cargoculted items about agile. A standup has 3 questions to report on: 1. What did you make pro

I've been beating this drum as it's one of the more frequently cargoculted items about agile. A standup has 3 questions to report on: 1. What did you make progress on yesterday? 2. What are you planning on making progress on today? 3. Do you have any blockers? Taking this pulse once every 24 hours is artificially constraining. Relevant stakeholders (product people, other engineers, project managers, etc.) should have perfect, frictionless visibility in to what people recently worked on, and what they are planning to work on at any given time, as self-reported by the team. Additionally, if you have a blocker, you should not wait until the next standup. Unless the blocker was discovered immediately preceding the standup, it should be well known to all who need to know with the same perfect, frictionless visibility. At the time of the standup, blockers should be well-known. I've specifically seen standups backfire as individuals use reserve their blockers until the next morning. It's a great reason to call it an early day when you hit a blocker and get the opportunity to report something of substance at the next day's standup. Perhaps I just described an unattainable utopia, but I think it's important to start with process idealism and make considered compromises rather than acculturating the status quo. I lead an entirely remote-first development team, and am adamant that standups often are a crutch at best, and inhibit progress at worst.