Cycle that represents Scrum and UX work together

Question

PSU assessment query:

What is the best cycle representing Scrum and UX work together, out of following, according to Scrum?

I think, option 1, can be best answer but not sure as can't find any evidence on Scrum.org.

I confess to be quite unsure as to how "UX = User Experience Design" has anything to do with, or any possible conflict with, "project management." ("Scrum" or otherwise ...) — Mike Robinson, Commented Aug 27, 2020 at 18:28
Assessment tests are only as good as the test designers, and it's not always possible to know what they have in mind as the "correct" answer. In formal Scrum, UX is never a separate activity, so trying to make it separate or sequential is an anti-pattern. — Todd A. Jacobs, Commented Aug 28, 2020 at 13:27

Undry · Accepted Answer · 2020-08-26 13:42:28Z

2

Answer is 2.

For both Scrum and UX you do the following steps:

answered Aug 26, 2020 at 13:42

Undry

1371 bronze badge

Add a comment |

Ashok Ramachandran · Accepted Answer · 2020-08-23 09:23:11Z

Scrum is founded on empirical process control theory, or empiricism

Here is a detailed justification of the above by Ken Schwaber, who jointly developed the Scrum framework with Jeff Sutherland.

The Three Pillars of Empiricism are:

Transparency: Significant aspects of the process must be visible to those responsible for the outcome
Inspection: Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances
Adaptation: If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted

I am not that familiar with the UX cycle. Based on the above, you can try and figure out which option fits best.

Seb StLeonards · Accepted Answer · 2020-08-29 12:08:36Z

"Build then Measure then Learn" - It sounds to me like Lean. Not Scrum and UX.
"Plan then Do then Check then Review" - Is it not PDCA with a tweak? The 'act' is replaced with 'review' to give it a scrumish feeling, but it is not Scrum and not UX.
"Discovery then Sprint Delivery then Sprint" - Whatever it is, has nothing to do neither with Scrum nor with UX.
"Sprint Planning then Design then Development then Test then Sprint Review" - This one combines Scrum events with a cross-functional delivery process which includes UX.