User stories - problems that cannot be made by users

Question

I am from XP background. I know this process very well and have solid experience working with it. I found this to be the best way to develop software.

I am in the role of a technologist, and this creates a lot of introspection and reassessment of my own concepts.

The very common thing that I hear is that some work cannot be done in history. I personally do not believe in it. Excuses include

• Too big (the developer has nothing to show until the end of 5 weeks).
• its complex algorithm or abstract concept (it will take 5 weeks to write and not show anything).

This question is for tips, tricks, or suggestions.

I am looking for tips, advice and suggestions on how to solve these and similar perceived problems (and much more if you can think about them).

I will mark the answer, which contains the most information about how to get around users / developers who do not write stories and do not refer to their many excuses as to why not (I just listed a few, and there are many more).

Answer 1

So basically, your question is: “What can I do if people claim that the task is too large for the user's history and cannot be shared.

In my experience, almost any problem can be shared. Ask them if they can implement the simplified version, leave the advanced functions, perhaps even use the default values ​​in some places; basically, anything, to create something that gives meaningful results (i.e. testable) in one iteration.

Remember: the iteration point is not full functionality, but useful and testable functionality.

This separation may be difficult, but it makes you first think about what you really need, which is very valuable. Developers can bitch about it (I often do it myself :-)), but it is really necessary. Overcoming large tasks into manageable user stories is at the core of all flexible methods.

However, if the task really, really, really can't be broken (think of a complex mathematical algorithm in a research task that takes weeks to even understand the basics), then your iteration is too short. The iteration should be long enough to produce meaningful results. And if most of your problems are so difficult that they take 2-3 months to do something, then your iteration length. But I never saw a project where it really is ...

Answer 2

Here are a few resources that I have gathered over time and which may help:

• Custom Story Templates
• Tool for weight loss stories
• Twenty Ways to Share Stories
• Ways to share user stories

Too big or too complicated, there is always a way to put the story on a diet (you may not get the final result in one iteration, but that doesn't mean you can't and, well, there will be more than one iteration).

Answer 3

users / developers who do not write stories

Users should not write user stories. They should not tell you user stories. You can expect them to talk about how they work, about the problems that bother them, and about what they would like to ease for their daily work.

You, in turn, must listen to them and take notes. If they allow, use a tape recorder or camera. Then you return the collected information when you reproduce it, and determine what you call user stories. You discuss them with the team, and when you have an agreement, you have use cases for your development.

What role developers play is up to you. If they are just coders, they are not involved in this process. If they partially act as consultants, they help determine user stories.

Answer 4

Usually, when you get “too big,” what they actually say is, “I only have a vague idea of ​​how this should work.” You need to work with them in order to better define it until it becomes possible to break it down into logical parts that are easier to manage.

Answer 5

The problem of “algorithmic specification” is a general one.

Many people prefer to write code and do not care about who this user is or what they do.

I try to get them focused by asking these questions.

• What actions can a person take? What can they do with the information? If they have a certain responsibility, they can take measures to deny, approve, hold, reject, process, stop, start, something. If the user cannot take any action, you need to ask if they are really interested.
• What decision should they make? How to decide what action (if any) to take? We cannot automate this decision - why people are in a cycle.
• What information should this person take in order to make a decision on taking action.

Information-decision-action.

We only write information preparation software for people to make decisions so that they can take action.

If this is not the trick, then the stories get out of hand.

Answer 6

This is mainly the responsibility and responsibility of the owner of the product. And there may be any requirements / tasks that cannot be divided into User Stories. I found many such discussions on the SCrum Master Forums

Answer 7

If the development team claims that the plot is too large and cannot fit into the sprint, take their feedback and try to share the story with the need and it's nice to have tasks and try to break it down based on this.

check this flowchart .. can help: http://www.agileforall.com/wp-content/uploads/2012/01/Story-Splitting-Flowchart.pdf