Agile Project Management User Stories and Estimation 2

Question 1

In the INVEST mnemonic for good user stories, what does the 'N' stand for?

Accepted Answer

Negotiable

Answer

Necessary

Answer

Numbered

Answer

Nominal

Question 2

A team estimates a story they have never done before and has no comparable past work. Which technique best handles this uncertainty?

Accepted Answer

A spike to gather information first

Answer

Assigning the highest story point value

Answer

Skipping the story entirely

Answer

Estimating in exact hours

Question 3

What is the primary purpose of relative estimation with story points rather than absolute time?

Accepted Answer

It compares sizes without forcing precise time commitments

Answer

It guarantees deadlines are met

Answer

It removes the need for a backlog

Answer

It lets managers track individual performance

Question 4

During Planning Poker, two team members reveal very different estimates. What should happen next?

Accepted Answer

The high and low estimators explain their reasoning, then re-vote

Answer

Average the two numbers automatically

Answer

The Scrum Master decides the value

Answer

The lower estimate always wins

Question 5

Which item is typically NOT written as a user story?

Accepted Answer

A technical infrastructure or non-functional requirement

Answer

A new customer-facing feature

Answer

An end-user workflow improvement

Answer

A reporting capability for users

Question 6

What does a story being 'Estimable' (the E in INVEST) require?

Accepted Answer

The team understands it well enough to size it

Answer

It has a fixed deadline

Answer

It is broken into exactly five tasks

Answer

It is assigned to one developer

Question 7

Why are Fibonacci-like sequences (1, 2, 3, 5, 8, 13) commonly used for story points?

Accepted Answer

Larger items carry more uncertainty, so gaps widen

Answer

They are easier to add

Answer

They match exact hours of work

Answer

They limit teams to six stories per sprint