When adopting a new way of working, it’s natural to use what you currently know as a starting point, and to frame questions about the new thing you are learning using the terminology and perspective of the old way of working.
Among Agile teams, especially those with a strong UX focus, “MVP” has become part of the everyday din of project discussion. A typical conversation might go something like this: Yeah, we’re working on our MVP right now.
In the first part of this two-part series, we talked about what Stories are, their relationship to Personas and Story Maps, and factors to consider when writing stories.
If you are a UX designer who wants to quickly get up to speed with integrating Agile and UX, there are few better places to start than with User Stories.
Together with members of the Agile Experience Design LinkedIn group, I created a survey on the State of Agile UX.
Imagine yourself walking down a fictional hall in a fictional office building and passing two different offices. In the first office sits a UX designer, busily plugging away at a deck of wireframes, preparing to review them with the rest of the team. In the second office sits another UX designer, also busily plugging away at a deck of wireframes, preparing to review them with the rest of the team.
One of the most consistent patterns I see among those integrating UX and Agile is a business-as-usual approach to Personas, i.e.
This last weekend, a group of about 30 UX designers, developers, and leading thinkers in the Agile UX space (Jeff Patton, Ward Cunningham, Alan Cooper, Lane Halley, Desiree Sy, and William Pietri among others) met at Cooper in San Francisco to talk about the power and the challenges of integrating the Agile and UX disciplines.
Designing a user experience is usually considered synonymous with the work of designing the part of a system users will directly interact with.