PO still responsible from product after it launchs?
Let's say we released the product to market but there are still some bugs needs to fix, improvement ideas.. How should handle the process?
What does the Scrum Guide say about ensuring work is "Done" and of genuine release quality?
This is the opening sentences of the Scrum Guide's section that describes the Product Backlog
The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product.
If there are still bugs to fix and improvements to make, shouldn't they be in the Product Backlog for the Scrum Team to address?
The Scrum Guide doesn't mention anything about the launch of the product.
Do you perceive a need to handle the pre-launch and post-launch situation in different ways? If so, what are the reasons for that?
Why was a product with bugs released to market? And if there is room for improvement, then the product lives on.