The so-called "cloud architectures" are not an architecture at all. They are a deployment strategy that removes choices, adds complexity, and locks you into a specific vendor. They often damage (or preclude you from having) an actual architecture. Literally everything you do in the cloud, you could do with multiple threads in a monolith (something I often do before breaking up the monolith into distinct services because it makes building and testing easier). So, the architecture can be deployed on the cloud or in a monolith.

Refining a story and defining details before you implement, release, and get feedback is just waterfall requirements gathering. Those requirements _will_ be wrong. Agile is NOT waterfall. It's not doing what you did before but with new names.

<sigh/> Let's just get rid of the damn sprints entirely! When you're done with the current thing, pull the next thing. The entire team works on one story at a time. It takes as long as it takes.