It depends on the size of the team, and how well you run meetings (agenda, specific issues to be discussed, how well these issues are written, precise topics), how large the project is, etc.
You can have a very tight feedback loop (sometimes writing experimental code and coming up with a proof-of-concept during the meeting) if you run a tight ship.
The issues we experiment with are usually quite broad - improvements to logging, routing - but the implementation is always more narrow. Still, it seems like there is still more room for more refinement and focus now that you mention it.
You can have a very tight feedback loop (sometimes writing experimental code and coming up with a proof-of-concept during the meeting) if you run a tight ship.