I don't like agile stuff much, but I love user stories. They let you start thinking deeply about the UI for a feature before you do anything else. That way, y

I don't like agile stuff much, but I love user stories. They let you start thinking deeply about the UI for a feature before you do anything else. That way, you don't wind up implementing a data model that doesn't map nicely to a UI. Look at old KiCad with it's feedforward pipeline approach full of manual "finish and move to the next tool" compared to other apps. Core functionality and user experience aren't always easy to separate. Starting with user stories lets you design the core of the app in a way that won't constrain the UI or require nasty piles of hacks to get 5he results you want. They also make edge cases more likely to jump out, in a story it's easy to see steps where stuff could go wrong, as opposed to a requirement that isn't like a story, which might be described in a more isolated way and not connected to other features, and not reveal the issues you might have at the interfaces.