New answers tagged

4

Each story should be valuable independently. But don't get too hung up on it. The idea is to avoid partial functionality. ie spending ages doing something and being unable to demonstrate any progress towards the project goal. So for example say I have an ecommerce site project with a Login story and a Purchase story. Obviously I need both to have a ...


0

I think the heart of your problem, at least in this particular example, is how you decomposed the story. To me, the story about the QA officer needing to have data recorded isn't a story. There may be stories around how the QA officer queries, views, and exports data. But the fact that data is recorded seems like it would better fit on the story or stories ...


0

Context is king. A story that happens after authentication is dealt with somehow is still a useful story. You do not have to bake a fully detailed authentication story into every user story simply because you're required to always authenticate. Also, your authentication requirement is only "always" in certain contexts. Your software and procedures might be ...


Top 50 recent answers are included