>Stand ups are bad - Let's be frank, I'm belting out code so quickly that staying on the same page as everyone else is just not worth the time anyway (at the sp

>Stand ups are bad - Let's be frank, I'm belting out code so quickly that staying on the same page as everyone else is just not worth the time anyway (at the speed I'm going it'll be done tomorrow anyway). Could you elaborate on this? I find standups most useful when we're working on small widgets of feature work precisely because we move so fast. Standups keep the business side in sync with the code we're putting out (e.g. features x, y ready to release, expecting z next week). It gives them a tighter feedback loop in case they need to manage expectations or coordinate with other groups. If we're working on meatier chunks that take longer then we back off to a pull model. When someone wants to know they ask, but daily standups aren't very helpful when updates sound like "Working on <huge_feature> for the forseeable future"