Comments by "ForgottenKnight1" (@ForgottenKnight1) on "USER STORIES Shouldn’t Be TOO BIG" video.

1. Show books (source is irrelevant, hardcoded or very simple adapter are preferred choices) 2. Show books from old application (here you connect to it, whatever it is) 3. Show books with details from source X (integration with source X API) 4. Show books with details from source Y 5. Show books with details A, B, C, D (that might come from source Z) By now, you might have guessed the idea.
4
@CanalDoFante There's a lof of "cheating" that you can before you actually need any infrastructure on the cloud. Infrastructure should appear if there is a business need for it, not by default.
3
Not long. The outcome of the first approach is a failed product right from the start, because there is no business that can clearly state its needs "on first go". The second one will lead to a successful product because you are building iteratively and you provide incremental value to which the users can react and provide feedback.
1