Home / BA / Improve Prioritization Using a Combination of Techniques

Improve Prioritization Using a Combination of Techniques

 

  1. Improve Prioritization Using a Combination of Techniques

. Prioritization is the most important stage after gathering all the business and functional requirement.

Is used for addressing the common also important requirement of stakeholders on the priority.

. There are mainly three technique used for prioritization which are mentioned below :

MOSCOW Technique –

In this technique requirements are classified as per their current importance in SDLC.

 

MUST – Mandatory ( Must meet to the business need of the organization )

Should – Of high priority ( should have this requirement )

Could – Preferred but not necessary ( if not this requirement is not addressed then no any impact on the application )

Would – Can be postpone and suggested for future execution ( will add this requirement in next version )

 

If we take example of online ticket booking application  :

There are following stages are included in this like Register, Login, Seat Allocation, Payment, Buy Refreshment, refreshment reserved to seats

 

Must – Register, Login

Should – Seat allocation, Make Payment

Could – Buy refreshment

Would – Refreshment reserved to seats.

 

Ranking :

 

In this technique you will rank the requirements on an ordinal scale.

We will give different numerical value to each requirement based on its importance.

 

KANO Techniques :

 

This technique is based on the satisfaction of the customer.

There are three factors in this technique

 

Basic factors – Dis satisfies

Performance factors – Satisfies

Excitement factors – Delighter ( Also called as a USP )

 

 

Also if we are working in Agile methodologies there are two technique which are helping in prioritizing the requirement.

 

  1. High BV :

BV stands for Business Value.

This business value shows the how much this user story is important for the business.

This business value ranges between 10 to 500.

Where are 500 is highest Business Value and 10 is lowest Business value.

This business value is rate by the client on the basis of their importance.

 

2 .  Low CP :

CP stands for the complexity points.

CP value shows the amount of effort or work has to be done by the scrum team to develop any user story.

This Complexity point ranges between 1 to infinity.

This complexity point is rated by the scrum developer.

 

So after gathering all the requirement by the BA, on the basis of high business and low complexity point scrum master will prioritize the user stories to deliver.

After prioritizing the requirements BA or scrum master finalized the Feature list.

Also we consult s Subject Matter Expert also for the prioritization.

 

If proper prioritization is not done while working on the project then that will leads to conflict between the client and developer.

Prioritization is used for smooth execution of task without any conflict.

And this is on going process on daily basis. If we Software development life cycle is of six month then  we prioritize the things on month basis and then on week and day so on.

Prioritization is done business analyst while discussing with the senior Business analyst or project manager.

About Sandeep Nandkumar Patil

Check Also

What is BRD? How is it different from SRS?

BRD stands for Business Requirements Document, whereas SRS stands for Software Requirements Specification. Both documents …

Leave a Reply

Watch Dragon ball super