Lean UX versus Agile UX
The basic concept of Lean UX is an inexpensive, analytics-driven approach to create a Minimum Viable Product (MVP), and drive the development of the MVP with creating a demand in the market using user feedback.
From the user's feedback interacting with this MVP, improvements are made in the development phase and then released again. Thus, the user's response is only measured after release and using the product. This approach unites product development and business through constant measurement and ensures a digital product can be created in a short period of time. The testing and validation of the product are done through three basic steps--build, measure, and learn.
Agile UX is derived from the agile methodology and incorporates short status meetings in regular intervals with cross-functional teams to improve communication. It's all about the collaboration of teams and the delivery of the product by uniting designers and developers during the product development cycle. What makes Agile UX effective is the fact that you're testing against fixed outcomes. You have full control over the amount of sprints needed to create a specific feature, and with each sprint you analyze, test, and reiterate every change made in the previous sprint. This ensures a continuous improvement of quality and refinement of the product.
It's natural to assume that if you adopt a Lean UX or Agile UX approach, it will replace traditional UX. On the contrary, these approaches complement the tradition UX and make it more flexible to fit into the dynamic environments we find ourselves in when developing digital products. To put this statement in context, let's briefly look at what tradition UX is. Tradition UX relies on the core principles of design and usability; first do all the research and groundwork, and then go into development.
Agile UX produces a more refined, high-quality product, while Lean UX produces several products that are less refined but refinement increases with each released. It seems that Agile UX is perfect, so why bother with Lean UX? The original agile methodology focuses on an improved smooth process for software development and, unfortunately, design was never included in this process. Agile UX is about building a product faster with less risk, despite what it looks like. So, Agile UX is not so perfect after all. A lot of companies use both interchangeably, depending on the project. Agile UX fits naturally into the agile culture of software development, and Lean UX brings in the inexpensive data-driven approach to improvements. There is no right or wrong way. Use the methodologies that work within your environment and your project to deliver the best product for the user.