Features:
Must-Have: (The project would fail if the following features/functionalities is not met)
Answering format:

  • What is this feature/functionality?
  • Where would this feature be on the webportal? (E.g. the searching for jobs would be a new page on the web portal)
  • The ideal steps for a user to use this feature/functionality (e.g. Step 1 The user clicks on the top search for job bar. Step 2 The user enters the input. Step 3 The user sees a list of jobs with titles, location… on their browser, Step 4 The user click on one of the jobs and get redirected to a new page on another tab
  • Briefly explain the connections between this and other features (if any)

Note: The above format would help us the best to understand more precisely thoughts about a feature in your mind. You do not have to follow the entire format if you really cannot think of any, but it would be good to do so. : )

Should Have: (The project would not fail if the following features/functionalities are not met, but the project would be tougher to gain attractions)

Could Have: (The project is completely fine without the following features/functionalities. These are just some neat, interesting stuff but do not necessarily serve a greater purpose. This might be hard to distinguish from the should haves. My suggestions would be to consider how these features impact the value of our project to the users/customers)

Won’t Have: (The features that would likely be in the project, but for some reason, we can’t. Either time or resources do not allow us to implement these. We would like to keep those ideas and possibly move those to the categories above in the future: )