Story points are used in agile estimation to measure the size of user stories based on business value, complexity, risks, dependencies, and amount of work. Estimation by analogy compares new stories to previous similar stories estimated in story points. The triangulation method estimates a story between two other stories of known points. T-shirt sizing uses informal sizes like XS, S, M, L, XL instead of points. Affinity mapping first prioritizes and orders stories, then groups similarly sized stories to assign common story point values.

1. Agile Estimation
Anilkumar ARS

3. Purpose

4. Target

5. Traditional Estimation Vs Agile Estimation

13. Story Points are the measurement unit to estimate the size
of a user story, on the basis of its.
1.Business Value
2.Complexity
3.Risks
4.Dependencies
5.Amount of work
Influencing Factors of Story Point :

14. Planning Poker

20. With estimation by analogy in Agile, story sizes are compared with other stories. This relative sizing
approach is helpful when making assumptions relevant to agile estimations.
For instance, a company already estimated user story A for two weeks. Now, if they come across a
user story B that is twice as large as user story A, they will assign it a larger estimation number.
For effective Agile estimation using the analogy, the triangulation method is widely used. According to
the triangulation method, the user story is estimated against similar intent user stories that have
already been estimated.
For example, if the story is bigger than the story estimated at six-story points and smaller than the
story estimated at 10 — estimating it at eight will be a good strategy.
Analogy use cases
•If retrospectives are a part of the process
•Among teams that have an excellent mutual understanding
•Among highly experienced teams
Analogy Estimation

21. In this t-shirt sizing Agile estimation technique, the items
are estimated in standard t-shirt sizes (i.e., XS, S, M, L,
and XL). This is more of an informal but creative
technique, and numbers can be assigned to each user
story and categorized under different t-shirt sizes for better
understanding.
T-Shirt size estimation use cases
• Running rough estimations
• The team is new to Agile estimation
• There are large backlogs
• Running early-stage estimation
. T-Shirt Size Estimation

22. Affinity Mapping
Step 1: Backlog grooming and prioritization
As per regular Scrum rules, the product owner needs to prioritize the backlog prior to the estimation meeting.
Step 2: Relative estimation
This is the main task in affinity estimation. Firstly, each user story is written down on a card and placed in a pile.
Each member of the development team then takes turns to place a card in a line on the table or adjust the
position of a card already on the table. At the end of this step, there should be a continuous line of user stories
from those requiring least effort on the left and those requiring most effort on the right. At this stage, it makes no
difference how much more difficult the user stories are from each other. The important thing is that the stories
are ordered relative to each other.
Step 3: Story-point grouping
We can now happily say that the user stories on the left are easier than those on the right. Therefore, it’s highly
unlikely that the user stories on the left will be 21 story points or the stories on the right will be 1 story point. We
also know that if the easier story is 3 points, anything to the right of it must be equal to, or greater than, 3 story
points. With this information we can then divide the cards into similarly sized groups and assign a story-point
value that can be applied across all user stories in that group.

23. THANK YOU