It took us two chapters to complete our first user story. Now, we have a minimum viable product (MVP) that we can experiment with. In agile, slicing requirements in this way is really powerful. We could start collecting feedback from some test users and decide what is the next feature we should build. Also, it’s early enough to change something if our product ideas were wrong.
Learning how to slice your product requirements vertically instead of horizontally may save you a lot of time while building software. That means you don’t wait until you have a full layer completed ...
