Step #1 : TravelNest - Define Product requirements for MVP
Tags: webdev, product
Published: 2023-08-21 04:01:07

Welcome back!  This is the second post in ["Creating TravelNest - an AirBnB Functional Clone" series](https://dev.to/meetashwin/creating-an-airbnb-clone-travelnest-3bja).

I am starting with a simple product requirements document that describes the core features of TravelNest.

I am using the following tools at this stage:
* A [simple product requirements template](https://www.atlassian.com/agile/product-management/requirements) from Atlassian

## Goals

* We aim to create a software application that lets travelers book places offered by home owners across the world
* This will be initially created as a responsive web application, that is accessed via desktop and mobile browsers
* Property owners can register themselves and list properties for rentals (including location, images, description, rates etc.)
* Travelers can browse through properties and choose one that meets their criteria
* Once chosen, travelers can make a booking which must be accepted by the respective property owner
* Once accepted, the property is unavailable for booking by any other traveler on same dates
* Travelers and property owners can exchange private messages related to property, until a week after the last date of stay
* Payments are settled outside the platform (for initial release)

## Assumptions

Here are some basic assumptions to help with the system design.

* Number of unique users => _< 10000 unique users per day_
* Number of active property owners => _< 250 MAU_
* Number of active travelers => _< 2500 MAU_
* Max. number of properties by a single owner => _5 properties_
* Max. number of current bookings by a single traveller => _3 bookings_

Further technical assumptions will be covered in system design.

## User personas

Following are key user personas for TravelNest application.

* **Property owner** : Who owns properties and list them for rental using the platform
* **Traveler** : Who searches for and books properties for stay
* **Site Admin** : Who manages the platform and have elevated access to prevent malicious usage of platform (e.g., fake properties, fake bookings etc.)

## Core user stories

![TravelNest User Stories](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/8lkssvdci6vi3nbrn8fk.png)
![TravelNest User Stories](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/drqoswagrezv7zx3pgub.png)
![TravelNest User Stories](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/j9ygdl676xyfnw5c4bvj.png)
![TravelNest User Stories](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/cgrf28lfq8hepatftcs4.png)
![TravelNest User Stories](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/9wenwth8x48w5g6vztbl.png)

## What we are not doing

* Mobile application is out of scope for MVP
* No variable price for properties.  Price per night is fixed for a property on all dates
* Date change on existing booking is out of scope for MVP.  For dates changes, traveller must cancel old booking and create a new one
* Payment for booking are settled outside the platform between travelers and property owners
* Videos are not available as part of property listing
* Website design is not part of development.  An opensource website template will be used

## Next steps

Now that we have the product requirements in place, the next step is to get some [C4 diagrams](https://c4model.com/) in place to describe the system to be built.  See you all soon!

**_Posts in this series:_**

1. [Step #0 : Creating TravelNest - an AirBnB functional clone](https://dev.to/meetashwin/creating-an-airbnb-clone-travelnest-3bja)
2. [Step #1 : TravelNest - Define Product requirements for MVP](https://dev.to/meetashwin/step-1-travelnest-product-requirements-for-mvp-b0b)
3. [Step #2 : TravelNest - System Design Diagrams](https://dev.to/meetashwin/step-2-travelnest-system-design-diagrams-3k2p)