D
D
Denis Oleshkevich2015-01-29 13:03:20
Business Informatics
Denis Oleshkevich, 2015-01-29 13:03:20

How to effectively take into account the comments of the client?

During communication with the client, a list of “non-tasks” is born, about 10-20 points. Each of these “undertasks” needs to be thought about, reformulated, described in more detail, decided when to do it and to whom to entrust it, after that it becomes a real task and can be added to the tracker. It often happens that this task is already in the system, which means that you need to remember about it and update it.
This whole process takes a lot of time and effort, and I want to put it away. But if you do not turn "undertasks" into tasks today or the next day, then it is simply impossible to remember what was meant.
What techniques or tips are there to help simplify or structure this process?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
W
w495, 2015-01-30
@w495

I can’t say that I am a great professional in such matters,
but it seems to be better to start not from the tasks, but from the client’s goals,
and formulate tasks together on their basis.
If the goal is achievable, then the intermediate tasks are no longer so important.
The least important ones may turn out to be unnecessary at all.
10-20 points - do you communicate with him continuously for several hours?
It may make sense to break the communication into more rounds.
About remembering what was meant - there are different techniques for recording oral speech
that simultaneous interpreters use. If needed, I can look for the book.
I think that this will simplify the process of turning the "undertask" into a task.
From experience, it is good when there is more than one person at a meeting with a client.
As a result, everyone hears, understands and fixes something of their own.
All this also helps to construct a more or less complete picture.
Why are they forgotten? Our tasks sometimes hang in the queue for years,
but we remember about them. True, someone expressed the idea that if a
“task hasn’t stuck” for more than a year, then it can be safely closed.
+ It seems that duplicates are not as bad as they seem.
Do you use different scrum boards there?

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question