One of the agile Principle says "Our highest priority is to satisfy the customer through early and continuous delivery of valuable software". Business Value Prioritization is an essential activity to achieve this.

1. New Trends in
Requirements prioritization
Business Value Prioritization in agile way
Raghavendra Veluru
CSM, PMI-ACP, SPC
Scrum Coach
rveluru@yahoo.com
Mobile +91 988 611 1772

2. Welcome
 OBECTIVES
What are the Sources of Requirements?
Why do we need prioritize the requirements?
What are the Requirement Prioritization
Schemes?
How do I check the Health of Requirement?
Q &A
 INTENDED AUDIENCE
Practicing Agile
2

3. Ice Breaking … …
3

4. Source of Requirement
 Sources of Requirements
◦ Customer Pain-points
◦ Regulatory Compliance
◦ Competition
◦ Innovation
4

5. 5

6. Usage of Features in a
System
http://theagileexecutive.com/2010/01/11/standish-group-chaos-reports-revisite
6

7. The Project Triangle Turned
Upside Down
http://www.applitude.se/2011/02/the-project-triangle-turned-upside-down/
7

8. Usage of Features in a
System
http://theagileexecutive.com/2010/01/11/standish-group-chaos-reports-revisite
8

9. Prioritization
 Prioritization enables
◦ To Flex the Scope
◦ To meet Budget and / or Timeline
◦ Objectives while retaining a useful set of
functionality
 We can Prioritize a Requirements @
◦ Release planning
◦ Iteration Planning
9

10. Value Prioritization Case
Study
 How a leading Credit Card Service
Company saved millions using value
based Prioritization
Card
Holder
Merchant
Acquire
r
Credit Card
Company
Issuer
10

11. Type Non Zero Zero Total %ge
Very
Complex
12 4 16 75
Complex 20 12 32 63
Mid
Complex
15 6 21 71
Simple 28 87 115 24
Very
Simple
16 25 41 39
40%
60%
Checks Used
Non Zero Zero
Very
Complex
7% Mid
Complex
14%
Complex
10%
Simple
51%
Very
Simple
18%
Algorithm Complexity
Value Prioritization Case Study…
11

12. RELEASE
DATE
Sprint 1 Sprint 2 Sprint 3 Sprint 4
Achieved 0 0 5 21
Cumulative 26
Rollout 1
Sprint 5 Sprint 6
29 26
81
Rollout 2
Sprint 7 Sprint 8
34 29
139
Rollout 3
Sprint 9 Sprint 10
33 40
212
Rollout 4
Sprint 11 Sprint 12
8
225
Rollout
5
Value Prioritization Case Study…
12

13. Product Backlog
Vision
 Build Robust Finance System for Fictitious
Technologies LLC.
Theme Build A robust Payroll System
so that finance team will help employees in processing their pay roll
Establish proper communication with the employs so that they will be
satisfied with the pay roll calculations and continue to focus on their key
business value of software development
Build A Robust Invoice System
Build A Robust Time Tracking System
13

14. Product Backlog
Epic  Pay slip Generation
 As an employee I need to see my pay slip so that I can
understand the summary of my salary at a glance
Epics Earnings
As an employee I need to know the earnings made in this month
so that I will know how much the base salary is.
Deductions
As an employee I need to know the deductions made in this
month so that I will identify the areas to save tax
Monthly Summary
As an employee I need to know summary of no of pay days,
government tax number so that I can validate and correct
14

15. Product Backlog
User Stories  Deductions – Provident Fund
 As an employee I need to know how much money credited
into my PF account so that I can validate with PF department
 Acceptance Criteria:
 1. PF = 12% of Basic + Special Allowance + Employee Self
Contribution
 2. Need to display in deduction pane
 3. Need to be credited to PF account through NEFT
 Deductions – Local Government Tax
 As an employee I need to know the amount of tax deducted
under local government tax so that I can visualize the
contribution
 Acceptance Criteria:
 1. Deduct $100.00 if gross salary is > $100000.00 else Deduct
10.00
 2. Should not deduct for temporary employees
15

16. Product Backlog
16

17. MoSCoW
Could
Should
Must
Could
Should
Must
MoSCoW (Must Have, Should Have, Could Have, Won’t Have)
Recommended not to sped more than 60% effort for Must Haves for a project,
with 40% Shoulds and Coulds.to avoid risk to the success and predictability of
the project,
17

18. Kano Model
Developed by Professor Noriaki Kano,
Fulfil Needs
Customer Satisfaction
http://en.wikipedia.org/wiki/Kano_model
Delighter
s
Exeter s
“WoW”
Wants
“Satisfiers”
Total Satisfaction
Total Dis
Satisfaction
Don’t Do Do Very Well
18
Time

19. http://innovagile.blogspot.in/
rveluru@yahoo.com