[{"id": 397061, "created": "2024-06-06T14:33:49.257586", "project_id": 193, "task_id": 453876, "user_id": 300, "user_ip": null, "finish_time": "2024-06-06T14:34:26.179779", "timeout": null, "calibration": null, "external_uid": null, "media_url": null, "info": {"answer": "Objective/Goal: Explain why are you building this and what do you hope to accomplish. Features: For each feature, you should include a description, goal and use case at a minimum. Additional details may be helpful or necessary depending on the complexity of the feature, such as out-of-scope items.", "data_id": "3d21b0ef482a2925bfd2affe7d8048cc", "category": "business", "question": "What are the objectives in PRD?", "answer_URLs": "https://www.productplan.com/glossary/product-requirements-document/", "answer_type": "incorrect", "input_query": "What is the content of PRD?", "is_reliable": "very_reliable", "edited_answer": "A product requirements document (PRD) is an artifact used in the product development process to communicate what capabilities must be included in a product release to the development and testing teams. This document is typically used more in waterfall environments where product definition, design, and delivery happen sequentially, but may be used in an agile setting as well.\n\nThe PRD will contain everything that must be included in a release to be considered complete, serving as a guide for subsequent documents in the release process. While PRDs may hint at a potential implementation to illustrate a use case, they may not dictate a specific implementation.\n", "question_type": "good", "location_related": "no"}}]