agileagile-project-managementagile-processes

How to handle this story


I am not sure when you would break story into stories or into tasks.

Let's say you have a story that talks about bringing down a service, and to do that you have to analyze and depreciate 5 api where each one takes one week

How would you do that ?

1) break story into 5 stories and this way every story is less than a sprint and can be owned by someone (but cant be demoed)

2) break a story into tasks but then multiple people is working on a single story and one story is lasting more than sprint

Other? Thank you


Solution

  • Let's say you have a story that talks about bringing down a service

    Why are you doing that? Who is going to benefit from it?

    That information will help you to create the story associated with the work item.

    As a [person that benefits from this work] I want the service brought down so that [reason]

    Now, once you have defined the user story you can then add sub-tasks to it that describe how the work will be done. e.g.

    Sub-task1 = deprecate API X

    Sub-task2 = deprecate API Y