Skip to content
Browse
BABOK Guide
BABOK Guide
10. Techniques
Introduction 10.1 Acceptance and Evaluation Criteria 10.2 Backlog Management 10.3 Balanced Scorecard 10.4 Benchmarking and Market Analysis 10.5 Brainstorming 10.6 Business Capability Analysis 10.7 Business Cases 10.8 Business Model Canvas 10.9 Business Rules Analysis 10.10 Collaborative Games 10.11 Concept Modelling 10.12 Data Dictionary 10.13 Data Flow Diagrams 10.14 Data Mining 10.15 Data Modelling 10.16 Decision Analysis 10.17 Decision Modelling 10.18 Document Analysis 10.19 Estimation 10.20 Financial Analysis 10.21 Focus Groups 10.22 Functional Decomposition 10.23 Glossary 10.24 Interface Analysis 10.25 Interviews 10.26 Item Tracking 10.27 Lessons Learned 10.28 Metrics and Key Performance Indicators (KPIs) 10.29 Mind Mapping 10.30 Non-Functional Requirements Analysis 10.31 Observation 10.32 Organizational Modelling 10.33 Prioritization 10.34 Process Analysis 10.35 Process Modelling 10.36 Prototyping 10.37 Reviews 10.38 Risk Analysis and Management 10.39 Roles and Permissions Matrix 10.40 Root Cause Analysis 10.41 Scope Modelling 10.42 Sequence Diagrams 10.43 Stakeholder List, Map, or Personas 10.44 State Modelling 10.45 Survey or Questionnaire 10.46 SWOT Analysis 10.47 Use Cases and Scenarios 10.48 User Stories 10.49 Vendor Assessment 10.50 Workshops

10. Techniques

10.33 Prioritization

BABOK® Guide

10.33.1    Purpose

Prioritization provides a framework for business analysts to facilitate stakeholder decisions and to understand the relative importance of business analysis information.

10.33.2  Description

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. These priorities are used to determine which business analysis information should be targeted for further analysis, which requirements should be implemented first, or how much time or detail should be allocated to the requirements.

There are many approaches to prioritization. For the purpose of this technique, prioritization is classified into one of four approaches:

  • Grouping,
  • Ranking,
  • Time boxing/Budgeting, and
  • Negotiation.

When choosing a prioritization approach, business analysts consider the audience, their needs, and their opinions on the value a requirement or business analysis information brings to a stakeholder's respective area.

Business analysts revisit priorities and utilize different approaches when changes occur in the business environment, to the stakeholders, and to the business analysis information.

Figure 10.33.1: Approaches to Prioritization

image.png

10.33.3 Elements

.1   Grouping

Grouping consists of classifying business analysis information according to predefined categories such as high, medium, or low priority. Many requirements management tools support listing the priority category as an attribute of a requirement.

.2   Ranking

Ranking consists of ordering business analysis information from most to least important. Some adaptive approaches involve the explicit sequencing of requirements in an ordered list (a product backlog).

.3   Time Boxing/Budgeting

Time boxing or budgeting prioritizes business analysis information based on the allocation of a fixed resource. It is frequently used when the solution approach has been determined. Time boxing is used to prioritize requirements based on the amount of work that the project team is capable of delivering in a set period of time. Budgeting is used when the project team has been allocated a fixed amount of money. This approach is most often used when a fixed deadline must be met or for solutions that are enhanced on a regular and frequent basis.

.4   Negotiation

The negotiation approach involves establishing a consensus among stakeholders as to which requirements will be prioritized.

10.33.4 Usage Considerations

.1   Strengths

  • Facilitates consensus building and trade-offs and ensures that solution value is realized and initiative timelines are met.

.2   Limitations

  • Some stakeholders may attempt to avoid difficult choices and fail to recognize the necessity for making trade-offs.
  • 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.
  • Metrics and key performance indicators are often not available when prioritizing business analysis information; therefore, a stakeholder’s perspective of the importance may be subjective.