Agile Masterclass: Agile for Project Management - Introduction to Estimation

The lecture introduces the concept of estimation in agile development, contrasting it with traditional methods. Traditional estimation focuses on task-based efforts measured in hours, while agile estimation evaluates business value and complexity using story points. Agile estimation is relative, revisited in iterations, and considers factors like business value, complexity, risk, and dependencies. A hypothetical example of painting a house illustrates agile estimation, emphasizing the importance of relative sizing and categorizing user stories into story points.

What is the primary purpose of estimation in planning?

• To provide an exact calculation

• To make an educated guess

• To avoid any guesswork

• To ensure complete accuracy

In traditional estimation, what is typically estimated?

• Business values

• Efforts required for tasks

• Relative size of tasks

• Complexity of user stories

What unit is used in agile estimation to measure the complexity of a user story?

• Days

• Story points

• Weeks

• Hours

How does agile estimation differ from traditional estimation in terms of focus?

• Agile focuses on exact hours

• Agile focuses on fixed scope

• Agile focuses on relative size

• Agile focuses on absolute time

What is a key characteristic of agile estimation regarding plans and estimates?

• They are revisited in every iteration

• They are fixed once done

• They are only revised at the end

• They are never revised

In the hypothetical example, why is the kitchen estimated at eight points?

• It is easy to paint

• It is complex due to plumbing

• It is the smallest room

• It is the largest room

Which factor is NOT considered when estimating the size of a user story in agile?

• Exact time

• Risk

• Complexity

• Business value