Section 4 Estimating Styles

Question 1 of 15

1. Question

What is another term for Bottom-up estimating?

Estimating by decomposition
Estimating by committee
Just in time estimating
No blame estimating

Question 2 of 15

2. Question

Which statement describes Bottom-up estimating?

Time-consuming
Appropriate for whole-project estimates
The most useful style at the start of a project
Too slow ever to be useful for agile work

Question 3 of 15

3. Question

Which estimating style is most appropriate for a medium horizon?

Top-down
Bottom-up
Middle-out
Analogy

Question 4 of 15

4. Question

What can an analogy-based estimate be used for?

Supporting early business decisions
Supporting assignment of individuals to the team
Justifying getting equipment for the team
Planning a Sprint

Question 5 of 15

5. Question

Which is the highest level of Top-down estimating?

Analogy
Grouping
Task breakdown
Decomposition

Question 6 of 15

6. Question

Which statement does NOT describe Estimating by decomposition in the early stages?

It takes time but is worth all the effort
It is too slow to support fast decision-making
It can be misleading, because its precision implies a certainty that does not exist
It will be based on many assumptions, which may later prove invalid

Question 7 of 15

7. Question

What are Top-down estimates based on?

Just enough understanding to estimate size without analysing every detail
Detailed knowledge about the team members and their individual skills
An expectation that additional contingency will be added on to ensure a good outcome
An expectation that it will be changed by senior management

Question 8 of 15

8. Question

Which statement about a Top-down estimate is correct?

It has inherent uncertainty, so is often stated as a range
It has inherent certainty, so is usually presented without contingency
It has too many assumptions to make it reliable
It forms a good basis to underpin a contract

Question 9 of 15

9. Question

What is stated as a specific use for a Bottom-up style of estimating?

It can be useful for validating a Top-down estimate
At Post-project, it is useful for assessing where the analogy estimates were wrong
It provides the level of certainty people expect for bigger horizons
In the early stages of a project, it is a good team-building exercise

Question 10 of 15

10. Question

What is captured every day by the team members to support Inspect and Adapt?

Accurate and up-to-date information
A timesheet
Minutes of the daily Scrum
The latest holiday plans

Question 11 of 15

11. Question

When is analogy the most appropriate style to use?

When the speed to produce an estimate is more important than the precision
When the precision of the estimate is the most important factor
When bidding for a commercial contract
When there are no risks involved

Question 12 of 15

12. Question

Which of these statements is NOT correct?

Each estimating style is only effective in one phase of the lifecycle
Each style can be considered more appropriate for certain stages of the lifecycle
Styles can be combined to cross-check results
Styles can be combined to improve accuracy

Question 13 of 15

13. Question

What is the best basis for using analogy to create an estimate?

Previous experience of similar work
Self confidence
Certification in maths
A web search

Question 14 of 15

14. Question

Which statement is true?

Top-down is used when there is neither the time nor the information available to carry out a Bottom-up estimate
Top-down is used when the estimator is too busy to worry about minor details
Top-down is used to provide a very rough size of a solution as quickly as possible
Top-down is chosen because the team enjoy Planning Poker

Question 15 of 15

15. Question

Which of these is a benefit of Top-down estimating?

The speed of estimating combined with the focus on the full scope
The focus on the detail combined with the use of Planning Poker
The ability to create precise estimates
Being able to estimate as a team, since this means no individual gets the blame later