Product Requirement Documentation

At this point, it was important to create a minimum product requirement document where I employed the MoSCoW method of prioritising features for design and development.

• M - Must have this requirement to meet the business needs

• S - Should have this requirement if possible, but project success does not rely on it

• C - Could have this requirement if it does not affect anything else on the project

• W - Would like to have this requirement later, but delivery won't be this time

This allowed us to prioritise all features that we intended to develop in the first iteration when advocating the user. For example, we wanted to create a map view of comparing accommodations, in each city, where we designed the feature but left the development for the second iteration in order to meet the business needs in launching the product.

*Due to the proprietary nature of this product, only pre-approved examples of the work I completed have been published in this case study.