3 ms·
Oh, well... if you do what the article say, start with an actual story about the user solving a problem, and destroy every useful element until you have a forma
by marcosdumay 4y ago
Oh, well... if you do what the article say, start with an actual story about the user solving a problem, and destroy every useful element until you have a formal scrum ticket... then your stories won't have any useful element.
You can throw them away, or you can stop destroying the useful part, and get useful stories to work with. You'll just have to accept that they are not standardized.
Really, there two basic ways to specify some software. The algebraic way where you enumerate (ideally independent) capabilities, and the narrative way with stories. Those lead to very different kinds of software, that fit better different problems/users. Throwing one of them away is a great loss.