产品经理工作总结之需求管理

宝宝宸

需求管理是产品经理工作中非常重要的环节，能直接决定整个团队的工作节奏和产品效果，尤其在面对有敏捷迭代需求的项目，更是如此。那我们要从哪些方面来思考需求管理呢？
产品的需求总会源源不断地来自各个方面，来自客户、领导、研发人员等，如何管理这些纷繁复杂的需求很重要。（现状）
首先要有一个需求池来容纳这么多的需求，目标并不是把需求全部做完，也不是为了管理而管理，而是要找到优先级更高的需求，解决用户最关心的问题，从而实现项目以及公司的最大价值。
为了做到第一步，我们先要确定产品总体的愿景和目标，再进一步地将大目标拆分成季度目标和月度目标，形成产品发展的一个路线图（roadmap），为的是将目标细化，通过具体的目标进行需求管理，这样就能比较合理地对需求进行排期并划分优先级。
还有一点，一般而言项目的总体目标是不变的，但是小周期中的小目标是可以灵活变动的，就像敏捷宣言中所言：响应变化高于遵循计划才是正确的处理方式。
一份详细清晰的需求列表除了标明优先级，还要有需求的描述、提出人、提出时间、需求评估结果、当前进度等信息，这样才能更好的对需求进行管理。如果需要与业务方进行密切合作，也可以将需求清单共享给用户查看，与用户建立起良好的沟通机制。
当一个需求比较复杂时，在进入需求评审阶段之前，有必要与研发先进行小范围的讨论，目的是确认技术上的可落地性和迭代需求范围。前者的作用不必多说，能够直接评估需求是否能够实现以及研发所需的时间。后者的作用有可能被忽略，精确的迭代范围能够维持一个短（比如2周）而稳定的开发周期，在频繁的迭代中长此以往能够提高团队对工作量评估的准确度，进而改善整个团队的工作节奏。
对于不必要的需求要及早砍掉，避免浪费时间。
Demand management is very important in a project. It determines the result and work rhythm, especially for projects with agile requirement. The problem is how to manage different kinds of demands.
Demands come from different people, like clients, manager or even developers.
First, we need to have a demand pool to include all the demands. Our goal is not to finish all the demands or manage demands. Our goal is to filt out demands with high priority. Realize these demands can satisfy clients and realize the value of company.
To reach the goal mentioned above, PM need to know the overall vision and target of the project. Then divide the target into quarter goals and month goals. These goals make up a roadmap for the project. With more specific goals, we can prioritize demands better.
Usually, the overall target of the project is stable but smaller goal in a period is changeable. As the saying goes, "responding to changes is more important than obeying the plan".
A detailed demand list should contain priority, description, proposer, proposed time, evaluation result and current progress. With all these information, we can analyse demands better. Also, if we cooprate closely with our clients, we can share the demand list with them to build a good communication mechanism.
When a demand is very complicated, before it goes into review stage, we should have a small meeting with developers to talk about technical feasibility and demand scope. To estimate the demand scope is very important. It can help developers estimate development time. If we can accurately estimate the time for every iteration, the team confidence would be enhanced.