Agile Story Point

What do story points represent in Agile?

• Number of hours to complete a task

• Relative effort or complexity of a task

• Cost of the task

• Number of team members required

Story points are typically assigned based on which factors?

• Complexity, effort, and risk

• Team member availability

• Deadline date

• Budget

Which Agile estimation technique uses cards with Fibonacci numbers?

• Planning Poker

• MoSCoW prioritization

• Waterfall scheduling

• Gantt charting

True or False: Story points are the same as hours.

• True

• False

What is the primary benefit of using story points instead of time estimates?

• Easier to track employee hours

• Helps account for uncertainty and complexity

• Simplifies billing clients

• Increases task duration

If a story is assigned 8 points and another story is 2 points, what does this imply?

• The 8-point story will take four times longer than the 2-point story

• The 8-point story is roughly four times more complex or effortful than the 2-point story

• The 2-point story is more important
  

• Nothing — points have no relation

What does “velocity” in Agile refer to?

• Number of stories completed per sprint

• Speed of team members typing

• Number of hours worked daily

• Amount of budget spent

Which of the following is NOT a good practice when assigning story points?

• Estimating as a team

• Using relative comparison

• Assigning story points based on individual preference only

• Revising points after learning more

Which of these is a common scale used for story points?

• 1, 2, 3, 4, 5

• Fibonacci sequence (1, 2, 3, 5, 8, 13...)

• Powers of 10

• Roman numerals

What should you do if two stories seem equally complex but one has more unknowns?

• Assign the same story points

• Assign higher story points to the one with more unknowns

• Ignore unknowns in estimation

• Estimate based on deadlines only