OK so this is what I think when someone really asks this question to a Manager or the BB… now that I assume that this question comes out of one or more person from a Team… I believe that these questions really affect the Team the moment they get raised…
These are first of the few things I really think why these questions are raised:
1. Is he paid for chatting, reading newspapers and bossing around?
A member not having enough visibility on what others within his team are doing has this question in mind quite often… The best way to avoid this is to let everyone know in a Scrum what each one is up to for that day/week.
2. I have so much of work and he sits Idle?
Most of the time the question comes because of different duties or responsibilities each one is handling… Most of the time people confuse between duties and responsibilities… I really had to mention that "Do you know what your CEO does? And the answer was NO, so the issue here is that the moment you feel you are working hard; you see others not working so hard… Law of nature really….
3. The beginning of the problem is the End of the Day?
So most of the developers tend to stay late at least that's the culture out here in India… many of them are bachelors who prefer not to go on their hostels where they don't have Yahoo, Internet and of course work… So while you work late and late you feel you are the only one in the office who work… no matter you really work till then or just funk around.
4. The taste of the Poison can only be tested when you Taste it?
Many of the aspirants feel that what their superior does or knows is less than what he or she knows and does… common misconception that leads to a Team trauma at the same time raises this question too often in the mind… The major issue here is the poison of success (I am on my way to write this soon) doesnt let them think sensibly...
5. I am always left alone….
Now this is a problem with a genre that has some einsteinius genes… well I really mean that they like to be alone… in their own world, dreaming about the figures and the code they are writing…, most of the times these hysterical genes don't allow them to think anything up until 10 in the night and when they wake up they realize that the whole day is gone doing nothing but programming and it's already next day morning ;). The cause hits the case and the question gets a base…
Now that I have written a bunch of why's I think it will be relevant to put on How to avoid these things…. After all We are here to Grow a Team not Build it;)