Templates provide a standard format that makes it easier for readers who have to read multiple MRDs.
模板提供了一个标准的格式，使那些不得不阅读大量MRD的读者更加容易阅读。
I think this is primarily caused by the misconception that MRDs need to sound formal and professional.
我想这个主要是因为MRD听起来是正式的和专业的原因吧。
I've found these to be very important part of my MRDs and engineers have really appreciated these requirements being defined in MRDs.
我发现这些是我的MRD中非常重要的一部分，工程师们会非常感激在MRD中定义这些需求。
I've noticed that these are often omitted from MRDs as many product managers and product marketers consider these "technical details".
我注意到因为许多产品经理和产品市场人员认为这些是“技术细节”，而在MRD中被忽略。
I recommend that you only include P1, P2 and P3 requirements in your MRDs, as lower priorities are unlikely to get done in most projects anyway.
我推荐你只要包括P 1,P 2,P3的需求在你的MRD中，在多数的项目中更低的优先级可能未必会实现。
This will help you create better MRDs, engineers will like you more (or at least hate you a lot less!), and your team will create better products.
这将帮助你写出更好的MRD，工程师将喜欢你（或者至少少恨你一些），你的团队也将创造更好的产品。
This will help you create better MRDs, engineers will like you more (or at least hate you a lot less!), and your team will create better products.
这将帮助你写出更好的MRD，工程师将喜欢你（或者至少少恨你一些），你的团队也将创造更好的产品。
应用推荐