Relative Sizing in Agile Methodology

Fred Master Pasqua, a certified Scrum trainer, explains the concept of relative sizing using analogies with glasses and car washing. He discusses the importance of comparing tasks relative to each other rather than estimating exact time or effort. The video also covers the modified Fibonacci sequence for story points and highlights common pitfalls teams face when using relative sizing.

What is the primary focus of relative sizing in Agile?

• Comparing tasks to each other

• Determining the number of team members needed

• Measuring exact time for tasks

• Assigning monetary value to tasks

In the example with glasses, what is the main challenge presented?

• Determining the exact amount of water

• Finding the right type of glass

• Measuring the temperature of the water

• Calculating the weight of the glass

How do teams determine the relative size of tasks?

• By assigning random numbers

• By comparing tasks to a baseline

• By estimating the time required

• By using a fixed scale

What is a modified Fibonacci sequence used for in Agile?

• To calculate project costs

• To determine team size

• To estimate relative sizes of tasks

• To schedule meetings

What is a common pitfall teams face when using relative sizing?

• Comparing tasks in isolation

• Using too many baselines

• Focusing only on time estimates

• Ignoring team input

In the vehicle example, what is the main factor considered for relative sizing?

• The speed of the vehicle

• The amount of work required

• The type of fuel used

• The color of the vehicle

How does relative sizing help in predicting time?

• By determining the number of team members needed

• By setting deadlines

• By allowing comparison of task sizes

• By providing exact time estimates