Home / BA / What is requirement prioritization in Business analysis?

What is requirement prioritization in Business analysis?

Requirement Prioritization is a process or technique to line-up all the requirements for the Development process in the Software Development Life Cycle ( SDLC )
            It is a technique to identify and manage the importance of various requirements to acknowledge the limited resource available.
            All the Functional requirements get queued according to the priority basis. The factors which decide the priority of the requirements are as follows :-
a)     Importance
b)    Risk
c)     Cost
d)    Benefit
e)     Time
f)     Strategy

The main actors who keeps plays vital role in prioritization of any requirement are :-

  1. Customers
  2. Developers
  3. Business Owners

The techniques which is used for the prioritization of requirement in the project development life cycle are :-

  1. 100 Dollar Test
  2. Top 10 Requirements
  3. Numerical Assignment
  4. MoSCoW
  1. 100 Dollar Test :-  100 Dollar Test is the fastest and Simplest Prioritization technique which is relative in nature.
  • Top 10 Requirements :- As the Name states most important requirements used to lined up first.
  • Numerical Assignment :- In Numerical Assignment prioritization technique stakeholders used to provide Numerical value to each requirements.

While assigning the values 1 is the lowest value and 5 is the highest value for any requirement. According to the value the requirements used to get prioritized.

  • MoSCoW :-  MoSCoW is the most important and widely used prioritization technique in the business Analysis and Software Development to establish a common understanding with stakeholders.

According to the importance which is decided by the MoSCoW analysis all the requirements used to get delivered to the Product Owner.

Full form of MoSCoW  :-  Must, Should, Could and Would
M:- Must have this requirement to meet the business needs ( Mandatory)
S :- Should have this requirement if possible, but project success doesn’t rely on this ( Of High Priority )

C :- Could have this requirement if it does not affect anything else in the Project ( Preferred but not Necessary )

W :- Would like to have this Requirement later, but it won’t be delivered at this time ( Can be postponed and suggested for future execution )

About Alok Kumar

Check Also

Explain SRS and Its Key Elements

Introduction: Clear and concise communication is the cornerstone of successful software development projects. Software Requirement …

Leave a Reply

Watch Dragon ball super