To provide software on demand is not an easy task. However if you are following agile rules, the entire situation is different. The success ratio goes up. If asked to provide solutions to millions of community users, the question to ask is – is agile more than enough or is there space for SCRUM?
As a product owner, there is a need for -
- Scope Commitment
Communities are built as they help people of the same group with the same ideology and they stay together for a long time.
This decides the success and failure in the community. Collaboration with a community must be dependable, this leads to all the fake marketing campaigns inside a community be identified faster and deleted at the same time. Same way spam from your inbox is detected and pushed to a different folder and deleted after.
In this case, it means that the product owner has to be an active community member, if that’s not possible then, a domain expert who works very close with the product owner has to be active.
Grooming a product backlog is the priority for product owner
Product owner has to use different communication methods to when it comes to customer approach.
When dealing with a customer the product owner has to
- Find a problem
- Escalate the problem within the community
- Have a discussion forum for finding a solution.
This is followed by delivery of the product.
The product owner has to create two initial groups
- Experts Group
- Product Community group
Product owner should treat this group as a key project stakeholder. Product Owner should interact with experts group very close during implementation phase.
Results have to be provided to the whole community.
However mean while the sprint results have to be evaluated after each sprint.