4 ms·
It sounds like you're trying to decompose software into developer tasks, which is not what (my interpretation of) agile is about. Forget the developer for a mo
by stickfigure 7y ago
It sounds like you're trying to decompose software into developer tasks, which is not what (my interpretation of) agile is about.
Forget the developer for a moment and take the user perspective. What's the first thing the user wants to do? Log in? Ok, that's a story. What's the next thing the user wants to do? See a list of widget prices? Ok, that's a story. What's the next thing the user wants to do? Change a price? Story.
If you can't sit down and think of a dozen narratives like this, then the fundamental problem that you don't really understand how people are supposed to use your software or what your software is supposed to do.
- loopz 7y agoActually, those are stories developers tell themselves, not users!
- CyberDildonics 7y agoCalling everything a 'story' is just another in a long line of trends that pretend making up a new name for something is progress. (Also a user doesn't actually want to log in, they want to do something and you are making them log in)
- jussij 7y agoI would think if 'login' was simple enough to write as a single story then that login feature would be next to useless. The task of login is more about security, access control, authorization and tracking, not just giving the user access to a web landing page. That level of complexity makes it a project in itself.
- stickfigure 7y agoThat depends on business requirements. In simple cases, auth can be as simple as dropping a little javascript on the page. But sure, you can have follow-on stories like "user is denied access protected resource" or "admin sees resources accessed by user". Enough individually-useless stories and you end up with a useful app. That's kind of the point of agile.