Skip to main content
10 events
when toggle format what by license comment
Nov 2, 2018 at 13:47 comment added Max Hohenegger Hi Daniel, I suppose the vanilla Scrum approach would be to break down just enough to fill 2 or 3 sprints with stories, while keeping (and estimating) the remaining requirements on epic level. For historic reasons I don't want to get into, we have to do the full breakdown in advance in this case. But I am interested in what disadvantages this could bring, compared to any other approach that you have in mind.
Nov 2, 2018 at 13:36 comment added Max Hohenegger To clarify the scale: I would estimate the breakdown will eventually lead to a number in between 500 and 1k stories, plus around 2k acceptance criteria (GivenWhenThens). Because we are developing a product, we also have to deal with changing business requirements from multiple customers.
Nov 1, 2018 at 21:54 comment added Daniel Hi Max, I'm curious about this statement: "customers may insist on a breakdown of a large number of requirements for planability". In my experience there are other ways to plan without decomposing large amounts of the backlog.
Nov 1, 2018 at 20:25 comment added Doc Brown IMHO you are overthinking this. Changing the requirements description of a dozen user stories in the backlog requires a fraction of the time of implementing only a few, or just even one of them in code. How often, in reality, did you encounter a situation where you had to rewrite so many user stories that you felt it became unmanageable?
Oct 31, 2018 at 16:22 history edited Robbie Dee CC BY-SA 4.0
edited title
Oct 31, 2018 at 12:00 history tweeted twitter.com/StackSoftEng/status/1057603218304352256
Oct 31, 2018 at 11:14 answer added Robbie Dee timeline score: 5
Oct 31, 2018 at 11:12 history edited Robbie Dee CC BY-SA 4.0
deleted 1 character in body
Oct 31, 2018 at 10:00 review First posts
Nov 2, 2018 at 16:53
Oct 31, 2018 at 9:56 history asked Max Hohenegger CC BY-SA 4.0