项目经理应该在典型的 IT 项目上花费多少时间
我们最近对许多项目的成本进行了审查，结果是人们认为分配给项目经理角色的时间太多了。
例如，我们有一个开发项目，需要 10 天的开发时间，5 天的测试时间，3 天的技术文档时间，1 天的功能规范时间，7 天的 PM 时间。
一般来说（对于 IT 项目）人们对每个角色的时间百分比有何看法？开发、测试、BA、PM 等？
更新：假设 BA 做得很好并且要求足以减少返工
We've had a number of projects where the costs have been scrutinised recently and one thing that has come out is that people believe there is too much time allocated to the project managers' role.
For example, we have a development project which will take 10 days of development time, 5 days for testing, 3 days for technical documentation, 1 day for functional spec and 7 days for PM.
Generally (for IT projects) what are peoples thought on percentage of time for each role? Development, Testing, BA, PM etc.??
Update: Assuming the BA has done a good job and the requirements are sufficient for minimal rework
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我们有 %20 的比率，这意味着如果 PM 也是开发人员（在我的例子中是我），如果我花了 180 小时来完成项目中的所有实施，我可以使用 36 小时来完成 PM 的工作。
但这主要取决于您的组织类型。
we have %20 ratio which means that if PM is also developer(in my case it's me) if I spent 180hrs for all the implementation in a project I can use 36hrs for PM stuff.
But it is mostly dependent on your organization type.
这是一个很复杂的问题，没有具体答案，只有意见和建议。
您的开发人员的评估水平如何？完美的 10 天开发实际上意味着 15 天，因为没有人能够以 100% 的速度（速度）进行编码 - 白天总是会出现中断，从而占用时间（以及您的注意力）。
你无法计算出 BA 或 PM 应该在一个项目上花费多少时间，因为变量太多。如果BA没有做好，大家就得更加努力。如果开发人员做得不好，测试人员和PM就必须更加努力。如果由于太多的客户输入而导致需求发生变化，每个人都必须更加努力地工作。你明白我的意思了。
This is a biiiiiiig question with no specific answers, only opinions and suggestions.
How good are your developers at estimation? 10 perfect days for development actually means 15 real days because nobody can code at 100% speed (velocity) - there are invariably interruptions during the day which suck up time (and your concentration).
You cannot put a figure on how much time the BA or PM should spend on a project, there are too many variables. Everyone has to work harder if the BA hasn't done a good job. The testers and the PM have to work harder if the developer doesn't do a good job. Everyone has to work harder if the requirements are changing due to too much client input. You see what i mean.
我想这取决于你的客户在与产品经理合作时的反应程度。如果 PM 花费的这 7 天意味着开发人员在开始编码之前了解了他们需要了解的所有信息，那么可能就很好了。
如果开发人员经常因为 PM 没有很好地收集客户的需求和目标而受到阻碍，那么 PM 就会花费很长时间才能把工作做得不够好。
如果 PM 将所有时间都花在完善图表或制作漂亮的幻灯片上，那么也许这些时间花得不值。
确实很难说，但基于有抱怨的事实，我想这是否是批评总理工作质量的礼貌方式。
I guess it depends on how responsive your customers are when working with the PM. If those seven days the PM spends means that the developers know all they need to know before they start coding, it is probably just fine.
If the developers are constantly blocked because the PM didn't do a good enough job collecting the requirements and goals from your customers, then the PM is taking a long time to not do the job well enough.
If the PM is spending all his or her time perfecting diagrams or making pretty powerpoints, maybe it isn't time well spent.
It's really tough to say, but based on the fact that there is grumbling, I wonder if that is a polite way of criticizing the quality of the PM's work.