How do you deal with repetitive storytelling?

Question

The idea of ​​dividing work into business history comes down to reducing the relationship between tasks. But how do you handle stories where the common part of the work is common to them.

For example, if you have two stories, like displaying information received from one web service, but also on two different pages, how do you deal with the general task of creating code to call a web service?

Do you combine them into one big story? Do you create a third “story” with just the technical challenge of creating a common web service code? Do you keep the original and allow two developers to choose a plot to argue with each other?

What is the most flexible approach?

Answer 1

It depends on how much work you need to call the web service. If this is a small percentage of the total size of the story, it does not really matter; if they are made at the same iteration, just let the developers talk about it while working to find out who will do it.

If you work more instead of calling a web service — perhaps this includes a LETTER of a web service — then you should see if you can break this work down into a third story. Perhaps this third story contains all the work of calling / recording a web service, and then enough work on the front side to demonstrate that it works with the business. Then, at the next iteration, you can tackle the remaining two (original) stories. The advantage is that you demonstrate value for the business and at the same time do not fit in with the details of the front end.

Answer 2

In our environment, we will create three stories in your case, one to call the web service, and the other two will have a dependency (the tool we use supports the creation of “blocker notifications” that link tasks with dependencies). The result is as if there was one story, including a web service, and one without it, except in this case, you can prioritize the two types of use of this web service, and when the story requiring it stretches, if necessary, implement the web - the service will need to be move first.

Answer 3

Creating an additional task to create common things is the way to go.