Section 10 Best practice and Top tips

Question 1 of 10

1. Question

What should an estimator NOT be forced into?

Providing detailed estimates, when the information available is very high level
Providing detailed estimates for sprints
Providing early estimates, before proper analysis has taken place
Working with others when creating your estimate

Question 2 of 10

2. Question

What is required to meet the purpose of an estimate?

Create the estimate at the right speed and at just the right level of detail
Create the estimate in the right format and as quickly as possible
Select people you respect to help you create the estimate
Run a workshop with the experts to create the estimate to the appropriate level of precision

Question 3 of 10

3. Question

Why is it helpful to relate estimates to business requirement wherever this is practical?

Because if priorities change, it is easier to revise the estimate
Because the best hope for success is to follow the agile rules
Because this will ensure sufficient requirements analysis will be done
Because the top agile priority is to deliver all the requirements

Question 4 of 10

4. Question

What is the recommended attitude towards learning from experience?

Use it to build value from lessons learned, and do not view it as a criticism of an earlier estimate
Accept this is an integral part of agile and recognise it just has to be endured
Use it as an opportunity to re-emphasise the reasoning behind your initial estimate
Volunteer to facilitate the retrospective so you can manage any potential criticism of the estimate

Question 5 of 10

5. Question

Which statement is true with regards to estimating for agile?

You will never be 100% certain, so your estimate is unlikely to be 100% right
You should strive for 100% certainty, so that your estimate is more likely to be right
Working with a group raises the likelihood of 100% certainty, so should be encouraged
Protect yourself against any future criticism

Question 6 of 10

6. Question

What does best practice for agile estimating recommend?

Estimate using more than one technique and estimate in groups
Always estimate using at least 2 techniques at every stage in the lifecycle
Estimate Bottom-up as your default choice
Always cross-check your estimates using Analogy, Top-down and Bottom-up

Question 7 of 10

7. Question

What is the effect of presenting a precise estimate when you are uncertain?

It gives a false impression of confidence
It helps reassure the team that you are a skilled estimator
It reduces discussions about your estimate
It ensures the estimate is treated with respect

Question 8 of 10

8. Question

What attitude should be taken towards challenges to assumptions?

They should be encouraged and welcomed
They should be actively discouraged
They should be ignored
They should be written-up on Post-It notes and then dealt with using a facilitated workshop

Question 9 of 10

9. Question

What is the outcome of using more than one estimating technique?

Where the results are significantly different, at least one result is wrong, maybe both are wrong
It shows the estimator is using due diligence
It ensures the estimate is fully accurate
Where the results are significantly different, it is very frustrating

Question 10 of 10

10. Question

During the project what drives revision to an agile estimate?

Review of progress, of risks and of assumptions
Review of team morale and of management satisfaction
Review of the Burn-up charts
Review of the progress reports