How your stakeholders get insight of current state of marketplace
Hi, I took open assesment and thought about interesting sentence
’The PO invites stakeholders to the Sprint Review to learn about how the current state of the marketplace ...’ .
How stakeholders in your organisation gain those information?
Thank you
In Scrum, the product is released incrementally into the marketplace. Stakeholders then have repeated opportunities to determine the state of the product in relation to that market, including current and potential value.
How stakeholders in your organisation gain those information?
Marketplace is a general term. The main expression of this sentence is to understand whether the features(output) of the product has market value(outcome).
I think we should first understand who are the stakeholders in your organization.
Product stakeholders include sponsors, users, profit-seekers, and so on.
If this is a product to be sold, then marketing staff, sales staff, distribution partners, alpha tester, etc., are the best candidates for stakeholders.
If the product is used internally, the end users will be the most important stakeholders.
These appropriate stakeholders are very clear about what the current market wants and what kind of functions can satisfy the needs of the market.
Thank you @Ching-Pei Li, stakeholders identification is really good start. As I was involved with Scrum in startup environment I found challenging to find a tools to facilitate value maximisation especially if product has not been launched yet or it was in very early stage. So I am curious about real examples how such information are obtained in other organisation. How stakeholders in your examples gains this information ?
"How stakeholders in your examples gains this information ?"
Jana, if "product has not been launched yet or it was in very early stage" the information is "obtained" by the specific stakeholders through one or more of the below:
- stakeholders' prior expertise (ie from similar past positions)
- stakeholders' market research - competitor analysis
- business forecasts
- prototype/mock ups
- workshops
If it's in early stages (that is, you've created at least one increment that can be reviewed - and thoroughly tested, but not necessarily in production), even better because direct product feedback can be directed to the product owner, who, in turn, would analyse themselves and see how to best order/update the backlog.
Does this help?