Relative Estimation

Description

IIBA Business Analysis Agile Business Analysis (Agile BA Techniques - Requirements Management) Flashcards on Relative Estimation, created by Charlotte P on 15/10/2021.
Charlotte P
Flashcards by Charlotte P, updated more than 1 year ago
Charlotte P
Created by Charlotte P almost 3 years ago
1
0

Resource summary

Question Answer
What is the purpose of Relative Estimation? Relative Estimation is used to make future predictions based on past experiences, knowledge, complexity, size & uncertainty required to complete backlog items.
At what Horizons is Relative Estimation used? ALL HORIZONS
What improves over time with Relative Estimation? The ability to accurately estimate as new information is discovered about capabilities and capacity.
Story points are provided as a numeric value to each story using __________. Story point is a reflection of the amount of _______ needed to deliver the story. 1. Fibonacci scale 2. effort
Describe 'Planning Poker' A team review each of the backlog items or stories. Each team member chooses a number. If there is alignment within 1 degree of numbers, one of them is chosen and the team moves on. If there is wide variation in the numbers, the discussion continues to uncover new information to help.
Describe 'Silent Sizing' The team prepares the backlog items on individual cards and line them up on a wall/table. Each team member selects a card and places it on the wall/table. This is repeated for all of the cards, creating a linear line, with the ‘smallest’ cards at one end and largest at the other. Breaking points are then identified to group similarly sized items. Fibonacci scale story point then assigned to each group.
STRENGTHS of Relative Estimation? - Simple & reliable - Accuracy improves over time - Sizing approaches are very collaborative and likely to have a positive impact on teams
WEAKNESSES of Relative Estimation? - As it is based on historical data, having to estimate a completely new item can be challenging & accuracy is questionable - Changes to team composition may impact team velocity & capabilities - Numbers provided are team specific - confusing for stakeholders? - Stakeholders may focus on outputs (time taken) rather than outcomes (value)
Show full summary Hide full summary

Similar

Minimum Viable Product (MVP)
Charlotte P
Impact Mapping
Charlotte P
Story Elaboration
Charlotte P
User Stories
Charlotte P
Planning Workshops
Charlotte P
Kano Analysis
Charlotte P
Job Stories
Charlotte P
Story Decomposition
Charlotte P
Story Mapping
Charlotte P
Retrospectives
Charlotte P
Reviews
Charlotte P