<aside> 💡 The product requirements’ sole goal is to facilitate development and align teams. Therefore, the relevant PRD is a feature's only source of truth.

</aside>

PRD structure

1. Overview:
   • [Briefly explain the purpose of the feature or update]
2. Objectives:
   • [List the main objectives or goals the feature or update aims to achieve]
3. Requirements:
   • 3.1 Functional Requirements:
     • [List the specific functions or tasks the feature or update should perform]
   • 3.2 User Experience:
     • [Describe desired user experience and any specific design principles]
4. User Stories:
   • [List the user stories, outlining who, what, and why]
5. Implementation Roadmap, Timeline and milestones:
   • [Provide an estimate of the tasks, timeline, and milestones] - Request input also from the tech lead
6. User interaction and design:
   • [Outline how users will interact with the feature and any UX/UI considerations] - Request input also from the designer
7. Technical Considerations:
   • [Identify any potential technical issues, dependencies, or additional resources required] - - Request input also from the tech lead
8. Success Metrics:
   • [Define the key performance indicators (KPIs) and success metrics for the feature or update]
9. Open Questions:
   • [List any topics or areas that require clarification or are still uncertain]
10. Acceptance Criteria:
    • [Specify the acceptance criteria or conditions that must be met for the feature or update to be considered complete] - Request input also from the QA
11. Out of Scope:
    • [Clearly outline what is not included in the scope of this feature or update]
12. Revision History:
    • [Document any revisions or updates to the PRD]

Process

1. Create the PRDs on Confluence with an embedded Miro board for UIs in needed.
2. Link the user stories from the PRD with the corresponding Jira epic.
3. Analyze and break down each user story into tasks.