That's how I use the data: Say No to demand

I often encourage my programmers to say no to demand, and I would like to share some experience with you in this area.

First of all, people are very strange animals, for easy to get things, often not enough to cherish, especially such as the process of virtual dongdong, but also the "free" access to the program do not have to look at, usually no evaluation, or evaluation as: it is so.

This is what every developer doesn't want to see, so I say no to any needs!

Not that I do not respect the user, in fact, I want to do better, I think the risk of the demand for people, actually do not know what they want! But they always thought they knew what they didn't want, that the software that is required to do so is not considered necessary, and there is no such thing in the world that they can always pick on you (it requires some logical understanding), so boldly reject him, no matter how anxious he says!

1, if this user really needs a certain function, he will talk about this with you, you will not miss the opportunity to make cow x software

2, if this user really needs a certain function, he will carefully think again, why the boy does not give me this, is not my request is very unreliable, and then he will rack his brains to think: how to be reliable?

3, if this user really needs a certain function, he will find people with similar needs, the collective harassment you, indicating that this is indeed the point of opinion, not his personal wishful thinking

4, if this user really needs a certain function, he will further study the problem, perhaps only in the original function based on a little work can be completed, without new features.

5, if this user really needs a certain function, xxxxxxx

XXXXX here represents a lot of content (including, of course, complaints against you!) But you have to resist the pressure. These things help you buy time, you can actually think about what to do in the meantime, help you to bring all you expect: clearer requirements, creative ideas, a group of people can be discussed collectively, etc., but also help users to fully mobilize the imagination and executive power, He's going to do everything he can to get it, won't he?

Secondly, programmers are also very strange animals, often bear their own pressure, like complaining but dare not fight with the user and the boss, in fact, fighting a fight everyone has been moving, everyone in this process to say their own ideas, if not recognized, but also inspire him to improve his ideas, become more ingenious, which is often the source of creativity, That's really great!

Finally, lying is a strange thing, clearly it is easy to do the function, but it is difficult to say, this often requires some methods, fortunately, some common methods can be referred to

1, I am busy with other projects

2, I think this function is a bit difficult technical, I need total total

3, this is not on the current planning route, we put it to the 2 period can it?

4, xxxxxxx

The story is not over, as programming has metadata, project also has metadata, this is-demand statistics.

If you are very careful, on a comprehensive record of each demand for the person, time, background, whether the previous needs of the continuation, etc., set an early warning line (a function on a number of indicators), to the alarm conditions to put on the agenda.

We insist on doing so, and we find

1, in this process, often a team training more scientific, more methodical.

2, programmers and users have more communication, they become a base friend

3, software development is no longer isolated, users are used to noisy, all kinds of things should be a few sentences, together with the completion of some very interesting works

4, because at any time to quarrel, team members become extroverted.

Okay, so I'm using the data to play games with the demand, and you?

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/Programming/project/