What do you do as a developer with customer requests without errors, i.e. Minor user interface fix?

Question

I am only one person working on a project, therefore I am a non-PM developer above me. I ended the portal, the hoverwer client attacks me from time to time with a request such as “make the font bigger” or change the field in css or make a button that does “xxx and yyy”. There is a simple task, sometimes just a few clicks, but it takes me a while, and I hate doing such tasks. On the other hand, I understand these people, and sometimes a small correction helps them in their work. What can I tell them on the communicators - they are difficult to ignore. It’s best to turn off communicators, but I need him to communicate with my colleagues. What do you do in such situations?

Answer 1

Create an established queue in which your users can send requests in such a way as not to interrupt your working day.

From the sounds of this, you receive requests through the communication channel that you regularly check, you can try to move it to the side.

Disconnecting communications is NEVER a good solution. In addition, I would outline the process and timeline when you get to these types of queries. I found great success in this simple approach.

Answer 2

If you work for yourself, your customers are your most important reason why you are. This is your business! Thus, it is always good practice to keep them happy.

It is said ...

- . , , . , , , , " ", , , .

, .

, / /-, , . , FogBugz , /. .

Answer 3

"", . , .

== == == $$

Answer 4

( MKS, ). , , . /, . . , , , , : " ?"

, . ( , , ), .

Answer 5

, . , , , .

, .

Answer 6

Do not change your path for each request you request. Collect feature requests for a while, then prioritize the queries, then select the ones that make sense, and then work on the next version.

In my opinion, it’s good to follow a fixed release schedule: it makes the development process more controlled, improves the quality of the software, and your customers know what to expect.