3. Priorities Requirement

Question 1

Purpose

Answer 1

To rank reqs in the order of relative importance

Question 2

Description

Answer 2

Priority can refer to the relative value of a req, or to the sequence in which it will be implemented
Prioritization is ongoing process, priorities changing as the context changes
Prioritization us a critical exercise that seeks to ensure the max value is archieved

Question 3

Inputs

Answer 3

Reqs + designs

Question 4

Elements 1

Answer 4

1. Basis for prioritization
   Factors:
   Benefit
   Penalty
   Cost
   Risk
   Dependencies
   Time sensitivity
   Stability
   Regulatory or policy compliance

Question 5

Elements 2

Answer 5

2. Challenges of prioritization
   Each sh may value something different, may be conflict amongst sh
   Sh may indicate priority to influence the results to their desired outcomes
   Different type reqs not all response on criterial in some way. Need sh make tread-off in prioritization

Question 6

Elements 3

Answer 6

Comm3. Continual prioritization
The SH may re-prioritize yet again

Question 7

Guidelines and tools

Answer 7

Biz constraints
Change strategy: provide cost timeline value
Domain knowledge
Governance approach
Reqs architecture
Solution scope
Reqs mng tools/ repository

Question 8

Techniques

Answer 8

Backlog mng
Biz cases
Decision analysis
Estimation
Financial analysis
Interviews
Item tracking
Prioritization
Risk analysis and mng
Workshops

Question 9

Stakeholder

Answer 9

Customer
End user
Implementation sme: provide input relating dependencies base on technical constrant
Project manager: use input to project plan
Sponsor
Regulator

Question 10

Outputs

Answer 10

Reqs + design ( prioritized)