Skip to main content
10 events
when toggle format what by license comment
S Nov 7, 2017 at 21:20 history suggested Alan Larimer
not related to the Scrum framework
Nov 7, 2017 at 19:56 comment added Daniel I'm not sure why all the close votes. There are many good practices around splitting backlog items that may apply to different circumstances but are not opinion-based.
Nov 7, 2017 at 15:23 review Suggested edits
S Nov 7, 2017 at 21:20
Nov 7, 2017 at 10:34 comment added Thomas Owens Any way you want to? Most agile methodologies that I'm familiar with (Scrum, Nexus, Disciplined Agile Delivery, LeSS, SAFe) don't require requirements to be expressed as user stories. User Stories come from Extreme Programming. They may be helpful in other methodologies to keep the focus on the users of the system under construction, but they aren't the only way to capture requirements. Scrum simply refers to "Product Backlog Items" which have "the attributes of a description, order, estimate and value" -- nothing about how to specify that description.
Nov 7, 2017 at 4:09 comment added user1447718 without userstory how do i do it in agile system?
Nov 6, 2017 at 15:50 answer added Daniel timeline score: 3
Nov 6, 2017 at 15:35 comment added Thomas Owens Why do you need a user story? They aren't required, unless it's by your organizational processes (which I'd also question - it's useful for some requirements, but not all). If you decide to go forward with your user story, who (what user class or persona) uses these feed files and what benefit do they obtain from having them? Finally, why do you want to constrain your user stories to such a small point scale? A story should be an independently designable, buildable, testable, and releasable piece of functionality. Some stories require more effort to achieve that than others.
Nov 6, 2017 at 15:23 review Close votes
Nov 9, 2017 at 7:43
Nov 6, 2017 at 15:08 review First posts
Nov 6, 2017 at 15:22
Nov 6, 2017 at 15:03 history asked user1447718 CC BY-SA 3.0