0% found this document useful (0 votes)
26 views39 pages

BA Requirements Prioritization

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
26 views39 pages

BA Requirements Prioritization

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 39

BUSINESS ANALYSIS

FOUNDATION
COURSE
REQUIREMENTS
PRIORITIZATION
ABOUT ME
Nataliia Piatkevych
▪ Senior Business Analyst at SoftServe

▪ 12 years in IT, > 6 years as BA

▪ CСBA from IIBA

▪ Background: QC Engineer and Business


Development Consultant
GROUND RULES

1 Any time is the right time to ask your question


in the chat
2 If you face any technical issues (no
presentation, no sound, etc.), let me know

3 You are welcome to turn on the camera

4 Keep your mic muted


WHAT ABOUT YOU

1. Do you have experience in prioritizing requirements?


a. Yes, I have such experience

b. No, but I know theoretically

c. No, no knowledge so far


WHAT ABOUT YOU

2. Have you heard about any prioritization techniques?

If yes, drop the names in the chat.


AGENDA
1. What is prioritization
2. Basis for prioritization
3. Challenges of prioritization
4. Methods and Techniques
1. Classification
2. Game-based
3. Value-mapping
5. Tips
6. Takeaways
7. Q&A
WHAT IS
PRIORITIZATION?
WHAT IS PRIORITIZATION
➢ Prioritization is the act of ranking requirements to determine their
relative importance to stakeholders (BABOK)

➢ Prioritization is a process used to determine the relative importance


of business analysis information. The importance may be based on
value, risk, difficulty of implementation, or other criteria (BABOK)

➢ Prioritization of the backlog is an ongoing activity to select which work


items go into upcoming iterations and which items are discarded from
the backlog. The priorities are assigned to backlog items (Wiegers)
BASIS FOR
PRIORITIZATION
BENEFIT

the advantage that accrues to


stakeholders as a result of requirement
implementation, as measured against
the goals and objectives for the change
PENALTY

the consequences that result from not


implementing a given requirement
COST

the effort and resources needed to


implement the requirement
RISK

the chance that the requirement


cannot deliver the potential value, or
cannot be met at all
DEPENDENCIES

relationships between requirements


where one requirement cannot be
fulfilled unless the other requirement is
fulfilled
TIME SENSITIVITY

the 'best before' date of the


requirement, after which the
implementation of the requirement
loses significant value
STABILITY

the likelihood that the requirement will


change, either because it requires
further analysis or because
stakeholders have not reached a
consensus about it
REGULATORY OR POLICY COMPLIANCE

requirements that must be


implemented in order to meet
regulatory or policy demands imposed
on the organization, which may take
precedence over other stakeholder
interests
CHALLENGES OF
PRIORITIZATION
CHALLENGES OF PRIORITIZATION
➢ Each stakeholder may value something different

➢ Difficulty in characterizing something as low priority

➢ Some stakeholders may attempt to avoid difficult choices and fail to recognize
the necessity for making trade-offs

➢ Priority is indicated to adjust the result to the subjectively desired outcome

➢ Can’t remember why it was a must-have” or “How can you call this Low
Priority?”

➢ Whoever screams the loudest, gets priority

➢ Long time-consuming discussions on low value features

➢ The solution team may intentionally or unintentionally try to influence the


result of the prioritization process by overestimating the difficulty or complexity
of implementing certain requirements
QUIZ

1. You are working on requirements prioritization. Requirement


1 is dependent on requirement 2, requirement 2 is
dependent on requirement 3. Requirement 3 was given a
priority ‘medium’, and requirement 2 was given priority ‘low’.
Which factor influenced prioritization the most?
a. Cost
b. Dependency
c. Penalty
d. Value
QUIZ

2. You are Business Analyst working on the regulatory project.


Lead BA asks you to prioritize requirements in order to meet
the regulatory demands imposed on the organization over
other stakeholder interests. What factor is influencing the
prioritization?
a. Time Sensitivity
b. Cost
c. Risk
d. Penalty
QUIZ

3. You are Business Analyst on the project. The stakeholders


have difficult time coming to a consensus for one of the
requirements, and hence there is high probability that this
requirements will change. You decide to give it lower priority.
What factor influenced your decision the most?
a. Risk
b. Benefit
c. Stability
d. Dependency
PRIORITIZATION
METHODS AND
TECHNIQUES
TYPES OF TECHNIQUES

1. Classification

2. Game-based

3. Context evaluation / Value mapping


CLASSIFICATION

• High-Medium-Low
• 1-2-3-4-5
• MoSCoW
• Now, Next, Later
• Dots scoring/voting

MoSCoW
GAME-BASED

• Prioritization poker
• 100$ test (Buy a feature)
VALUE MAPPING

• Priority quadrants
• User Story mapping
• Weighted Shortest Job First (WSJF)
• Kano Analysis
• Systemico Model
• RICE/ ICE
PRIORITY QUADRANTS EXAMPLES
Action Priority Matrix Eisenhower matrix
WSJF EXAMPLE
KANO MODEL EXPAMPLE
EXPAMPLES
Systemico Model RICE
HOW TO APPROACH PRIORITIZATION
Depending on circumstances (e.g., available stakeholder time or the nature of information
available), different set of techniques can be used.

• which must have clearly defined:


• criteria on which to compare options
• processes to vote/score/rank
• roles and processes to make the final choices.
TIPS & TAKEAWAYS
TIPS
➢ Make it visual, tactile, collaborative

➢ Use the same level of abstraction (e.g. per release,


quarter, sprint)

➢ Agree on category definitions first

➢ Show suggested priorities

➢ Use a combinations of techniques

➢ Document the approach in Requirements Management


plan
TAKEAWAYS
➢ Deliver the most valued items to the business at the
earliest

➢ Rework by the development team is minimized by


assigning more volatile requirements lower priority

➢ Prioritization task is an ongoing activity and need to


keep a constant eye on the drivers that may cause the
priority change
USEFUL READING
1. More about Dot voting: https://dotmocracy.org/
2. MoSCoW technique for Agile projects:
https://www.youtube.com/watch?v=QfZo9cxnQgY
3. Luke Hohmann. Innovation Games: Creating Breakthrough Products
Through Collaborative Play.
4. More about KANO: https://foldingburritos.com/kano-model/
5. More about SYSTEMICO: https://barryoreilly.com/2012/08/21/the-
systemico-model/
6. More about FEATURE BUCKET approach to prioritization:
https://adamnash.blog/2009/07/22/guide-to-product-planning-three-
feature-buckets/
7. More about Grid Analysis:
https://www.mindtools.com/pages/article/newTED_03.htm
Q&A
THANK
YOU!

You might also like