PRD

Product Requirement Document (PRD)

INTRODUCTION

User generic
Razorpay
5/5

1. How to write a Project Specification (aka PRD)

This video emphasises on importance of detailing while writing a PRD to ensure that it’s objective of Specification is well achieved. All you really want to do is communicate what you need to the developing team. It doesn’t really matter how you do it, or the format or what it looks like, or how you deliver it as long as you communicate it well. First you wanna keep in time that you should always put in as much detail as possible, you can’t have too much detail. Forgetting something is a big expensive mess, so don’t hold back to try to get as much as you can.

Imagine that the reader, your developer, is coming with zero knowledge: Explain everything no matter how rudimentary or obvious it seems get it down on paper.Imagine they have to learn everything from scratch.

  • Use lots and lots and lots of words.
  • Don’t go short.
  • Don’t try to be concise.

Consider the writing process as a brainstorming exercise and just jump around all over the place and when something comes to you just add it in. Just start typing, typing and typing and you’ll drill down on each requirement just like shown in the example below.

Brainstorming process shown through real example based on a site that tracks people’s weight loss.

A client comes to the service provider they say I’ve got this great idea for the weight loss site and here are the requirements. And let’s say one of the requirements says something like this.

  1. User’s can see metrics about their workout. (Unclear about what metrics are being talked about) Lets’ try again.

     2. Logged-in user you can see metrics about their work out.             

(Not so clear yet but the idea of the exercise is just to add stuff for brainstorming.) Let’s try putting 1 metric

  1. Logged-in user can see a progress chart showing their weight loss.

(Now we’ve got a specific metric in mind.) Let’s try to add one more thing.

  1. Logged-in user can see the progress chart showing their weight loss period. The chart              will show the users weight loss by day, week or month.

Now, let’s try brainstorming in a totally different way We’re gonna tell a User story. These are sometimes called use cases, sometimes called user stories.

  1. A user wanted to see their weight loss so they logged in to this site and

they viewed a chart showing their Progress.

Let’s try it again (we’ll add a little more brainstorming and we’re adding stuff all the time.)

  1. A user wanted to see their weight loss so they logged into the site, clicked on “My Progress” and saw a chart showing their weight loss. 

(This is even better. Now we came up with something new. The developer didn’t knew that there was an area called My Progress.) Let’s try it again.

  1. A user wanted to see their weight loss so they logged into the site, clicked on My Progress and saw a chart showing their weight loss. Their weight had gone up that week and because they were gaining weight the chart was displayed in red.

Vola! We finally did it.

User generic
SourceSeek
4/5

Writing a Project Specification with minimal Pain

People who are looking at faster methods of writing mistake free PRDs, give this a read

User generic
SourceSeek
4/5

1. How to write a Project Specification (aka PRD)

Bitnami