New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Scrum PSM-II Exam - Topic 1 Question 84 Discussion

Actual exam question for Scrum's PSM-II exam
Question #: 84
Topic #: 1
[All PSM-II Questions]

You are the Scrum Master for three Scrum Teams working on the same product. There is a single Product Backlog that all three Scrum Teams select from. Management is eager to improve the productivity of the teams and wants to standardize velocity across all three teams so that they can see how each team is delivering value. When responding to management, which two statements are appropriate?

(choose the best two answers)

Show Suggested Answer Hide Answer
Suggested Answer: C, D

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.


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.''

by Carry at Jul 03, 2025, 02:12 PM

Limited Time Offer

25%

Off

Get Premium PSM-II Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Sheron
2 months ago
Velocity doesn’t equal value, that’s a key point!
upvoted 0 times
...
An
2 months ago
Totally agree, incentivizing based on velocity is risky.
upvoted 0 times
...
Jarvis
3 months ago
Wait, so we can't compare teams at all? That seems off.
upvoted 0 times
...
Talia
3 months ago
Standardizing velocity might help, but it’s not the whole picture.
upvoted 0 times
...
Marjory
3 months ago
Velocity is unique to each team, can't standardize it!
upvoted 0 times
...
Graham
3 months ago
I vaguely recall a practice question about how velocity should be used for planning, not for comparing teams. So, D seems like a solid choice.
upvoted 0 times
...
Nan
4 months ago
I feel like option C makes sense because velocity doesn't really measure value directly, just the amount of work done.
upvoted 0 times
...
Cassi
4 months ago
I think I read somewhere that incentivizing teams based on velocity could lead to unhealthy competition, but I'm not sure if that's always the case.
upvoted 0 times
...
Carli
4 months ago
I remember discussing how velocity is specific to each team, so standardizing it might not really reflect their actual productivity.
upvoted 0 times
...
Omega
4 months ago
Standardizing velocity across teams could help with comparisons, but I'm not sure it's the best way to understand value creation. I'll need to weigh the pros and cons.
upvoted 0 times
...
Lucina
4 months ago
Velocity is definitely a useful metric, but I agree that it doesn't directly translate to value creation. I'll need to consider that carefully.
upvoted 0 times
...
Catalina
4 months ago
Incentivizing teams based on velocity could backfire and lead to teams gaming the system. I'm not sure that's the right approach.
upvoted 0 times
...
Eun
5 months ago
Hmm, this is a tricky one. I'll need to think carefully about the relationship between velocity and value creation.
upvoted 0 times
...
Julianna
6 months ago
Standardizing velocity? That's like trying to herd cats. Gotta love management's innovative ideas.
upvoted 0 times
Ona
5 months ago
Standardizing velocity? That's like trying to herd cats. Gotta love management's innovative ideas.
upvoted 0 times
...
Brande
5 months ago
B. Standardizing velocity across teams can help with understanding which teams are creating more value.
upvoted 0 times
...
France
5 months ago
A) Incentivizing teams based on velocity can boost the Scrum Team's motivation to create more value.
upvoted 0 times
...
...
Emilio
7 months ago
I believe C is important to consider, as velocity does not directly correlate with value.
upvoted 0 times
...
Gaston
7 months ago
Velocity and value? Hmm, I thought they were like oil and water. Guess management needs a crash course in Scrum fundamentals.
upvoted 0 times
Basilia
5 months ago
C) Velocity has no direct relationship with value.
upvoted 0 times
...
Sharee
6 months ago
A) Incentivizing teams based on velocity can boost the Scrum Team's motivation to create more value.
upvoted 0 times
...
...
Yan
7 months ago
Incentivizing teams based on velocity? Sounds like a recipe for disaster. Velocity is more like a unique snowflake, not a standardized metric.
upvoted 0 times
Dona
6 months ago
C) Velocity has no direct relationship with value.
upvoted 0 times
...
Hannah
7 months ago
A) Incentivizing teams based on velocity can boost the Scrum Team's motivation to create more value.
upvoted 0 times
...
...
Skye
7 months ago
I agree with D, velocity is unique to each team and should not be standardized.
upvoted 0 times
...
Crista
7 months ago
I think A is a good option because incentivizing teams based on velocity can boost motivation.
upvoted 0 times
...

Save Cancel