Creating an Agile culture does not happen overnight. Everybody in the company has to embrace the new mindset. This category shares the knowledge, and some of our secrets, to being successful with Agile Software Development.
by Olga Morales.
When you collaborate in an open source project it is likely to be asked to make a fork of one repository. A fork is a copy of the project in your GitHub account. This duplicate allows you to freely experiment with changes without affecting the original project.
There is a problem when you fork a project, it is not going to have the last changes made in the original one, so in order to avoid problems when you try to push your changes it is better to keep your fork up to date.
by Matt Perez.
In a Forbes article, David Marquet pointed out the origin of the word “company,” … the com- in company is derived the same root that gives us companion and comrade and the pan- is derived from the word for bread. So a company describes a group of people breaking bread together. David Marquette And that’s […]
by Matt Perez.
According to Wikipedia, an asset is, “Anything tangible or intangible that can be owned or controlled to produce value. … Simply stated, assets represent value of ownership that can be converted into cash.” Given this definition, can we agree then that “asset” is a really crappy way to refer to people? Of course, most people […]
by Paola Trujillo.
When we were children the only limits were our dreams and imagination. Before we realized it, we were all grown up and making our lives fit other people’s expectations.
You can build your career to satisfy others, or you can take charge of your life and build a legacy.
It’s your choice!
by Misael León.
The key to thrive in the competitive environment is without a doubt to focus on the User Experience.
People simply won’t pay money for a product that doesn’t fit their needs.
Don’t let people’s misconceptions and lack of understanding keep you from doing User Research in your Agile Team to create world class products.
Agile teams can quickly adapt to the change in user preferences. And User Research is the tool to sense this pulse.
There are plenty of misconceptions that stand in the way. Here are some practical recommendations to make them work together.
At the core of UX sits User Research, a set of techniques to understand user behaviors, needs, and motivations through observation and measurement.
There are specific User Research activities that can help you at every stage of the product development process,
The challenge is to identify which one is right for the problem you want to solve and to allocate sufficient time to run it and get value from it.
Test small and often
When you introduce User Research to an Agile Team, you’ll hear things like this,
These myths are the result of a “just ship it” mentality. Work is rewarded based on how many features are shipped and not on how much we are changing user behavior towards our business goals.
Typically under Agile there is no distinct discovery step. Discovery research and requirements gathering are oftentimes conflated as one taks. Development is guided by a mock that may or may not reflect what users really want.
Typically this “discovery” work does not have an owner. There is no dedicated time to explore users’ motivations, expectations, or how they use your product. At best, product owners come up with design specifications barely in time before development starts.
To incorporate User Research activities in your Agile process the whole team must shift to a user-centric vision of the product. Change begins when learning about users is at the core of their work. Yes, you will still ship features, but these will be aligned to change user behavior and improve the product.
All of a sudden the work changes. Now the goal is to reduce tickets, not shipping a particular feature. This means that the team will explore options like creating a moderator role. They can research that simple idea with customers.
Test small and often.
This is another step to shift from a culture of delivery to a culture of learning.
Create a space where this discovery work can be done
You can also recruit users familiar with the product so they don’t spend tons of time going through the learning curve.
You could schedule regular research sessions with users. This makes it a weekly routine and everybody knows it’s “User Research day.”
In the end what matters is applying the right technique to find the answer to your question.
Ideally, instruct others to run the sessions themselves. Initially they could take notes, speak to the customers, and ask single questions. Over time they will get so used to the process and will be capable of running in on their own.
Atlassian did a great work building their own User Research lab. Theirs is by no means an expensive or fancy lab. It’s more about creating a space where this discovery work can be done. More than that, it is creating the right team mentality around user problems.
Check out how Atlassian built its lab
You can easily run User Research activities remotely.
Conduct remote usability tests through video calls. You can record the action in the screen using Quicktime, while still seeing the reaction on your user’ face.
Create affinity diagrams using virtual sticky-notes in Google Slides or similar. While not ideal, this workaround is pretty helpful when the other option is to have no UX Research at all.
Run tree tests, card sorting, surveys, and more with Optimal Workshop.
Prioritize your backlog with FeatUR‘s customer satisfaction survey.
It will take time, but you can help your team integrate the voice of the customer into their work. The time spent making this happen is worth every second.
Everybody from your team will benefit,
You cannot create meaningful solutions without customer input. And people simply won’t buy products that don’t fit their needs.
For More Information…
To learn more about how to integrate User Research and Agile, don’t miss the upcoming UX Webinar.
by Monica Tye.
More companies are incorporating flex time and integrating digital nomads into their workforce. This trend is especially true for the software industry.
Nevertheless, working remotely poses some challenges as well; I know this first hand. I then turned to one of my favorite Slack communities, Women In Tech. We discussed the challenges of working remotely as well as ways to overcome them.
Here’s what we came up with.
by Matt Perez.
As in, I have the ultimate power, but I’ll share some of it with you. In this form, empowerment is just another form of control. In a self-managed organization all “power” emanates from its purpose and mission. People come to work with all the power they need. Give yourself a chance to grow. Change your […]
by Judith Garcia.
Getting into a new project is challenging. Daunting even.
It’s not enough to know your way around the tech stack. But something that will probably be entirely new for you will be the project’s domain language.
This is what I went through when I transitioned from healthcare to the travel industry.
by Matt Perez.
As in, fiat hierarchy. The kind that’s all about power. There are plenty of hierarchies in nature, all around us. Including the ones encased in our skulls, made up of neurons. The good hierarchies are dynamic and adaptable. Stifling hierarchies are fixed, static, and serve only to encode the pyramid of “sacred rulers.” Give yourself […]
All your info is kept private. We'll never spam you.
Send us your resume and we’ll guide you trough the process of landing your dream job.