.png)
“Every action has an impact; choose wisely the impact you want to have.”
In agile if you consider DevOps as a developer that connects with IT or how infrastructure is managed, then you are wrong. DevOps involve a lot more than that. It involves the entire software development process, different departments intertwined together with their roles and work.
The customer always cares about your companies’ user experience and not about the number of developers your organization has. The companies user experience (UX) is a break-and-make element of your organization. It is the part of agile companies’ continuous process that designs the feature and product based on the user's need and matches the design to bring meaningful innovation that reduces their pain points. In a rapid burst of development, the UX fails to provide the same quality it generally would, bringing Lean UX into action.
Lean UX design is a culture, mindset, and process which embraces lean-agile methods. As traditional UX is focused on the deliverables the lean UX is more focused on the experience under design. The main objective of lean UX is to have as quick feedback as possible to make quicker decisions. In agile the main focus is to have rapid and iterative cycles in which lean UX plays an important role as it minimizes these cycles ensuring generated data to be used in each iteration.
Origin of Lean UX
The origin of Lean UX in agile can be traced from the lean manufacturing system which is used to eliminate the waste from the productions. At first in the Toyota production system, a lean manufacturing approach was used that helps the automakers to have substantial growth for the company. Further from this agile lean UX took key ingredient of eliminating by-product of the process that not provide customer’s any value and applied it to user experience.
Benefits of Lean UX
It helps in validating the core products and main features by the target customers.
It shows the importance of early testing and hence validation of the success of a product.
It improves team position and also team member's position between colleagues
It motivates the team and brings out positive reactions in team members for abandoning the previous version of the product and being eager to work on new concepts.
It makes the teamwork faster and smarter by speeding the design phrases go through.
Early Feedback with lean UX provides better products satisfying customers.
Why there is need for Assumption in Lean UX
Traditional UX projects are based on the deliverables and captured requirements. In lean UX the scenario is a bit different, team members don’t focus on the detailed deliverables but the process of product development for better changes of the product. So it becomes necessary for agile teams to ditch requirements and focus on the problem statements which will lead to an assumption for further use in creating a hypothesis. With help of assumption, it becomes easy to generate a common understanding of the idea and a way to get started with the agile project. The assumptions are further changed when team members get a proper understanding of the project. Team members are always aware at the start that the assumption they are making may be wrong and need to be changed with a better understanding of the projects.
To create assumptions team members gather together and start to discuss the problem further allowing brainstorming the idea for problem-solving. In this process, the general questions are tried to answer for better understanding and problem-solving. Questions are as mentioned below and many more can be added as per requirement.
Who the users are?
What’s the basic aim to create this product is?
What time product should be used?
A situation where this product can be used?
What is the product’s most important functionality?
Risk of product delivery?
There can be many assumptions created for the product and many solutions to each problem. When there are such cases of many solutions to problems or assumptions which are practically difficult to handle. Then it is better to go with the prioritization method. Prioritize the assumptions based on the risk it represents, consequences of its action, and understanding of the issue. More understanding and severe consequences of the problem is a higher priority.
Hypothesis in Lean UX
“The only way to test a hypothesis is to look for all the information that disagrees with it.”
In lean-agile methods hypothesis is created to test the assumptions. If we have already done the assumption we will create a clear hypothesis of it and try to find the evidence of it being true. If there is no way proving it right? Every point in lean UX is tested and finds evidence of it, if not found ay then it’s time to drop the idea.
In our upcoming article, we will learn more about agile lean UX principles and their foundation.
About Advance Agility
We, at Advance Agility, are the new-age Agile Coaching, Consulting and IT services company. We enable end-to-end Digital Transformation. Agile execution is integral to our being. We are doing SAFe implementation with small, medium and large organization across the globe. Our vision is to be the leading Agile execution player globally. To keep adding value at every process stage. We are on a mission to empower our clients, move from concept to cash in the shortest sustainable lead time by adopting human centric approach to business agility. Embracing the change is in our DNA. Things that keep us apart are Quicker and Seamless execution with End-to-end gamut of services. Our Global presence and Stellar Track Record give us an edge over our competitor.
Connect with us at advanceagility.com to learn about SAFe and SAFe Implementation. Write to us at contact@advanceagilty.com for any agile training or consulting needs. We are always looking for competent agile trainers as well. So if you are a good trainer or want to become one, do get in touch with us to that we can learn, grow and achieve together.
Optimize your Value Stream with SAFe DevOps Practitioner Certification
.png)
Comments