2. Deliver the “Need“
2
You may add a hundred items to the wish list on your
shopping app! But, do you buy all at one go?
You pick and purchase only those that you need immediately
Similarly, in agile development, you only pick the features that
benefit your end user at a given moment
3. Prioritization- The Savior
3
Agile teams pick features to develop and deliver a working software in short time-boxes called iterations
How do teams decide on
which features to work ?
How do they know what will
add value ?
Among various factors available, we will look at five major ones that typically governs prioritization
Its simple!
Teams prioritize!
How should teams
go about it?
5. Factor 1
5
Agile teams prefer features that are easily churned out in a given time-box and are budget friendly
Before you get that product out, you should know who your customers are and better way to find
that out is by creating 'Personas'!
Personas are the ultimate beneficiaries of your product!
Understanding personas and their challenges, will open up the scope for creating features that may
enhance customer experiences
Customer Satisfaction
6. Factor 2
6
Teams deliver feature after
feature without realizing
the value rendered
In the midst of this mechanical
run, the enterprise's strategy
and goals go for a toss
To avoid this, prioritize, include
capabilities that add value and
are more aligned to the overall
strategic goals
Business Value
7. Factor 3
7
Prioritizing small features
before the big ones is very
important
This will not only reduce the cost of
implementation, but also reduce
the cost of delay in realizing them
Value and time taken along
with the cost, collectively
affects prioritization
Cost of Delay
8. Factor 4 & 5
8
Optimization is the most effective way of exciting and
retaining the existing user base
Hence, during prioritization, it is always to better to
analyze the impact of any feature on the number of
existing users.
Many backlogs could be associated with varying
degrees of risk by affecting the overall business
Prioritizing high risk backlogs early in the
development cycle will be cost effective and reduce
implementation risk
Implementation riskImpact on the No of Users