# Question: Why Do Reference Stories Helps With Pointing Poker?

## What does number 13 refers to in planning poker?

As Fibonacci sequence is used, the cards have numbers – 1, 2, 3, 5, 8, 13, 21, 34, etc.

These numbers represent the “Story Points”.

Each estimator has a deck of cards.

The numbers on the cards should be large enough to be visible to all the team members, when one of the team members holds up a card..

## Who invented story points?

Ron JeffriesRon Jeffries was quoted recently “I’m not sure if I was the inventor of story points, but if I am, I’m sorry”. Story points seemed a good idea at the time. They grew more complex and took over our lives, making them harder. If you’re using story points, you’re doing it wrong.

## Are story points linear?

Story points are linear (otherwise it would be impossible to use them as a measure of velocity). However the scale is non-linear, to stop people arguing over whether something is a “5 or a 6” – by using a psuedo-fibonacci sequence, you automatically account for the vagueness of estimation.

## Why is story pointing important?

Story points give more accurate estimates, they drastically reduce planning time, they more accurately predict release dates, and they help teams improve performance.

## Which options describe benefits of planning poker?

BenefitsRelative. One of the immediate benefits of planning poker is that it allows you to estimate tasks relative to one another. … Equal voice. Another benefit is that this style of estimating gives everyone on the team an equal voice. … Equal contribution.

## What is a reference story?

Reference stories are documented work samples that provide Fibonacci guidance for a team or organization. Note that last part: for a team or organization. Unlike other concepts, you can’t Google for a universally applicable 5. Instead, it is a shared and adhered to estimate representation for a group.

## Why are story points bad?

Story points estimates can encourage a number of bad behaviours. They can encourage teams to “game the system” by continually increasing their estimates. This seems to increase velocity, but is fake and makes a mockery of the process.

## How do you explain story points?

Story points are a unit of measure for expressing an estimate of the overall effort that will be required to fully implement a product backlog item or any other piece of work. When we estimate with story points, we assign a point value to each item. The raw values we assign are unimportant.

## Why does Scrum use Fibonacci?

The reason for using the Fibonacci sequence is to reflect the uncertainty in estimating larger items. A high estimate usually means that the story is not well understood in detail or should be broken down into multiple smaller stories. … The Scrum Product Owner presents the story to be estimated.

## What is the reason to use planning poker in Scrum?

The reason to use planning poker is to avoid the influence of the other participants. If a number is spoken, it can sound like a suggestion and influence the other participants’ sizing. Planning poker should force people to think independently and propose their numbers simultaneously.

## How many hours is a story point?

Story Points represent the effort required to put a PBI (Product Backlog Item) live. Each Story Point represents a normal distribution of time. For example,1 Story Point could represent a range of 4–12 hours, 2 Story Points 10–20 hours, and so on. This time distribution is unknown during estimation.

## How many story points is a sprint?

It also subtly takes the focus off of swarming and puts attention toward a developer per story. 5 to 15 stories per sprint is about right. Four stories in a sprint may be okay on the low end from time to time. Twenty is an upper limit for me if we’re talking about a Web team with lots of small changes to do.

## What does the coffee cup mean in planning poker?

coffee breakThe coffee cup, or teacup card represents a “coffee break” request. Often, planning meetings can run long, and this is a way for players to request a break to eat, rest, or grab a cup of joe!

## Why do story points use Fibonacci?

Many agile teams use story points as the unit to score their tasks. The higher the number of points, the more effort the team believes the task will take. The Fibonacci sequence is one popular scoring scale for estimating agile story points. In this sequence, each number is the sum of the previous two in the series.

## How many hours is 3 story points?

Some teams try to map the story points to hours – for example two story points correspond to a task that will take 2-4 hours, and 3 story points can be mapped to tasks from 4 to 8 hours long, and so on.

## When should you do poker planning?

When should we engage in Planning Poker? Most teams will hold a Planning Poker session shortly after an initial product backlog is written. This session (which may be spread over multiple days) is used to create initial estimates useful in scoping or sizing the project.

## Does the product owner estimate user stories?

While the Product Owner doesn’t actually participate in the estimation itself (e.g. he doesn’t get to vote during Planning Poker), he is part of the estimation process so that he can answer questions about the stories being estimated, help the team refactor stories, or adjust the Product Backlog priorities in real-time …

## Where did story points come from?

Story points were invented as supporting beams for the bridge between business and development that would later be called agile. They started with a very good concept that wasn’t there before: The story.