Vai trò Product Owner đối với Việt Nam còn mới mẻ, chỉ mới vài năm trở lại đây, người ta mới bắt đầu nói về nó và nhiều công ty tuyển dụng bắt đầu cần những ứng viên cho vị trí Product Owner. Nhưng thực ra vai trò Product Owner không hề mới, Product Owner là một trong ba vai trò của Scrum và Scrum thì đã hơn 20 năm tuổi.
Definition of Value
Human always follows and find Happiness. Although it's very difficult to find, everybody has different happiness. Some people think money is happiness or a happy family, others think happiness is the peace of the soul (like a monk)... So we can say "what makes people happy is value for them".
The company is the same. Of course, every company has an ultimate purpose is revenue (except you are running a non-profit company). So, values of them are making the customer happy, good culture, good processes. over that values is assumed to have more money or save more money.
Just start this post with a few questions: Is your product (#Noproject) roadmap working? How much time and effort you take to update it but it's still far away from reality?
If your roadmap is still well and value can be created to the end user, this post is not for you. This post also does not share how to have a good roadmap, just show some common issues when you build a roadmap to make your plan is useless.
As Product Owner, how do you deliver Values to your Customer/End-User? To know what is value, you need to validate it. To validate your value, you need to know who is your Customer (End user).
I asked that because identifying your end user is very important. If you don't know who is your real customer, how can you build a product to make them happy? Or you will make no-one happy, no customer happy is no business, right?
Let go through 3 Situations below:
I'm Khoa Doan (View my Linkedin), Professional Scrum Trainer at Scrum.org