top of page

PRD Best Practices

Monday, October 22, 2018
3:30 PM to 5:00 PM 
Hawes 203

​

NO LAB THIS WEEK

​

Required Reading

  1. Food Chief PRD [Link in Canvas]

  2. Your MVP is Minimal, But Is It Viable? By Alex Iskold

 

Recommended Reading

  1. How to write a painless Product Requirements Document by Jerry Cao

​

Minor Deliverables: By 5pm on Friday, October 26

  • Lo-Fi Testing: Post links in the “Oct 26 - LF2” tab to your first round of Lo-Fi test “proofs” and key learnings . There are two columns to post links:

  1. Link to a doc with pictures, video and any other artifacts worth sharing.

  2. Link to a Google Doc of your team’s top 3 key learnings from your Lo-Fi test(s) and how these learnings will inform a) your solution ideas and b) your next round of tests.

  • MRD Peer Reviews: Each student will be assigned to another team’s MRD for qualitative feedback. Every team will get an equal number of reviewers per team (e.g., a four person team will have four reviewers). See below for specifics on Peer Reviews.

  • ​

Session Prep:

  1. Review the Food Chief team’s PRD example posted under "Required Reading" above. Bring to class any questions you have about the PRD.

  2. Be prepared to discuss your three key learnings from your Lo-Fi tests. 2-3 teams will be asked to present their findings (and pics/videos) with the class. Selected teams will be notified by 10:00am on Monday, October 22.

​

For those of you planning ahead, the October 29 session will focus on usability testing of your wireframes. If you have not started already, please get familiar with Proto.io, Balsamiq and/or Invision and begin sketching out wireframes of your product. Focus on the key use scenarios you expect your target persona to use in your MVP. You will be bringing your wireframes to the Oct 31 Lab for live testing!

​

PEER REVIEW INSTRUCTIONS:

Peer review assignments will be in the Assignment Master on the "Oct 19 - MRD" tab, no later than Oct 22. Please do not leave your reviews to the last minute! Earlier feedback helps you and your colleagues fine tune plans for work going forward.

​

MRD Peer Review Tips:

​

  • Provide constructive feedback on plans, insights and whether ideas resonate based on your understanding of the project and target persona(s).

  • If others have already provided feedback on the MRD you have been assigned before you've had a chance, be additive either on their comments or constructive on areas yet addressed. "Agree" or grammar edits do not count as constructive comments.

  • Probe or make suggestions on areas that you feel have more to be explored or are not clear to you. Remember, what is clear to the author may not be as obvious to the objective reviewer.

  • It is not necessary to comment on everything in the MRD, but we expect at least 6-10 comments by each reviewer.

  • Teams: Please remember that all MRDs should be in Google Docs with commenting ON for reviewers (plus Julia and Christina) for your MRD. Also please do NOT resolve any comments - it is important to preserve these for when you get to the PRD process and for end of semester reflections.

​

Happy reviewing!

bottom of page