How you can contribute as a Product Owner

Prioritize product roadmap

• When a customer says something is critical, be able to verify how much critical it actually is based on your domain knowledge of that team’s function and the related team’s function
• Be able to differentiate between “noises” and “valid request” (customers will always make noise, every request is critical, knowing which is critical and which is not is your value)

Finalize scope

• Similar as product roadmap, choosing what to do is critical here
• Choosing the scope of each release, what we need for the first release, what we can do later
• Finalize the metrics - this is the hard thing but it’s how you can improve the product later on, and can “sell” your products to other teams/the company
• Get clear alignment with customer (in paper, email) is your value here, will help us to have no surprise later on

Write ticket

• Details with clear mock-up
• Important test-cases (so that QC won’t miss this when preparing their own test-case)

Follow-up

• With a drum-beat (fixed schedule)
• Know how to fix road-block for your team (e.g. ask sysadmin to improve UAT server, ask QC manager to dedicate more QC, ask customers to clarify the unclear points in ticket)
• Know when to ask for support

Monitor (usage, exception with report/dashboard)

• Product development isn’t stopped when we deploy. We live with it, receive customer feedback. So we need to have monitor/dashboard so that we can detect the issues before customers.
• Ask the right question: what can go wrong, how can we measure it and ask the developers for help with query so that you can have your own set of report/dashboard. It’s your value

Share (release notes, newsletter)

• The good product deserves to be appreciated.
• How to introduce your product to someone not in your team, who might not be technical so that they can quickly grasp the benefit of it. It’s your value