By Aditya Kumar Feel free to ping me on Twitter or LinkedIn if you have any questions. For full context of this template, read this blog - https://blog.devgenius.io/a-practical-approach-to-planning-your-engineering-requirements-better-f526aeae8678
Write a high-level summary of the product requirements derived from PRD (product requirements document). If it's already present in the PRD, copy and paste it. Mention the link to the PRD
Mention the link of the UI/UX file (Figma link etc.), if any.
Engineering functional requirements essentially translate the product requirements into their tech counterpart. For example, if the product requirement is the “Login flow of LinkedIn”, in that case, the functional requirements will be the high-level description of all the APIs associated with that user journey. Please write down the possible engineering edge and corner cases and how to handle them as a requirement.
Check the PRD for things that are out of scope from the product perspective. Please ask the Product manager/Engineering manager to update all the out-of-scope items if they need to be written. If they are already written, copy the link to that section of PRD here and then write down all the things that are out of scope from an engineering perspective.
These should be everything you factored out while designing the solution in this document.
This section should create a list of -