Section 6 Estimating When, Why, How and Who

Question 1 of 15

1. Question

In an agile lifecycle, when is using an Analogy-based estimate the best option?

To support very early thinking
When planning for development
For planning the deployment of the solution
When developing the solution

Question 2 of 15

2. Question

Which statement is correct?

Use Top-down (story point) estimating to roughly size the candidate list before the next sprint planning event
Use Top-down (story point) estimating to roughly size the agenda for the next retrospective event
Use Top-down (story point) estimating to plan for deployment
Use Top-down (story point) estimating to capture rough ideas in the early stages of the project

Question 3 of 15

3. Question

What is the most appropriate style of estimating to create a Sprint Plan for the next 2-4 weeks?

Bottom-up
Top-down
Analogy
Finger in the air

Question 4 of 15

4. Question

Which style is most appropriate for providing an estimate for the next increment?

Top-down
Analogy
Middle-out
Bottom-up

Question 5 of 15

5. Question

Which estimating style is often used to validate a Top-down estimate?

Bottom-up
Analogy
Maximum-precision
Story points

Question 6 of 15

6. Question

During Feasibility, which project-level role expresses the high-level need?

Business Visionary
Accountant
Business Auditor
Project Manager

Question 7 of 15

7. Question

Who estimates the list of candidate stories for the imminent sprint, to prepare for sprint planning?

The team
The developers
The project manager
The users

Question 8 of 15

8. Question

Which statement reflects correct agile behaviour when estimating for agile?

Collaboration at the heart, always engaging with project level roles and advisors as appropriate
Technology is key, take the lead from the technical experts
Be pessimistic, always expect the worst-case scenario
Control at the heart, driven by the managers and stakeholders

Question 9 of 15

9. Question

Which role works with the team to create more refined time and cost estimates from the initial high-level estimates?

The project manager
The senior tester
The most experienced developer
The Product Owner

Question 10 of 15

10. Question

When is the latest safe point in the lifecycle to start planning for Deployment?

During Evolutionary Development
During Feasibility
During creation of the business case
During the initial funding process

Question 11 of 15

11. Question

What estimating takes place informally during daily Scrums (Stand-Ups)?

Bottom-up
Top-down
Story points
Affinity estimating

Question 12 of 15

12. Question

What is covered by an estimate created during the daily Scrum?

The next 24 hours
The next Sprint
The next Increment (release)
The next Deployment

Question 13 of 15

13. Question

What of these options is NOT suitable to support the very early thinking on a project?

Story points
Analogy
Collaboration
Being uncertain

Question 14 of 15

14. Question

What describes a typical agile lifecycle?

Very early thinking, Iterative planning, Iterative development, Incremental deployment
A rough guess, some planning, building the solution, releasing the solution
Very early thinking, one-off planning, Iterative development, Incremental deployment
Analysis and Design, Iterative development, Retrospectives, Incremental deployment

Question 15 of 15

15. Question

What is a specific use for a Bottom-up estimate during Feasibility?

To plan activity for the next phase (Foundations)
To create a detailed plan for the sprints in this release
To raise the level of management confidence
To reduce the level of uncertainty for this project