Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Scaled Agile Exam SAFe-DevOps Topic 3 Question 31 Discussion

Contribute your Thoughts:

Bernadine
1 days ago
Haha, A) Maximum economic value? What is this, a Wall Street trading floor? Weighted shortest job first is all about getting stuff done, not making a quick buck.
upvoted 0 times
...
Goldie
4 days ago
B) Epics, Features, and Capabilities makes more sense to me
upvoted 0 times
...
Selma
9 days ago
I believe it's A) Maximum economic value
upvoted 0 times
...
Tegan
9 days ago
D) Proxy for job size, for sure. It's all about efficiency, my friends. Smallest tasks first, that's the way to beat the backlog blues.
upvoted 0 times
...
Ruth
10 days ago
I'm going with C) User business value. Prioritizing tasks based on their impact on the user is the way to go, isn't it? Gotta keep the customer happy!
upvoted 0 times
...
Kiley
15 days ago
B) Epics, Features, and Capabilities? Really? That's like mixing up apples and oranges. Weighted shortest job first is clearly about optimizing task order, not project management artifacts.
upvoted 0 times
Carmen
3 days ago
A) Maximum economic value
upvoted 0 times
...
...
Daniela
18 days ago
I think it's D) Proxy for job size
upvoted 0 times
...
Kris
24 days ago
C) User business value
upvoted 0 times
...
Lai
26 days ago
Hmm, I think D) Proxy for job size makes the most sense. Weighted shortest job first is all about prioritizing tasks based on their size, not economic value or user business needs.
upvoted 0 times
Skye
11 days ago
I think C) User business value could also be a possibility.
upvoted 0 times
...
Antonio
15 days ago
I agree, D) Proxy for job size is the correct option.
upvoted 0 times
...
...

Save Cancel