It sounds like you don't have a problem with ratio of staff so much as a problem of people doing other people's jobs instead of their own. That's a company culture thing, and comes from upper management. If you're upper management, work with HR to determine the root cause of the problem and fix it - if you don't like it.
If you're not upper management, learn to work within it or find a new job. Unfortunately, I don't have a lot of experience in that environment, so I can't tell you the right way to play politics. But I can tell you that you've got a bunch of choices.
You might...
Tell people that they need to trust you to do your job, and that they need to do their job. When they're intruding on your space, tell them to stop. Make sure that individual responsibilities are clearly defined, and stick by those definitions.
Talk to your boss, and see if s/he can help put people in their place.
Try and get the other team members overloaded with work that they should be doing, so that they're not doing the work you should be doing
If people want to discuss stuff about which they have no clue, and you want to make the discussion productive, explain to them that the fundamentals that make the decision obvious are well documented, and identify where, preferably text books or standards documents. If they read the documents and still disagree, point out the additional documents that they obviously haven't read, but which they need to read.
ignore what everyone tells you, and just do it "right" - but you damn well better pick the correct value of "right". And you lose your job, regardless.
Ignore what everyone else says, since they obviously don't care what you think, and just go with the flow. Let them see the error of their ways. And you may lose your job, and get all the blame when the project fails. And don't be surprised if the people who really caused the problem get promoted.
Pick a developer or two whose sole responsibility is the wasted meeting time. These few, trusted developers could then take back the parts of the meetings that are actually important and the rest of the team could do their work. Note that these folk are often called "managers" :)
good luck - I hope someone else posts a good answer...
If developers spend more than 4 hours a week in meetings, in my opinion something is wrong. Even more than 2 is questionable. This is over an extended period of time because it can vary by what stage the project is in.
I have no hard numbers for this, only the experience that most time spent in meetings is wasted time.
发布评论
评论（2）
听起来你对员工比例没有什么问题，但问题是人们做别人的工作而不是自己的工作。这是一种公司文化，来自高层管理人员。如果您是高层管理人员，请与人力资源部门合作确定问题的根本原因并解决它 - 如果您不喜欢它。
如果您不是高层管理人员，请学习在其中工作或寻找新工作。不幸的是，我在那种环境下没有太多经验，所以我无法告诉你玩政治的正确方法。但我可以告诉你，你有很多选择。
您可以...
祝你好运 - 我希望其他人发布一个好的答案......
It sounds like you don't have a problem with ratio of staff so much as a problem of people doing other people's jobs instead of their own. That's a company culture thing, and comes from upper management. If you're upper management, work with HR to determine the root cause of the problem and fix it - if you don't like it.
If you're not upper management, learn to work within it or find a new job. Unfortunately, I don't have a lot of experience in that environment, so I can't tell you the right way to play politics. But I can tell you that you've got a bunch of choices.
You might...
good luck - I hope someone else posts a good answer...
在我看来，如果开发人员每周花在会议上的时间超过 4 小时，那就是出了问题。甚至超过2个也是值得怀疑的。这是一个很长的时间段，因为它可能会因项目所处的阶段而异。
我没有这方面的确切数字，只是经验表明，大多数花在会议上的时间都是浪费时间。
If developers spend more than 4 hours a week in meetings, in my opinion something is wrong. Even more than 2 is questionable. This is over an extended period of time because it can vary by what stage the project is in.
I have no hard numbers for this, only the experience that most time spent in meetings is wasted time.