Section 2 Basic components

Question 1 of 20

1. Question

What is the overriding goal for an agile project?

To deliver a working solution on time
To deliver the appropriate level of documentation
To deliver a good return on investment
To deliver well-structured maintainable code

Question 2 of 20

2. Question

Which of these describe 2 uses for velocity?

As a measure of progress and to provide visible proof of progress
As a measure of progress and to identify problem team members
To keep the Agile coach happy and to comply with agile rules
As a way of justifying late delivery and to avoid individual blame

Question 3 of 20

3. Question

An Agile estimate must be able to?

Provide information for different timeframes
Provide low-level details
Provide plenty of graphics
Provide the name(s) of the estimator(s)

Question 4 of 20

4. Question

Why does an agile estimate need to allow for features to be dropped?

Because delivering 100% of the solution is an unlikely outcome in Agile
Because expecting delivery of a 100% solution is unreasonable
Because testing always takes longer than expected
Because agile estimates are always wrong

Question 5 of 20

5. Question

Which statement is correct for the estimating style used in an agile estimate?

It reflects the level of uncertainty
It is always the same
It has been approved by the quality team
It must be fun and engage the team

Question 6 of 20

6. Question

Which statement describes use of Story Points?

Story point are a good way of sizing components of a solution
Story points are directly associated to time e.g. 1 point = 1 hour
Story points are a good way of dividing up the work for the team
Story points are useful for covering up areas of uncertainty

Question 7 of 20

7. Question

Which of these statements is INCORRECT?

Velocity is used to understand which team members are underperforming
Velocity is used in planning to predict delivery
Velocity is used to measure progress
Velocity is used to provide visible proof of progress

Question 8 of 20

8. Question

When does Velocity work best?

When Sprints are the same length and the team is stable
When Sprints are the same length and the risks are low
When the team is stable and high-performing
When there is technology available for creating Burn-down graphs

Question 9 of 20

9. Question

What is the major benefit of combining story points with velocity?

This combination supports planning and transparency
This combination helps hide problems
This combination avoids forcing the team into making a formal commitment
This combination supports precise plans based on accurate details

Question 10 of 20

10. Question

How can a starting velocity be calculated?

From decomposition of a few stories or using commitment-based planning for a full sprint
From decomposition of at least 50 stories
By doing detailed analysis on the backlog
By using commitment-based planning for the next increment

Question 11 of 20

11. Question

Which of these statements defines how commitment-based planning works?

The team take stories into a sprint one at a time and stop as soon as they have no more capacity
The project manager calculates what the team can achieve in a sprint and the team commit to deliver these in the given timeframe
The business representative states the sprint goal, and the team commit to work overtime, if necessary, to achieve it
The team agree a mixture of easy and simple stories for the sprint and commit to get these delivered

Question 12 of 20

12. Question

What constitutes an ideal day?

The time when team members can focus exclusively on work to deliver the sprint goal
Typically this is counted as 7.5 hours
It is a day without any interruptions
It is a day when the project manager is out of the office

Question 13 of 20

13. Question

What is agile estimating and planning based around?

Varying horizons
Always using small teams
T-shirt sizing
Experienced estimators

Question 14 of 20

14. Question

Which statement is true?

When assigning points, avoid relating these directly to hours or days (in your mind or in discussion)
When assigning points, always relate these directly to hours or days (in your mind and in discussion)
When assigning points, avoid choosing numbers in the outer ranges
When assigning points, always be guided by the experts in the team

Question 15 of 20

15. Question

Which statement describes calculated velocity?

Calculated velocity is a risk until actual velocity has been proved
Using a calculated velocity is a bad practice and should always be avoided
Calculated velocity is unnecessary, provided the team do proper requirements analysis
Calculated velocity is the responsibility of the Product Owner

Question 16 of 20

16. Question

Which statement is true?

Agile plans, horizons and levels of confidence are intrinsically linked
Agile plans, horizons and levels of confidence are not linked
A high level of confidence is necessary before creating a plan in agile
Agile expects detailed plans to be based on long-term horizons

Question 17 of 20

17. Question

Which points are fixed for an Agile approach?

Time, cost, quality
Features, time , cost
Quality, working hours, precision
Features, time, team size

Question 18 of 20

18. Question

What is actual velocity based on?

A deepening understanding
A skilled, experienced team
Zero assumptions
Having enough contingency

Question 19 of 20

19. Question

How does an agile approach handle design?

Enough Design Up Front (EDUF)
No Design Up Front (NDUF)
Big Design Up Front (BDUF)
Design is irrelevant, because agile is an evolutionary approach

Question 20 of 20

20. Question

When will actual velocity be reassessed?

After completion of each sprint and delivery of each increment
At the end of project review
When senior stakeholders ask the deadline to be brought forward
Never

Estimating for Agile

Exams

Participants 33

September 13, 2022

Exam Summary

Information

Results