Estimation and Velocity

Question 1

What estimation method does waterfall projects use to get an idea of project duration?

Answer 1

Bottom-up meaning all tasks are decomposed and then estimated.

Question 2

What is estimating in a Scrum project called Top Down?

Answer 2

Because you first do a gross level estimate at the high level. As features are known in detail JIT estimates are created for each sprint. JIT estimates are more accurate because the details are known at that time.

Question 3

What are 2 methods of estimating in scrum?

Answer 3

Planning Poker

T-shirt Sizes

Question 4

How is relative work effort compared to absolute time estimation?

Answer 4

Absolute time is used for waterfall method and is precise estimate.
Relative work effort compares 2 task to each other and their relative work effort.

Question 5

What is planning poker?

Answer 5

It is relative work effort estimation methodology that estimates time to complete a task. Fibonacci sequence is most often used.

Question 6

What are the common numbers of the Fibonacci Sequence?

Answer 6

1, 2, 3, 5, 8, 13, 40, 100.

Question 7

When using planning poker, what is the difference between a low number (1) and a high number (100)?

Answer 7

Lower number, the details are well known and more accurately estimated. Higher number indicates that the user story needs to be decomposed further.

Question 8

Why would the Fibonacci sequence have wider ranges as the numbers increase?

Answer 8

There is a wider difference so it is easier to place an item in a lower or higher number.

Question 9

During planning poker, what happens if all agree versus disagree on the estimate?

Answer 9

Agree, then this is the number assigned to the estimate. If they disagree, then the team discusses their differences to resolve to the same number.

Question 10

During planning poker, why are the cards shown at the same time?

Answer 10

Avoid anchoring which is when a person agrees with the first person who speaks or agrees with the person who expresses the most confidence.

Question 11

What is the definition of velocity?

Answer 11

Amount of work a team can produce from a single sprint.

Question 12

Is velocity tracked for an individual or team?

Answer 12

Team

Question 13

When tracking velocity, what should be considered about the dynamics of the team?

Answer 13

If members are coming and going on the team, the velocity is going to vary and will be challenging to measure.
Timeboxes must remain the same to make accurate measurement.

Question 14

What can happen if the velocity estimate is wrong?

Answer 14

Lead to inefficient use of time, missed deadlines, micromanagement, stressed workers

Question 15

What is technical debt?

Answer 15

Cost incurred when shortcuts are taken to deliver project results.

Question 16

Why would an organization accept technical debt?

Answer 16

Bringing a product to market quickly.
Product life cycle is short and running out of time.
Seek early feedback that help to avoid making mistakes

Question 17

Does a technical debt have interest?

Answer 17

Yes because the longer you wait to implement the full feature set, the potential of customers leaving for a competitor that has a fuller feature set.

Question 18

Is technical debt always intentional?

Answer 18

No, it may be poor engineering, insufficient testing or poor quality overall.
The organization may lose a key vendor or supplier.

Question 19

When would you not pay down technical debt?

Answer 19

Product nearing its end of life.

Backlog features are not meaningful to customers