C: Velocity has no direct relationship with value. This is a true statement, as velocity is a measure of

the amount of work done by a Scrum Team in a Sprint, not the value or quality of that work. Velocity

can vary depending on many factors, such as the size, complexity, and priority of the Product Backlog

items, the skills and experience of the Developers, the Definition of Done, and the Sprint length.

Therefore, velocity is not a reliable indicator of value creation or team performance.

D: Velocity is the amount of business functionality that a Scrum Team creates in a Sprint. It is unique

to that team and used as an input to Sprint Planning. This is a true statement, as velocity is a team-

specific metric that reflects how much business functionality the Scrum Team can deliver in a Sprint.

Velocity can help the Scrum Team to forecast how many Product Backlog items they can select for the

next Sprint, based on their past performance and current capacity. However, velocity is not a goal or

a target for the Scrum Team, and it should not be compared across teams.

Reference:

Professional Scrum Master II Course, page 15: “Velocity is a measure of how much work a team can

complete in a given time period. It is usually expressed in terms of story points or function points per

Sprint.”

Professional Scrum Master II Course, page 16: “Velocity is not a measure of value or quality. It does

not tell us anything about the usefulness, usability, or desirability of the product increment.”

Professional Scrum Master II Course, page 17: “Velocity is unique to each team and depends on

many factors, such as the size and complexity of the work items, the skills and experience of the

team members, the definition of done, and the length of the Sprint.”

Professional Scrum Master II Course, page 18: “Velocity can be used as an input for Sprint Planning,

to help the team forecast how much work they can realistically accomplish in the next Sprint.

However, velocity is not a goal or a target for the team, and it should not be used to compare or

evaluate teams.”