Requirements prioritisation

Context

To figure out which features need to be developed with which level of priority, I made a MoSCoW list of requirements using the requirements prioritisation research method.

Results

Analysing the problem statement and B2B requirements

Based on the problem statement, project assignment and current B2B store, I already identify a list of requirements of basic webshop functionalities, in the form of user stories.

Interview with Robin

To figure out more detailed requirements, I interviewed Robin who is the product owner of the Masita project, who has worked on tons of webshops including the Masita B2B webshop.

• Which requirements can we already identify that aren’t already mentioned?
• Are there possible future features that we should consider?
• Are there any features that we might want, but might not be realistically achievable within the scope of the project?
• How can we keep scalability in mind?
• How can we prioritise the requirements list? (Is there a preferred way of documenting and prioritising these? E.g. MoSCoW model)
• Are there any additional requirements in terms of development/store we should consider?

From this interview, I was able to gather all the information that I needed which meant I could then start prioritising these requirements.

The full document which shows a more detailed approach, including Robin's answers can be found here:

Conclusion

Priority listing

As a conclusion, I noticed that while most of the requirements are based on the user’s needs, there are quite a lot of development requirements to ensure scalability and support future needs. This means I need to take these into account when researching which technologies are going to be used to develop the store.

Learning outcomes

3: Future-Oriented Organisation

By making this requirements prioritisation I show that I can take into account an organisational context and define what the project needs and how those needs should be categorized to optimize time spent making an MVP.

4: Investigative Problem Solving

By making this requirements prioritisation I show that I can identify issues and define the main scope of the project.