[{"id": 398213, "created": "2024-06-07T07:09:39.807845", "project_id": 193, "task_id": 454213, "user_id": 300, "user_ip": null, "finish_time": "2024-06-07T07:13:13.894537", "timeout": null, "calibration": null, "external_uid": null, "media_url": null, "info": {"answer": "10 Best Practices in Writing Requirements.\nUse a Basic, Best-practice Format. ... \nDefine Terms and Use them in a Standard Manner. ... \nKeep Functional Requirements Free of Design Details and Descriptions of Operations. ... \nInclude Additional and Supporting Information. ... \nBe Clear in Your Wording. ... \nOrganize, Standardize and Templatize.", "data_id": "cac101dcf208a4962b4e8dde9eaa96b0", "category": "business", "question": "How to write a good requirements document?", "answer_URLs": "https://archives.obm.ohio.gov/Files/Major_Project_Governance/Resources/Resources_and_Templates/04_Plan/37_Requirements_10_Best_Practices.pdf", "answer_type": "cant_find", "input_query": "How to write a good product requirement document?", "is_reliable": "very_reliable", "edited_answer": "10 Best Practices in Writing Requirements.\n\nUse a Basic, Best-practice Format. ... \nDefine Terms and Use them in a Standard Manner. ... \nKeep Functional Requirements Free of Design Details and Descriptions of Operations. ... \nInclude Additional and Supporting Information. ... \nBe Clear in Your Wording. ... \nOrganize, Standardize and Templatize.", "question_type": "good", "location_related": "no"}}]