is it required, or even necessary, to create and write a PRD for a FEATURE within an already existing product? Example: an iteration of a product is already in live production, but it might be a little outdated or missing some key features. Stakeholders ask the PM to update it. Should I write a "smaller version" PRD? I don't have access or knowledge of an existing PRD for the old version.
Great question, Foster! In the scenario of an existing product, I would recommend putting together at least a one pager covering the following 4 key points: 1. What is the objective of the new feature? 2. Why is it needed? You can mention here how this feature complements or enhances the existing product. 3. Requirements - user story + link the jira ticket(s) for engineering team to review, and make sure to include acceptance criteria. 4. Success metrics: Goal (increase engagement or adoption, reduce contact rate, increase customer satisfaction, etc.) + specific metrics your team will track. The goal of the one pager will ensure that you and your team have a place to collaborate and document the requirements of the new feature. Whenever anyone has a question about the product decisions made for this new feature you can point them to the 1 pager. Hope this helps, thanks!
![Natanael Cano - Amor Eterno [Official Video]](http://i.ytimg.com/vi/EO4prCs6WpM/mqdefault.jpg)
![BabyChiefDoit - Too Slow (feat. STAR BANDZ) [Official Music Video]](http://i.ytimg.com/vi/zayaxws7RPg/mqdefault.jpg)
Hey Fam! Thank you so much for watching.
If you have any questions or know of any other PRD tips please share them below 👇🏽✨
super helpful! thank you!
Glad it was helpful, thanks for the feedback!
So insightful! Thank you so much!!
Glad you found the video insightful, and thanks for the constant support @mexicanmax227, it means a lot to us!! =)
Yes I need some tips in prd
Thank you so much
is it required, or even necessary, to create and write a PRD for a FEATURE within an already existing product? Example: an iteration of a product is already in live production, but it might be a little outdated or missing some key features. Stakeholders ask the PM to update it. Should I write a "smaller version" PRD? I don't have access or knowledge of an existing PRD for the old version.
Great question, Foster! In the scenario of an existing product, I would recommend putting together at least a one pager covering the following 4 key points:
1. What is the objective of the new feature?
2. Why is it needed? You can mention here how this feature complements or enhances the existing product.
3. Requirements - user story + link the jira ticket(s) for engineering team to review, and make sure to include acceptance criteria.
4. Success metrics: Goal (increase engagement or adoption, reduce contact rate, increase customer satisfaction, etc.) + specific metrics your team will track.
The goal of the one pager will ensure that you and your team have a place to collaborate and document the requirements of the new feature. Whenever anyone has a question about the product decisions made for this new feature you can point them to the 1 pager.
Hope this helps, thanks!
@@danteanditzel ythanks!
So the PRD should ideally be ready before going in for UX? or after it but before the UI?
Same question here
How long it will takes me to write such document? And as a freelance work how mich it can be cost ?
PRD
Chelsey Way
That Dante guy is a qt 3.14
Haha Hey Jacob! Hope you’re doing well 🙏🏽
Thanks for your constant support brother, you got me inspired by your craft of making videos 📹
@@danteanditzel Miss you man! glad to see you constantly branching out and working hard.