1.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中定义这些需求。
2.He basically considered his MRDs to be sort of like decrees.
他基本上认为他的MRD就像一个法令。
3.Templates make it is easier to bring new product managers up to speed in writing MRDs - as MRD contents vary from company to company.
模板让新的产品经理快速的写MRD变得容易，因为公司与公司之间的MRD内容是不同的。
4.One thing I've noticed often (much to my chagrin! ) during my 11+ years in the industry are MRDs that use a very contrived language.
在我超过11年的行业中，我通常注意到的（更多是令我懊恼）一件事是用很做作的语言来写的MRD。
5.Templates provide a standard format that makes it easier for readers who have to read multiple MRDs.
模板提供了一个标准的格式，使那些不得不阅读大量MRD的读者更加容易阅读。
6.Templates help ensure you don't forget to cover all aspects that need to be covered in MRDs.
模板确保你不会忘记所有需要在MRD中覆盖描述的部分；
7.I've noticed that these are often omitted from MRDs as many product managers and product marketers consider these "technical details" .
我注意到因为许多产品经理和产品市场人员认为这些是“技术细节”，而在MRD中被忽略。
8.Engineering teams dread having to read MRDs.
工程师团队害怕但又不得不阅读MRD。
9.It takes a long time to write as well as read the MRDs.
写MRD和读MRD都需要花大量的时间。