Tag Info

Personally speaking, lean UX is not a type of UX strategy, it is more like the business strategy which accommodates the fundamental UX principles. In UX Design you Design -> Prototype -> Validate as is, but when you do this in sync with other development units in the organization, it becomes lean UX. Anyways, here are some of the links/books/what-have-you. ...

I would strongly recommend reading this excellent article on smashing magazine on Lean UX,to paraphrase the article: Lean UX is the practice of bringing the true nature of our work to light faster, with less emphasis on deliverables and greater focus on the actual experience being designed. Traditional documents are discarded or, at the very least, ...

UX, along with all of the other disciplines involved in your project, should be involved from day one. The team should strive to work in parallel with each other as much as possible. To achieve this, it is imperative that the UX resource(s) participate in all daily Agile rituals and meetings. This is especially true for backlog grooming and prioritization. ...

My response may be biased because I run a pure UX research, strategy and design firm, but as UX practitioners, we're involved in agile projects at the very beginning. As zsiberian stated, getting ahead of development by 1-2 sprints is the only way to keep the process agile. UX involvement in the iteration planning session allows the user story definition ...

Agile seems to come in a variety of flavors, but the theory is all the same, and based on that theory, UX is part of the mix from day 1...as is business line owners, customers, IT, marketing, etc. I usually find the problem is when UX is still doing waterfall but dev is trying to go AGILE. Lots of UX teams still want to pump out piles of wireframes, which ...

From my own experience I would say you work in a parallel stream ahead and after Development and if you take it literally not in Agile Development at all. Why? Because in my understanding Scrum, which we do at my company, is about production and development in iterations. But tasks itself not. You take a single task and work on it until its finished. Then ...

I think there needs to be more clarification on this concept in general. Even reading some of the comments so far I’m getting confused when UX within Agile is equated with Lean UX. There's a gap there that isn't really addressed in most content on the subject. And I imagine that's just because it's a challenge in general for which I'm not sure there's a ...

An approach which I find very fitting on where the UX role should intervene in Agile (Scrum in this case) development is: In the product backlog, translating end-user feedback into specifications. In the sprint planning meeting, providing mockups so both the Team and Product Owner have a better idea of what will be built and how. At the end of each ...

Ideally it needs to start as early as the final stages of the opportunity pursuit when the UX lead is invited to the closing meetings with the potential client and has reviewed the SOW. That does two important things: gives you voice in conversations about scope, which in tern gives you heads up about project and what it's going to take. Christie - I know ...