Techniques for Estimation - Zen Ex Machina

In Planning Poker, you choose the number that best represents your individual effort for the Product Backlog item. *

True

False

If during the Sprint, one team member finds that a feature is worth 5 Story Points and not 2, should they update the size in the Sprint Backlog or not? *

No. An estimation provides a forecast of what the size is likely to be, not how much is remaining in retrospect.

Yes. This ensures that estimations are always accurate.

Yes, and the team should discuss the change in the Retrospective in order to provide more accurate estimations in Sprint Planning in the future.

An individual team member shouldn't change the size of a feature without input from the rest of the team.

Velocity is defined as (choose the BEST answer) *

The effort needed to complete a Product Backlog item.

The amount of Product Backlog items that can be turned into an Increment of Done in a Sprint.

The sum of all the Story Points completed in a Sprint.

The sum of all the effort by team members during a Sprint.

Which statement BEST applies to estimation and accuracy. *

P-Days are more accurate than Planning Poker-based estimation

Planning Poker techniques provide more accurate estimations than P-Days

Apply Planning Poker estimates to all tasks.

Planning Poker-based estimations are more accurate than estimations based on hours or days.

Who should provide estimates? *

The Product Owner

The Scrum Master

Team members – the people who will do the work

Stakeholders

Managers

Work on a feature worth 5 Story Points is almost complete by the end of the Sprint, but did not meet the Definition of Done. At Sprint Review, the Product Owner decides to prioritise it for the next Sprint. What should the team do? *

Give the team partial credit for the work done by estimating the amount of work complete and add those Story Points to the team's velocity for that Sprint

Assess the amount of work outstanding and re-estimate based on the remainder. The team doesn't get partial credit for velocity for work that isn't Done.

Leave the estimate the way it is and return it to the Product Backlog.

Leave the estimate the way it is and put it directly into the Sprint Backlog for next Sprint.

When using Planning Poker *

Estimate the time taken and then choose the corresponding size.

Allow the experts in the team to provide their estimate first.

Esimate size first, and then derive time.

The number in Planning Poker represents (select ALL that apply). *

Effort needed to meet the Definition of Done

Complexity

Risk

Hours

The number of dependencies

What are the advantages of using hours in estimation? Choose the BEST answer. *

People are used to estimating in hours so it's easier to introduce than a new method like Planning Poker and Story Points

Hours directly relate to costs, so financial management by the Product Owner is easier.

Estimation by hours is useful due to familiarity but isn't a longer term strategy for accurate forecasting.

Hours isn't useful to an agile team. They should always use Story Points.

During Sprint Planning, 1/2 the team provide a size of 5 and the others provide an estimate of 8. What size should the team select? *

Size 6 1/2. This is mid way between the two sizes.

Select either 5 or 8 based on a team conversation. These are size categories, not a measure of time that can be divided in half.

Size 5.

Size 8, due to optimism bias.