Community Blog

In today's vlog, we will explore the ingredients to use Scrum with User Experience (UX).

Hey hey hey. How's it going awesome people? I hope you had a great week and keeping excited. I have noticed that several Scrum practitioners around me think that writing the Product Backlog items as a user story is mandatory.

My experience tells me that IT industry has some huge problems! First, there are many products for a lot of money that do not make sense. Second, products are created that solve the right problems in the wrong way. Third, products are created that solve the right problems in the right way but are not "sexy" in the eyes of users. All these 3 problems are addressed by the so-called User Experience. Although I must say that this is an often confusing concept. Many people hearing User Experience mean User Interface, and this is only a part of the truth! UI design is included in UX, but UX is a much, much broader concept.

When (Patricia Kong - Product Owner of Enterprise Solutions at Scrum.org) taught me how to combine the chocolatey-goodness of Evidence Based Management with the hazelnutty-goodness of Hypothesis Driven Delivery, I was ecstatic! "AHA!", I says to myself.

Many thanks to attendees at my PAL-E workshop in London on 26-27 October who reviewed & debugged my change story for "what is organizational agility?"

Este artículo es la segunda parte de otro donde hablaba de como integrar el trabajo de los especialistas de UX y los desarrolladores de software.

Tanto el desarrollo de software Agile como el diseño de experiencia de usuario (UX) tienen como objetivos comunes entregar antes sistemas más usados y valiosos para el cliente.