Q: 6
What technique helps a Scrum team to prioritize a large, flat backlog? Note: There are 2 correct
answers to this question.
Options
Discussion
B and C could work too, right? MOSCOW helps teams prioritize what's must-have or nice-to-have, so I'd pick B instead of A. Not sure why A is better here unless they're forcing hierarchy.
I don’t think it’s B. A and D fit better since they both help add structure, whereas MOSCOW can be a trap here.
A and D tbh. Both create hierarchy out of a flat backlog, not just prioritize. MOSCOW (B) is just about ranking but doesn't add any structure for slicing or grouping. If you see 'structure' mentioned, it's usually A and D.
B and D? MOSCOW (B) seems valid for prioritization, and D helps structure. Not certain A beats B without seeing more context.
B and D? MOSCOW (B) helps rank stuff, and story mapping (D) does too.
B , since MOSCOW gives a clear way to sort backlog items by must-have/should-have and I saw similar logic in a practice test. Not 100% but seems pretty useful for prioritization. Open to pushback though.
Pretty sure it's B and D. MOSCOW (B) is a standard method for prioritizing, and user story mapping (D) is used for breaking down large backlogs. Saw similar logic in practice questions, but not 100% if that's what SAP expects.
Its B and D for me. MOSCOW covers prioritization pretty well, and user story mapping (D) is a classic technique too. That’s what I’ve seen in the SAP guides and practice questions, but maybe A is more about structure than pure prioritization? Let me know if you disagree.
C or D? MOSCOW (B) is a trap here since it's about priority ranking, not creating structure. Pretty sure A and D both help turn a flat backlog into something manageable, but not 100% if A is enough alone. Thoughts welcome!
D imo, also A fits. Both give structure to a big flat backlog. Not totally sure B should count since MOSCOW's more for ranking priorities, not breaking stuff up. Disagree?
Be respectful. No spam.
