Existen algunos puntos que puedes profundizar para incentivar de una mejor manera la comunicación con tu cliente como desarrollador o desarrolladora web.
Comunicación precisa
La comunicación con tu cliente será siempre lo más importante. La precisión y claridad de estas interacciones determinarán la calidad del producto que tengas que desarrollar.
Customer requirement / Understanding the customer
In the beginning, some information might still be unclear. Go back to the customer and clarify.
Get info on requirements. Think of everything you need before you start building the software.
Veamos un ejemplo:
What questions do you think you could ask if we take bicycle online sales as an example?
How many different types of bicycles does the software have to support?
Should the software allow any changes to color or model once the bicycles have been purchased?
Does the software have an administrator interface to make changes?
Lluvia de ideas
Una “lluvia de ideas” es una reunión donde especialmente se debaten ideas del trabajo que se tiene que realizar o cómo se debe realizar este. Ninguna idea es mala, el equipo tiene que discutirlas para encontrar las mejores.
A session designed to express ideas about the project design. Any idea can be expressed.
Promote the right atmosphere to avoid having a foggy or muffled session.
The objective of brainstorming is to get good requirements that will create great results and great software.
You can also try brainstorming and observation as a complement to brainstorming to gather good requirements.
Two heads are better than one and four heads are better than two, as long as people can contribute without criticism. Carlos Arriaga
Historias de usuario
Las historias de usuario son representaciones visuales e individuales de una única tarea.
Working, functional software is the primary measure of progress.
User stories help you sort out what is most important.
Your priority is to satisfy your customer through early and continuous delivery of valuable software.
User stories should describe one thing that the software needs to do for the customer, they must be short.
Written using language that the customer understands. Avoid using technical terms.
User stories must be written from the customer’s perspective. Let’s see an example:
As a user …
I want to …
So I can …
Estimaciones
Una estimación es para cuándo estará terminada una determinada tarea.
After your initial requirement capture stage, you will have clear user stories.
The customer will then want to know those stories will be built.
How long will it take to complete the project? (Estimation)
Your estimate is the sum of all the time you take to build the user stories.
Your customer will want to know the total duration of the project.
Let’s see an example:
User story 1: Catalog creation (5 days)
User story 2: Selecting a bicycle (2 days)
User story 3: Selecting a color (2 days)
TOTAL: 9 days
El pensamiento de diseño
El “pensamiento de diseño” es un proceso efectivo para resolver problemas que te ayuda a crear grandes soluciones.
Design thinking encourages people to look for new alternatives to problems. Is successful because it focuses on the necessities of the user.
It’s about understanding the context and culture of the stakeholders involved.
Solutions are found using direct observation and data, which produce User Stories relevant to end-users.
Once the research is conducted, new ideas are generated to solve the problem easily. These ideas result in rapid solutions and/or prototyping.
The process of ideating early prototyping and testing guarantees quick and cheap solutions to bugs.
Existen muchas técnicas que puedes implementar para optimizar el desempeño laboral y la comunicación con el cliente. Normalmente, cada equipo implementa lo que funciona para el mismo, no necesariamente deben utilizar todas las técnicas, pero si explorar las mismas y buscar las mejores para mejorar el trabajo.
