Requirements prioritisation methods

Track Your Course Progress
You are currently studying as a guest. Your course progress and quiz results will not be saved unless you login to your EduCourse account. Login to track your progress and qualify for your certificate.

How to Choose the Most Important Requirements

Requirements prioritisation methods help business analysts decide which requirements are most important to deliver first. This is useful because resources like time, money, and people are limited. Prioritising requirements ensures that the project focuses on the highest value parts and meets business goals. There are several common methods used to prioritise requirements in projects:

Popular Requirements Prioritisation Methods

  1. MoSCoW Method
    This stands for Must have, Should have, Could have, and Won’t have. Requirements are grouped into these four categories based on importance. Must have requirements are the highest priority, while won’t have are the lowest.
  2. Kano Model
    This method groups requirements by how they affect customer satisfaction. Must-be features are basic needs, performance features increase satisfaction, and excitement features create delight. Prioritising is based on these categories.
  3. 100-Point Method
    Stakeholders distribute a total of 100 points across requirements to show which ones they value most. The points help rank requirements by collective stakeholder input.
  4. Value vs. Effort Matrix
    This method plots requirements on a grid showing their business value against the effort or cost to implement. Requirements with high value and low effort are prioritised first.
  5. Weighted Scoring
    Requirements are scored based on factors like cost, risk, and business value. Each factor has a weight. Scores are added up to rank the requirements for priority.

Using these methods helps avoid arguments about which requirements matter most. It also makes it clear to the development team and stakeholders where the focus should be. In practice, business analysts often combine methods or adapt them to fit their specific project needs. The key is to involve stakeholders in the prioritisation process so their views are reflected. By applying requirements prioritisation methods, you improve project planning and increase the chance of delivering a successful solution that meets important business needs.

Live Scenario • Active Situation

You are a business analyst leading requirements prioritisation for a critical new software project at a fast-growing company.

There is no single perfect answer. Choose what you would do in this situation.