Scrum master service to product owner
As per scrum guide
1)Understanding the product planning in empirical environment.
Do this mean that scum master should make the product owner understand the product planning?
2)Understanding and practicing agility
What does this mean as per product owner role?
Dear Tejas,
Ad 1) I am not an expert on the theory, but have been working with scrum methodology for >5 years now as product owner. In my opinion the scrum master should facilitate refining meetings with the team, so that userstories or epics or larger chunks of work are estimated by the team on complexity.
Based on that in my experience that product owner can construct a roadmap (what you call a product planning), which is basically the backlog estimated delivery in time, based on the teams velocity. Now, this is not a planning in the waterfall way of working. Because userstories get refined better, which will lead to better estimations of complexity. Also teams velocity could change over time.
Because priorities in the backlog change often in my experience, and refining continually leads to adjusted complexity estimations, I prefer using tooling to generate the roadmap for me or using tooling in which I can in high level visualize to my stakeholders when what would be delivered. For example: roadmunk, a-ha or priooo.
Ad 2) A product owner should be very aware of his role. Only defining the what. And based on estimation of complexity by the team (the how), prioritize userstories based on value creation. He/she should be the person that manages stakeholders expectations. The scrummaster has in the theory the role of evangelizing the way of working, but I think in practice also the product owner should do this within an organization