Section 1 Agile estimating fundamentals

Question 1 of 12

1. Question

Which statement is a correct description of an agile estimate?

A forecast of what outcome can be delivered for a given cost
A quote for what will be delivered and when
A forecast of which team will deliver the outcome
A fixed-price commitment to deliver the outcome

Question 2 of 12

2. Question

How does information in an estimate support the decision-making process?

It underpins the business case for doing the work
It provides certainty for a successful outcome
It allows the right team to be allocated
It ensures contingency is built in from the start

Question 3 of 12

3. Question

What is the value of an estimate in a commercial situation?

It helps customers understand what they are buying and when it will be delivered
It helps customers understand which individuals will be doing the work
It helps customers ensure the supplier takes all responsibility for the risks
It is a useful negotiating tool when problems occur

Question 4 of 12

4. Question

How does an agile estimate support delivery?

It supports forward planning and allows a team to assess what can be delivered at what point(s)
It supports retrospectives and allows a team to explain why problems have occurred
It supports Planning poker and Burn-up charts
It removes uncertainty and ensures delivery of the full solution

Question 5 of 12

5. Question

Which of these statements is true?

Even an estimate for what will be achieved in the next 10 minutes can be wrong
An estimate for a sprint will be fully accurate
An estimate for what will be achieved in the next 10 minutes will always be correct
Adding plenty of contingency ensures an estimate will be correct

Question 6 of 12

6. Question

What value comes from estimating collaboratively and collectively?

It ensures all aspects of delivery and business are taken into consideration
It ensures blame can be avoided
It ensures the novices within the team do not influence the outcome
It ensures that external influence on the estimate can be avoided

Question 7 of 12

7. Question

Who owns the risks associated with an estimate?

Ownership of risk sits with the business or the relevant management team
Ownership of risk sits with the team doing the estimate
Ownership of risk sits with the project manager
In agile everybody owns the risk

Question 8 of 12

8. Question

Why is it important to take ownership of the estimate?

If you are not part of creating the estimate, you will never fully commit to achieving it
If you are not part of creating the estimate, you feel left out of decisions
If you are not part of creating the estimate, you will feel like an outsider
If you are not part of creating the estimate, your contribution to the final delivery will not be acknowledged

Question 9 of 12

9. Question

How does agile support validation of the estimate?

Agile projects do this naturally throughout the lifecycle
Agile projects ensure every decision is a team-based one
Agile projects use sprints
Agile projects build in plenty of contingency

Question 10 of 12

10. Question

When should you estimate?

Only when necessary, to make a decision or to change direction
Every 2 weeks
At the start of the project and at each retrospective
Only when necessary, if senior management flag up a problem

Question 11 of 12

11. Question

What does the purpose of the estimate drives?

The time spent producing the estimate
The choice of estimator
The level of assumptions
The amount of contingency

Question 12 of 12

12. Question

Which of these sentences list 3 of the estimating principles?

Validate the estimate, Expect change and uncertainty, Know the purpose
Know the purpose, Take ownership, Avoid personal responsibility
Avoid risk, Expect change and uncertainty, Validate the estimate
Know the subject matter, Validate the estimate, Expect challenges