I would add this (it's probably a subset/related to "know your user"):
-know the process
after having known your user I think you should get insights of the process/topic/environment where the software will be used. at the end the values you give are there (better performance, features...ease)
Yes, I'd include that in knowing your user. It's no limited to knowing who they are, but what they are doing. That's your process, and it's also required knowledge.
hi!
I agree with your points.
I would add this (it's probably a subset/related to "know your user"):
-know the process
after having known your user I think you should get insights of the process/topic/environment where the software will be used. at the end the values you give are there (better performance, features...ease)
do you agree?
Yes, I'd include that in knowing your user. It's no limited to knowing who they are, but what they are doing. That's your process, and it's also required knowledge.
yeah!
thanks for sharing